Solo
One repository and a calm month of tickets.
$29 / month
- 1 workspace
- 1 repository
- 40 ticket runs / month
- 30-day run history
- Encrypted key vault
- Email support
Pricing
Pay for the conveyor, not the model.
Editor assistants usually sit near the price of a single seat and still leave the Jira-to-branch loop to a person. Hosted coding agents that bring their own model often start in the hundreds of dollars. DeveloperAI is the layer in between: your Cursor key does the writing, and the workspace that runs the loop starts at $29.
Most teams
Crew
The plan a small team actually finishes the quarter on.
$79 / month
- 1 workspace
- 5 repositories
- 200 ticket runs / month
- 90-day run history
- Switch the active repo anytime
- Priority email support
Forge
A busy board, still one conveyor belt.
$199 / month
- 1 workspace
- Unlimited repositories
- 1,000 ticket runs / month
- 1-year run history
- Custom Jira status names
- Stripe billing and receipts
How the numbers were chosen
Bring your own keys
GitHub, Jira, and Cursor bill you directly. A price that also resold model usage would double-charge the same ticket. These plans price the orchestration only.
Hard caps, no overage
Solo is 40 runs, Crew is 200, Forge is 1,000. When the month is used up, automations pause until the next period or an upgrade. A runaway board cannot invent a bill.
Annual is ten months
Yearly billing is the monthly price times ten: $290, $790, or $1,990. That is two months free, not a made-up discount.
| Solo | Crew | Forge | |
|---|---|---|---|
| Monthly | $29 | $79 | $199 |
| Annual | $290 | $790 | $1,990 |
| Ticket runs | 40 | 200 | 1,000 |
| Repositories saved | 1 | 5 | Unlimited |
| Active repo at a time | 1 | 1 | 1 |
| Run history | 30 days | 90 days | 1 year |
| Your API keys required | Yes | Yes | Yes |
| Surprise overage | None | None | None |
Trial, then Stripe
Every new workspace starts on a 14-day Solo trial: 1 repository and 40 runs. The trial is enough to connect keys and watch a ticket go through. It does not require a card.
Paid plans are bought in Stripe Checkout and renew until you cancel. The workspace keeps trial limits until Stripe confirms the first payment, then the selected plan’s cap and repository allowance apply for that billing period. When a trial or paid period ends, logins still work and keys can be updated, but automations stay off.
Questions
Do I need Cursor? Yes. The agent runs with your Cursor API key.
Can I poke around before the keys are in? Yes. The dashboard, forms, and billing pages are open. The Jira webhook stays unpublished and rejected until GitHub (token, repo, and branch), Jira, and Cursor are all verified and the plan is in its trial or paid period.
What is a run? One accepted In Progress event that starts the conveyor for a ticket.