Pay for the governance, not the tokens.
A flat platform fee for the rails. Bring your own agents and LLM keys, run them on your own machines, and keep the freedom to switch models anytime.
Wire up one repo and one worker to see governed delivery on your own code.
- 1 repository
- 1 connected worker
- Full webhook intake & triage
- Configurable workflow & human gates
- Community support
For the solo builder running real, multi-repo work on their own infra.
- Unlimited repositories
- Multiple concurrent workers
- Bring-your-own agent & LLM keys
- Reconciler: lost/stale-worker recovery
- Failure-aware routing & rework loops
- Email support
Shared tenant for a team that wants coordinated, auditable delivery.
- Everything in Builder
- Multiple users per tenant
- Shared workflows & charters
- Full attempt-level audit trail
- Priority support
Decoupling governance from the model is the whole point.
| IssueFlow | Black-box agent vendors | |
|---|---|---|
| Pricing model | Flat platform fee | Per-seat ($500+) |
| Token costs | None — your keys | Marked up |
| Model choice | Any agent, per stage | Vendor-locked |
| Where code runs | Your machines | Vendor cloud |
| Human gate placement | Configurable | Fixed at the PR |
| Lifecycle coverage | Triage → merge | Coding moment only |
Questions
Do you charge for tokens or LLM usage?
No. You bring your own agent subscriptions and LLM keys and run them on your own workers. IssueFlow charges a flat platform fee for the governance layer — never a markup on your model usage.
How is billing handled?
Subscriptions are managed through Stripe. The portal routes you to Stripe to start or change a subscription.
Where does my code run?
On your own machines. You attach self-hosted workers, and agent runs execute there — your code and repositories never leave your infrastructure.
Which agents and models are supported?
IssueFlow is model-agnostic and ships no agent of its own. You define the frameworks available on each worker and assign one per workflow stage.