Pricing

Flowzart bills workflow compute in watt-hours (Wh) and kilowatt-hours (kWh). If that’s a strange unit to see on a software bill, the short explainer walks through why and what’s actually being measured. The tables below cover the numbers.

Energy units

Subscriptions are priced in Wh per month. PAYG packs are priced per fixed Wh quantity. One Wh is roughly 25 LLM-using workflow runs; one kWh is about 25,000.

How the meter works

Every node type carries a Watt rating. When a node runs, it costs its rating multiplied by the seconds it spends working, rounded up to whole seconds with a one-second minimum. Waiting counts as working: an HTTP call that spends three seconds on a slow third party draws its full rating for all three.

Some real ratings, straight from the engine:

Node	Rating
If, Switch, Transform, Loop	1 W
State Manager	2 W
Webhook trigger, Schedule, Delay	5 W
Rate limiter, Circuit breaker	10 W
HTTP Request, Secure HTTP	50 W

The shape of the table is the point: logic is nearly free, and the expensive nodes are the ones that reach out into the world. A workflow run’s cost is the sum of what its nodes actually did, so a run that takes a fast path through the graph costs less than one that takes the slow path.

Running out

Hitting zero doesn’t kill anything. The balance goes negative and the deficit shows in the meter as honest debt; the next payment or renewal clears it. The only thing that stops workflows is having no active pack at all, for instance when a PAYG pack passes its one-year mark with nothing else on the account. We’d rather owe you an awkward number than hand you half a workflow.

Subscriptions

Tier	Per month	Allowance	Effective €/Wh	Roughly
Overture	€0	1 Wh	n/a	~25 LLM-using runs
Solo	€19	100 Wh (0.1 kWh)	€0.190	~2,500 runs
Ensemble	€89	1,000 Wh (1 kWh)	€0.089	~25,000 runs
Maestro	€189	5,000 Wh (5 kWh)	€0.0378	~125,000 runs

The monthly allowance resets every billing cycle. Unused Wh from a subscription month do not roll over.

Overture is permanently free at 1 Wh per month, enough to try Flowzart end to end without a card on file. The other three tiers are subsidised relative to pay-as-you-go: more Wh per euro than the equivalent PAYG pack, and the price per Wh keeps dropping as the tier rises.

PAYG packs

Pack	Price	€/Wh
100 Wh	€20	€0.200
1 kWh	€150	€0.150
5 kWh	€600	€0.120
25 kWh	€2,500	€0.100

Every PAYG pack is valid for one year from purchase. PAYG balance survives subscription cancellation: if a subscription lapses, the PAYG Wh remaining on the account stay there until they’re spent or their one year is up, whichever comes first.

PAYG is the right call when usage is occasional or unpredictable. The €/Wh is higher than a comparable subscription, but every Wh sits on the account until used.

Subscriptions vs PAYG

The subscription tiers are subsidised relative to PAYG, and the subsidy steepens at each step up:

Tier	€/Wh subscription	€/Wh equivalent PAYG	Effective discount
Solo	€0.190	€0.200 (100 Wh pack)	~5%
Ensemble	€0.089	€0.150 (1 kWh pack)	~41%
Maestro	€0.0378	€0.120 (5 kWh pack)	~69%

Another way to read the same shape: the Wh a euro buys roughly doubles at each tier up. Solo gives ~5.3 Wh per euro, Ensemble ~11.2, Maestro ~26.5. Each step up roughly doubles the energy a euro buys.

The choice is mostly about predictability. A subscription is the better deal at known monthly volumes. PAYG is the better deal when the volume is unknown, sporadic, or below the next tier’s allowance.

Third-party costs

A Wh measures Flowzart-side resources only: compute, memory, network, and storage on Flowzart’s infrastructure.

Third-party services that a workflow calls (LLM providers, webhook destinations, transactional email, image APIs, anything that hits an external endpoint) are billed directly by those services against the user’s own API keys. Flowzart’s meter doesn’t see those costs and doesn’t bill for them.

For the analogy and a fuller breakdown of what a Wh actually covers, see What the hell is a kilowatt-hour?.