Atomic commits
Application data and workflow state commit in the same PostgreSQL transaction, so a failure is never partial.
Workflow engine
Highway
Durable workflow orchestration on PostgreSQL.
Available
What it is
A workflow engine in which application data and workflow state commit in the same PostgreSQL transaction, so a crash cannot leave partial state behind. No Kafka, no Redis, no external queues: if you run PostgreSQL, you can run Highway.
Who it is for. Engineering teams that run long-lived, multi-step processes and want the guarantees of a database transaction rather than the semantics of a queue.
- PostgreSQL-native
- Durable execution
- Python DSL
- Multi-tenant
What it does
PostgreSQL-native
One source of truth. No Kafka, no Redis, no external queues and no extra infrastructure to run.
Durable execution
Workflows survive crashes and restarts and resume where they stopped; no work is lost.
Python DSL
Complex workflows defined in plain, readable Python without boilerplate.
Event-driven
Human-in-the-loop steps, webhooks and fan-out/join patterns are built in.
Circuit breakers
Failures are detected and contained automatically so they cannot cascade across services.
Multi-tenant isolation
Complete data isolation between tenants, enforced with row-level security.
Audit trails
Immutable event logs for compliance, with time-travel queries over historical state.
Ready to look at Highway?
The product site has the documentation and the way in. For procurement questions, a pilot or an integration, talk to us directly.