Pricing

One price for the control layer

Price Codie by the people using it. Keep every model, workflow, manager view, and cost control in one system as the team grows.

Works with
ClaudeCodexGeminiKimiGLMMeta Muse
Codie Finance showing AI spend, cost per merge, monthly burn-down, and projected month-end spend.
Plans

Start with the team. Expand when it works.

Your quote is based on team size and rollout needs. We'll put the scope and price in writing during the demo process.

For engineering teams

Codie Platform

Custom per-person quote

Everything a team needs to see, manage, and improve AI engineering work.

  • Session capture across supported coding tools
  • Developer, manager, and admin views
  • Blocker, onboarding, and activity visibility
  • Sessions connected to pull requests and merges
  • Model Operations, access policy, and usage
  • Finance reporting and cost per merge
  • Team Memory, skills, and shared patterns
  • Standard integrations and email support
For larger rollouts

Enterprise

Volume company rollout

Codie Platform with the controls, implementation, and review support larger companies require.

  • Everything in Codie Platform
  • Advanced role-based permissions
  • Company model catalog and policy controls
  • Security and procurement support
  • Custom integrations
  • White-glove rollout support
  • Volume pricing
How pricing works

Simple enough to budget

The platform price follows the team, while Codie keeps model usage and engineering economics visible.

01

Per person

Price the people in the rollout rather than buying a separate Codie seat for every model or coding tool.

02

One control layer

Manager visibility, model policy, session intelligence, skills, and finance reporting stay together.

03

Volume as you expand

Start with the engineering group in play and move to volume pricing as more teams come online.

Codie Finance with AI spend, delivery economics, cost per merge, and projected monthly spend.
The full cost picture

Know where the money goes

See AI spend next to active developers, merges shipped, cost per merge, and the projected month-end total.

Spend and outcomes in the same Finance tab
Monthly burn-down before the provider bill arrives
Cost per merge that leaders can track over time
Enterprise controls

Set the boundary once

Define the approved model catalog, privacy requirements, role baselines, request limits, and monthly budgets from one policy surface.

The right models for each role
Clear limits and review paths
Support through security and procurement review
Codie company model policy with approved models, budgets, rate limits, and role baselines.
A clear quote

Price your engineering rollout

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