Annotate your existing code in minutes, and make your applications fault-tolerant and observable by default. No orchestration server required.



The open source DBOS Transact library simplifies workflow and AI agent idempotency, concurrency, observability and other backend complexities.
Durable, idempotent workflows as code. Start, stop, resume, schedule, fork, and more.
Scale easily with durable, concurrent task queues.
Emit OTel logs, traces, and metrics for easy troubleshooting.
Highly efficient reliability scales to handle large, complex use cases.
Host your durable agents & applications anywhere.
Your agent control plane - make workflow ops even easier.
Not at all! DBOS is not a heavy framework that takes over your codebase. You only add DBOS decorators to the specific functions that actually need reliability.
Temporal is an alternative durable execution solution to DBOS, but it requires you to deploy and maintain a separate, dedicated workflow orchestration server alongside your application.
DBOS Transact is a library that runs directly inside your existing application code and uses your existing Postgres database in which to store and recover workflow state and execution history.
You get enterprise-grade durability without an entirely new piece of infrastructure to manage.
Nope! The DBOS Transact library is 100% open-source. You can run it on your local machine, or deploy it to your own cloud server.
DBOS Conductor is not required to run durable workflows built with DBOS. But it does make them easier to manage.
DBOS Conductor is a workflow ops platform that gives you visibility into DBOS workflow and queueing state and history. It can alert you to failures, and allow you to stop, start, fork, pause workflows. It also automates high availability for your application instances, automatically resuming them if it detects outages.



The easiest way to make workflows and queues durable and observable.