Reliable by design.
Honest about limits.

Atomic Flow began with a simple question: how can applications make failure handling explicit, testable, and easier to reason about?

What we're building

An open-source ecosystem centered on explicit workflow execution and recovery. The TypeScript implementation is the starting point; shared concepts may guide other language implementations later.

Explore the concepts ↗

What we won't promise

No library can universally roll back a payment, an email, or an arbitrary external action. Atomic Flow aims to make such limits and failure outcomes visible — not disguise them as guaranteed atomicity.

Understand the limits ↗

Open source

Atomic Flow's repositories use the Apache License, Version 2.0. Source, documentation, and design notes are visible while the project evolves.

Visit the organization ↗

Contributions

External contributions are temporarily restricted while foundational contracts and APIs are defined. The project can open up incrementally as those foundations mature.

Follow the roadmap ↗