Pricing

CHARGED FOR PROTECTION, NOT FOR TOKENS.

One protected agent is one durable Elixir Agent ID enabled for protection. You supply your own Claude, Codex, API-provider or private-model credentials, and Elixir does not mark up a single token of that usage.

  • Developer

    Free

    1 protected agent

    • Bring your own executor

    • Manual recovery

    • Basic evidence

    • API and MCP access

    Download Elixir
  • Pro

    Most chosen

    $49/month

    5 protected agents

    • Autonomous recovery

    • Incident history

    • Multiple executor adapters

    • API and MCP

    • Enhanced evidence

    Subscribe to Pro
  • Team

    $199/month

    25 protected agents

    • Continuous monitoring

    • Policy controls

    • Shared access

    • API, MCP and webhooks

    Subscribe to Team
  • Business

    $749/month

    100 protected agents

    • Advanced governance

    • Approval policies

    • Audit trails

    • Production fleet capabilities

    Subscribe to Business

Enterprise

Custom

Large fleets, with the operational and governance requirements that come with them. Priced per engagement.

Contact for Enterprise
  • Private deployment

  • SSO and RBAC

    Discussed per engagement. Not shipped in the alpha.

  • Custom adapters

  • Extended audit retention

  • Enterprise policy

  • SLA and support

How billing works

BRING YOUR OWN AI.

Elixir does not mark up your model usage

You supply your own supported Claude, Codex, API-provider or private-model credentials, and you pay your provider directly at their rates. Elixir charges for protection — the governance, evidence and recovery system around the model — and never takes a cut of the reasoning.

Where a provider reports tokens rather than money, Elixir records cost_usd: null rather than guessing. Unknown is never zero.

One protected agent is one durable Agent ID

Not one host, not one process, not one caller. An agent that moves between machines, runtimes or providers is still one protected agent, because its identity does not change when its infrastructure does.

A Fleet Doctor does not turn 100 patients into one billable agent. Billing counts the durable Agent IDs enabled for protection — the patients — not the number of callers reporting on their behalf.

What a lapsed subscription does — and does not — do

Elixir never deactivates an agent for a billing reason. Not on past_due, not on unpaid, not on canceled. A lapse reduces what may be added; nothing already protected is switched off, and Elixir will not resolve an over-entitlement by choosing an agent to stop protecting. Payment grants nothing, and withdrawing it takes nothing away that is already running.