Buy the workflow surface you actually need.
Start local with Solo. Add repository slots, GitHub Actions validation, and agent workflow support with Pro or Studio.
Website subscriptions
Prices are loaded from Paddle. Machine and repository limits are enforced by the licensing backend on every paid command.
Solo
- Local CLI and TUI cockpit
- Security, dependencies, secrets, code health
- SARIF, JSON, and HTML reports
- No source upload
Pro
- Everything in Solo
- Repository slots for CI validation
- MCP server for coding agents
- PR gate with annotations and SARIF upload
Studio
- Everything in Pro
- More machines and client repos
- Agent-ready repair prompts
- Best fit for repeat review workflows
Plan comparison
The important difference is not only price. It is whether the plan stays local-only or can enforce repository workflows in CI.
Pricing FAQ
The current model is built for solo developers and small teams first. Enterprise procurement pages can come later when the product has that sales motion.
Does Code Radar upload my source code?
No. Scans run locally or inside your GitHub Actions runner. License and analytics calls use entitlement and metadata, not repository contents.
Why does Solo have zero repository slots?
Solo is intentionally local-only. Repository slots start with Pro because CI usage is where shared keys and team workflows need stronger controls.
Can I change plans later?
Yes. Paddle handles billing, and the licensing backend reads active plan limits from the database rather than hardcoded client limits.
What happens if Paddle checkout is unavailable?
The page shows the checkout error and the backend records the failed conversion with attribution, so marketing data stays accurate.