OpenWind · In active development

Requests, approvals and handoffs, run your way. Every step records who or what moved it, and when.

OpenWind runs work as records moving through steps you define. You change the steps without writing code. It runs on your own servers. The foundation and the first customer-ready apps are complete; scale and extensibility are in progress. The connector runtime and webhook gateway are built, but there are no ready-made connectors yet. No AI features inside OpenWind today.

Bring us a workflow
An example

One expense claim, step by step.

Any request your team handles is built the same way: a record that moves from step to step. Here is one, drawn in blocks. The steps and names are an invented example; you set your own.

Illustrative · invented example

  1. Submitted

    An employee files a claim with the receipt attached.

    Employee

  2. Manager approves

    Only the line manager can approve. If they reject it, they must say why.

    Line manager

  3. Finance checks

    Finance confirms the amount and the receipt match the policy.

    Finance team

  4. Paid

    The claim is closed and the payment is noted on it.

    Finance team

Every move is written down: from which step, to which step, who or what moved it, and when. A claim that waits too long at one step can raise an alert.

How it works

How a record moves.

Illustrative · schematic

  1. Request

    Someone moves a record to its next step.

  2. Guards

    Who is allowed, which conditions hold, which fields are required, and a reason, where you ask for one.

  3. Recorded

    From, to, who or what moved it, and when, in the record's history.

  4. What happens next

    Automations, notifications, webhooks.

Undoing a step is a new step, so the history shows both.

What it does

What an operations team gets.

Steps you configure.

A visual workflow editor. A new workflow is configuration, not new code.

Reasons where they matter.

Any step can require a comment before it runs.

Time limits per step.

SLA timers and breach alerts, which can trigger automations.

Recurring work (nearly complete).

Scheduled work orders created automatically, preventive maintenance for example.

Your work in one place.

Each person sees their own work, across every workflow, on one screen.

Integration by webhooks and API.

Webhooks (automatic messages between systems) in and out, regular checking for systems without them, and an inbound API for partners. More is in progress.

Attachments scanned.

Uploaded files are scanned for viruses, with quarantine.

Isolation in the database.

Each organisation's data is separated by the database itself, with isolation tests.

On your servers.

Runs on your own servers, with sign-in and secrets storage that you host too.

Run one workflow on it, beside what you have.

How a Proof works