Two we build as products. One is next. The rest we build to order, in your environment.
Work becomes records moving through steps you define. You change the steps without code. Every step records who or what moved it, and when.
No AI features inside OpenWind today.
Designed for work orders, preventive schedules, inspections with readings and limits, and custody. The foundations are in place; the asset, work-order and schedule modules aren't built yet. Not ready for production.
It will turn a contract into a workflow your team can run: who owes what, and by when, set up as steps in OpenWind. Your team reviews a draft instead of writing one, and nothing runs until they approve it.
Your counsel decides what a clause means. Timing is a plan, not a date.
These are capabilities, not boxed products. When the same job comes up twice, it earns a name and a page.
Routine work is checked against rules your team wrote, and exceptions go to a person who decides.
Ask about this: Checking work against your rulesTest model behaviour on your own cases and produce evidence a reviewer can read. We map it to the rules; we don't certify.
Ask about this: Evals and evidenceRecord which tools an agent can reach, and give it credentials scoped to a budget you set. We report on what we tested.
Ask about this: Tool and agent securityFind the AI subscriptions and APIs that are unused or duplicated, and what each one costs. We don't resell any of them.
Ask about this: AI spend audit