Draw your incident process.
Then let it run.
A flow is a picture of what should happen when something breaks — and the thing that actually executes it. No runbook that goes stale, no glue code nobody wants to own.
Available on Every plan
A single condition node splits the quiet day from the bad one. Both paths are visible, both are live.
01
Nodes for the things you already use
Payment gateways, webhooks, message queues, serverless functions, databases and notification channels. Each node is configured in the panel, not in code, so changing a route is a two-minute edit rather than a deploy.
Payment gateway
Stripe, PayPal
Webhook
Any HTTP endpoint
Message queue
SQS, RabbitMQ, Kafka
Serverless function
Lambda, Cloud Functions
Database
Postgres, MySQL, Mongo
Notification
Email, SMS, Jira
02
Branch on what actually happened
Send a declined card down a retry path and a 500 down an escalation path. The same flow handles the quiet day and the bad one, and you can see which branch fired.
no — declined card
yes — server error
03
The diagram is the documentation
Hand a new engineer the flow instead of a wiki page. What they read is what runs — which is not true of any runbook written more than a month ago.
Node
AWS Lambda: process_sub
Renews subscriptions from the queue. On failure the payment is retried once, then on-call is paged.
Advanced details
Built by AI agents too
Claude Code, Cursor or any MCP client can read flows and add nodes through the API. Starter and up.
One flow per service
Split by service or environment — each flow has its own webhook key.
Flows by plan
1 on Hobby; 4 included on Starter and 8 on Pro, then $10 and $8 per extra flow; unlimited on Enterprise.
Safe concurrent edits
A version check stops two editors, or an agent, overwriting each other.
Everything else, in the same place.
Real-time reports
Errors and events arrive as they happen, grouped so one noisy bug stays one report.
Alerts that reach you
Email, SMS, Jira and webhooks on every plan, routed by the flow you drew.
Public status page
Tell your users what is broken before they open a ticket. Included from Starter.
Advanced analytics
Trends, frequency and impact across every flow. Exportable from Starter, deeper on Pro.
Team access
From 2 seats on Hobby to unlimited on Enterprise, with roles for who manages billing and members.
Frequently asked questions.
A Flow is a visual workflow that defines how errors and events are processed in your system. Each flow can include multiple nodes for triggering, processing, and responding to events.
Relevant articles
All articles →8 min read
Top 5 System Monitoring Solutions in 2026
Knowing a server is up is table stakes. Knowing the moment something breaks — and having it handled — is the real job. Here are the five best system monitoring solutions in 2026, led by Atflow.
7 min read
5 Best Mixpanel Alternatives in 2026
Mixpanel made product analytics mainstream, but event-based pricing and a charts-only ceiling send many teams looking. Here are the five best alternatives in 2026, led by Atflow.
9 min read
10 Cheap Error Tracking Solutions in 2026
Error tracking should not cost more than the app it watches. Here are 10 budget-friendly options in 2026 — ranked for value, with Atflow on top.
Get your free account. One flow included.
Nothing to install, no card required. Draw your first flow and point your app at it.
Get started free