Pricing for solo developers
and engineering teams
Operon is the command center for the AI coding agents you already run. Start local with a one-time license, add cloud sync when you work across devices, and move to per-seat Team when a whole team needs the same view. Every plan runs Claude Code, Codex, Cursor, Gemini CLI, and Aider.
Plans
Three ways to run your fleet
Solo Local
For individual developers · 14-day trial
- Unlimited local sessions
- Full trace and event history
- Context monitor and flight plan
- Persistent terminal daemon
- Analytics dashboard + session DNA
- Any CLI agent — 5 verified, more in beta
Pro
For multi-device + sharing · 14-day trial
- Everything in Solo Local
- Cloud sync + Supabase Realtime
- Decision memory search across devices
- Session continuation + branching
- MCP Hub + Skills + Automations
- Linear / GitHub / Jira import
- Session history sharing with redaction
Team
For engineering teams
- Everything in Pro
- Team observability dashboard
- Cross-session intelligence + cost prediction
- Best practice + knowledge extraction
- Tool benchmarking across the team
- Worktree orchestration (incl. SSH remote)
- PR draft generator + admin audit log
What unlocks at each tier
What every plan includes
The instruments, not just the agents
Every plan wraps the CLI agents you already use rather than replacing them. Sessions run in isolated Git worktrees, the same task can be raced across agents in Arena, and multi-step work is planned and routed through orchestration.
The observability layer is the same on every tier: full trace history, context monitoring, and cost tracking. What paid cloud plans add is where that data can be seen — a second device, a teammate, a dashboard — not whether it is captured. Data handling on each tier is documented on the local-first security page.
Larger organizations also run an Enterprise plan with self-hosting and compliance controls; it has no public list price. The plans and pricing reference describes what each plan is for, and solo vs team covers when syncing with a team starts to pay off.
Already have an account? Plan changes, invoices, and seat counts live on the Billing screen in the web dashboard, which requires signing in: manage your subscription.
FAQ
Pricing questions
Q
Solo Local is a one-time purchasefor a single developer on a single machine, and it unlocks every local feature — sessions, traces, context monitoring, analytics — with no cloud dependency. Pro is recurring and adds cloud sync, decision memory across devices, and session sharing. Team is priced per seat and adds the shared workspace: team observability, cross-session intelligence, and worktree orchestration.
Q
Yes, two ways. Local mode is not a time-limited trial — it runs fully, with no account, for as long as you want. If you want cloud features (sync, the web dashboard, team surfaces), a new account starts with a 14-day trial so you can evaluate them before committing to a recurring plan.
Q
Cloud surfaces become read-onlyuntil you pick a plan. Local mode keeps working the whole time regardless — your sessions, traces, and history stay on your machine and remain fully usable.
Q
Per seat, per month. A seat brings one member into the shared workspace: they can see the team’s synced decisions and session metadata, appear in team analytics and observability, and take part in shared workflows. You pay for the members who are actually in the workspace.
Q
Your repository is never uploaded as fileson any plan. Cloud plans sync events, tasks, decisions, session information, prompt and response text, tool inputs and outputs, and code diffs by default, and you can turn off per-project code-content sync to keep diffs and tool I/O local. Adding teammates lets them see that shared data; it does not add a new category of upload.
Q
Yes — from the Billing screenin the app or the web dashboard, which requires signing in. You can move between plans there, and the app reflects your effective plan immediately, adjusting which cloud features are available.