Licensing, machines & limits

How license tiers, concurrent machine slots, and the free-tier limits work — and why flowwork suits ephemeral sandboxes.

Machines & sandboxes

One license runs on multiple machines at once — Free: 1, Pro: 5, Team: unlimited. The engine binds a machine automatically on first start (by a hardware fingerprint); there’s no extra step.

Slots are concurrent, not lifetime: when the engine stops it releases its slot, and an idle machine frees its slot automatically after a few hours. That makes flowwork ideal for ephemeral sandboxes — spin one up, let Claude Code author and run a workflow, then destroy it. The slot frees on teardown, so a fleet of short-lived sandboxes shares one key and you pay for the minutes used instead of hosting an always-on server.

# In a fresh sandbox
export FLOWWORK_LICENSE_KEY=FW-XXXXX-XXXXX-XXXXX
flowwork &            # claims a machine slot
# ... Claude Code authors + runs workflows via flowctl ...
# destroy the sandbox — the slot is released on shutdown
Hit the machine limit?

Stop an idle machine (or let it expire), or upgrade for more concurrent machines.

Free-tier limits

The free tier allows up to 3 active workflows and 10 runs per day. Activating a 4th workflow or exceeding the daily run count returns a clear upgrade message rather than failing silently.

Note

Limits are about active workflows and runs per day — not a cap on steps, forms, or connectors within a workflow. Upgrade to remove the limits.