ProcessWeave runs your business processes end to end — across ERP, email, documents and human approvals — entirely inside your own infrastructure. Every action, human or automated, is recorded in an audit trail built to be examined.
Your datacentre or your own cloud account.
One deployment serves one customer.
The service writing the log holds INSERT only.
Your directory decides who is who.
Your process data stays on your network.
A return authorisation. An invoice approval. A new partner onboarding. The work crosses an ERP, a mailbox, a spreadsheet, a scanned PDF and four people who each know what to do next. No single system owns it, so it is held together by habit, chasing and re-keying — and when something goes wrong, reconstructing what happened means asking people what they remember.
Single-tenant, on-premise. Your ERP credentials, your documents and your process data stay on your network. There is no vendor cloud in the execution path — not for the work, not for the metadata, and not for model calls when you choose to host the model yourself.
Examine the architectureEvery step, decision, correction and failure is written to an append-only log with the actor’s verified identity and, for every edit, the value before and after. Append-only is enforced by database privilege rather than by convention: the service that writes the log holds INSERT and nothing else, and refuses to start if it holds more.
Examine the architectureThere is no path from a model to your production systems. AI drafts, a human approves, and only then does anything act. Document extraction returns a confidence score for every field, and anything below your threshold goes to a person instead of becoming a guess.
Examine the architectureA ProcessWeave workflow is a JSON definition in your own Git repository. You can diff it, review it in a merge request, roll it back, and take it with you. There is no proprietary format holding your process hostage — and no code buried inside the definition. The platform’s components are code; your process is configuration.
Explore the platform
{ "id": "invoice-approval", "version": "3", "nodes": [ { "id": "arrives", "type": "trigger", "component": "email.watch" }, { "id": "extract", "type": "action", "component": "document.extract", "input": { "ref": "${arrives.attachments[0]}" } }, { "id": "check", "type": "gate", "when": "${extract.confidence} >= 0.85", "onFail": "route-to-manual-entry" }, { "id": "approve", "type": "human-task", "form": "invoice-approval", "pool": "finance-managers", "when": "${extract.amount} > 5000" }, { "id": "post", "type": "action", "component": "erp.post-invoice" } ]}Illustrative workflow definition
email.watchThe process starts with a received request.
Illustrative executionAn approval that waits nine days for a manager is not a cron job and a status flag. ProcessWeave executions are durable: they survive restarts, deployments and infrastructure failures, and resume exactly where they stopped. Failed steps retry — and because every external write is idempotent by rule, a retry never creates the same record twice.
Execution is waiting. Its position is preserved.
Illustrative sequence
ProcessWeave is early, and you should hear that from us rather than find it out. The execution engine, the audit substrate, the human-task layer and the connector model are built and running. Our first deployment is in acceptance testing with the customer. Conversational design and the intelligence layer — the part that watches thousands of runs and tells you what to change — are on the roadmap, not in the product. If you need those today, we are not your vendor yet. If what you need is durable, auditable automation that runs inside your own walls, we are ready to talk.
Read the current boundaries
The components — what the platform can reach and do.
The workflow engine that executes definitions durably.
The record of everything the platform has done.
Validation, simulation, optimisation, process mining.
Designing a process by describing it.
The fastest way to evaluate ProcessWeave is to walk one of your real processes through it with our engineering team. Not a sandbox tour — we take a process you actually run, and show you how it would be defined, executed, and audited.
Request a technical walkthrough