Pricing

One price for
the whole AI toolkit.

Every seat gets the full toolkit, governance and analytics. No separate charge per tool, model or feature.

For your pilot and beyond

Pro

$150per seat / month

For teams of 25–100 engineers.

  • The full toolkit: skills, harnesses (including Codie), models and policy, LLM API, agent tracing, MCP gateway and guardrails
  • Governance: model policy, access by role, budgets and limits, audit trail
  • Visibility: spend, cost per merge, skills and models that ship, limits and blockers
  • Your keys, ours, or both, with no token markup
  • Email support
For a company-wide rollout

Enterprise

Custom pricing

For 100+ seats.

  • Everything in Pro
  • SCIM provisioning and advanced roles
  • Company model catalog and custom policy controls
  • Security review and procurement support
  • Custom integrations
  • White-glove rollout and a dedicated contact
  • Volume pricing
Model usage

Model usage, your way.

Seats cover the platform. Model usage depends on how you configure it: bring your own keys and pay your providers directly, including against existing AWS Bedrock, Vertex or Azure commits; use Codiedev's keys and pay provider rates with no markup; or mix the two, model by model.

Your keysOur keysOr both
Services

Support for the way your team works.

Workshops and 8–12 week workflow consulting engagements are quoted separately.

See Services →
FAQ

Before you start.

What counts as a seat?

Anyone using the toolkit: engineers, product managers or anyone else running AI coding sessions through Codiedev.

Can we start with a smaller team?

Yes. Most companies start with a pilot team, then expand. Pro starts at 25 seats.

Do we have to switch coding tools?

No. Codiedev works inside Claude Code, Codex, Cursor and Copilot, and adds Codie for any model.

Can we use our existing Bedrock, Vertex or Azure commitment?

Yes. Bring your own keys and keep burning down those commits, then fill any gaps with models through Codiedev.

Do you store our code?

No. We keep session summaries and metadata, never your source code.

Price your rollout.

Tell us how many people are in scope and which tools and models they use. We'll show you the product and put the price in writing.