WeaveNet
Workflows with a formal execution model.
Most orchestration tools describe a workflow as a sequence of steps and leave the hard parts — two branches running at once, a join that must wait for both, a failure halfway through that has to be unwound — to whoever writes the handlers. WeaveNet models workflows as Petri nets, where those behaviours are part of the execution semantics rather than something each team reimplements.
For · Teams running multi-step processes across services, where partial failure is expensive.
CAPABILITIES
What It Does
Petri-Net Engine
Concurrency and synchronization are expressed in the net itself — parallel branches and joins behave the same way every run.
Visual Builder
Compose and inspect workflows on a canvas, with a code editor for the step definitions that need it.
Queue-Backed Execution
The gateway validates and enqueues; workers consume and execute. Load builds a queue instead of dropping operations.
Compensation
Define what unwinding looks like when a later step fails, rather than discovering the half-finished state in production.
Templates & Instances
Author a workflow once as a template, then instantiate it per organization and application.
Integrations
Webhooks, API keys and configurable HTTP targets for reaching the systems a workflow has to drive.
HOW IT WORKS
Start To Running
- 01You model a process as a net — the states it can be in, and the transitions between them.
- 02You publish that net as a template in the repository.
- 03Each organization instantiates the template for its own applications.
- 04The gateway accepts operations over REST, authenticates and validates them, then enqueues them.
- 05Worker nodes consume the queue and advance the net, holding locks so no two workers move the same instance at once.
UNDER THE HOOD
Architecture
EARLY CONVERSATIONS
Interested in WeaveNet?
WeaveNet is still early — we're talking with a small number of pilot partners. If it fits what you're building, we'd like to hear from you.