Business flows first
Flowhawk drafts your flows from your code and the first hours of traffic. You confirm them in a visual editor, rank how much each one matters, and every span and log carries its flow and step.
From one alert to the cause, in one dive.
Spots what breaks.
Dives on it.
Flowhawk watches your business flows and sets up its own collection. When one breaks, it goes straight to the cause: which flow, how many customers, the change behind it and the traces that prove it.
Top up from $30 and pay only for what you use. No seats. OpenTelemetry native.
POST /checkout
502 · 1.84 s
- checkout flow · checkout
- cart.load
- inventory.reserve
- payments.charge step · pay
- POST psp/v2/charges
- order.fail
What you see when a flow breaks
Real pages from Flowhawk, on a demo shop where a deploy broke checkout.
Built around what your customers do
Most tools show you services and hosts. Flowhawk starts from your business flows, like signup, checkout and payouts, and tells every story in those terms. It is for engineering teams without an SRE.
All signals, connected
Traces, logs, errors, metrics, sessions, AI calls and database queries share one trace ID. A log opens its trace at the right span, a chart point opens example traces, and every alert opens the flow it belongs to.
One page per incident
Each incident gets a page generated for it: the impact in orders or sign-ups, the failing step, the change before it and the traces that prove it. Every number links to the query behind it.
An agent that can change what is collected
The built-in agent answers questions, investigates incidents and proposes changes as reviewed diffs. Because Flowhawk owns collection, it can raise sampling on a broken flow for a while when it needs more evidence.
Config as code
Flows, alerts, dashboards, collection policies and page templates are YAML in your git repo. The UI, the agent and the CLI all write the same files, so every change can go through a pull request.
MCP for your coding agent
Claude Code, Cursor and other coding agents can query production data, incidents and flows over MCP while they write the fix.
One line of setup
A thin OpenTelemetry distribution for Node.js, Python, Go, Java, .NET, Ruby and PHP, plus SDKs for the browser, React Native, Flutter, iOS and Android. Collection is controlled remotely per flow, so you sample less of what is healthy and keep every error, without a redeploy.
// Node.js: npm install @flowhawk/sdk-node
require("@flowhawk/sdk-node").init({ service: "orders" });
# Python: pip install flowhawk-sdk
import flowhawk_sdk
flowhawk_sdk.init(service="recommendations")
// Go
flowhawk.Init(flowhawk.Options{Service: "payments"})
// Java and Kotlin
Flowhawk.init(Flowhawk.options("orders"));Pay for what you use, in dollars
Top up a balance and pay for what you store and what the agent does, priced in plain dollars. No plans and no per-seat fees, so invite the whole team. We set up your workspace after the first top-up, so there is no free trial to run out.
Prepaid balance
$30 first top-up
Every feature and 30-day retention on your own system. Top up again from $10 or turn on auto-reload. A 10-person team with light use spends about $31 a month.
Start for $30| Each GB of telemetry you send, kept for 30 days (billed as $2.00 per compressed GB, which holds about 10 GB) | about $0.20 |
| Agent investigation | $1.25 |
| Agent question | $0.25 |
| Generated page | $0.20 |
| Uptime check or heartbeat beyond the first 10, per month | $0.20 |
| On-call text message / phone call | $0.10 / $0.25 |
| Alerts, dashboards, flow rollups, push and email pages | free |
Prices exclude VAT and sales tax, which are added at checkout where they apply, and every top-up comes with an invoice. Top-ups stay valid for 12 months. Annual invoices, bring-your-own ClickHouse, longer retention and SSO add-ons are available on request.
Open the trace. Read the story.
Send your first traces and see your flows on the first page you open.