Chat / RAG
$1,950/mo ungoverned
save $1,248/mo from routing
One question, one answer. Customer chat, document Q&A, simple summarisation. Daily volume = end-user requests, not engineer count — a small SaaS chatbot or internal RAG sees ~1–5K/day.
AnyForge · The AI governance index
Most teams default to a frontier model for everything. Smart Routing sends simple requests to Haiku, mid-complexity requests to Sonnet, and the hardest requests to Opus. It usually cuts the bill by half or more. Move the sliders.
Pick a preset to populate per-workload daily volumes below. Each row stays editable — adjusting any row switches this to Custom.
The model your team currently sends every call to. Drives the ungoverned (red) bar: your baseline.
Routing mix · what AnyForge would route to
The models that fill each tier when routing is on. Drives the With AnyForge Control (gold) bar. Default is the Anthropic ladder; mix providers freely to match what you would route to.
Annual savings · all workloads
$58K
By workload: $15K chat / rag · $28K single agent · $15K multi-agent crew.
On the multi-agent row specifically: $13K/yr from routing alone, plus $1,895/yr from Crew on top. Crew's biggest savings come from HIL gates that prevent entire bad runs from completing. They aren't modelled here, so the calculator under-counts Crew by design until we have measured data.
Your AI portfolio
Set the daily volume per workload to match your stack. Defaults are typical for an active product.$1,950/mo ungoverned
save $1,248/mo from routing
One question, one answer. Customer chat, document Q&A, simple summarisation. Daily volume = end-user requests, not engineer count — a small SaaS chatbot or internal RAG sees ~1–5K/day.
$3,600/mo ungoverned
save $2,304/mo from routing
One agent loops through plan → tool → result → next step. Cursor, Claude Code, Cline, browser-use. Daily volume = agent invocations across your dev team — ~10 devs × 30 invocations/day ≈ 300/day for an active engineering org; small pilots run 50–100, large teams 500+.
$1,755/mo ungoverned
save $1,123/mo from routing
+$158/mo from Crew on top
= $1,281/mo total saved with Control + Crew
Architect → Engineer → QA → Compliance with HIL gates. The AnyForge Crew shape. Daily volume = orchestrated runs/day — active Crew shops run ~30/day (≈ one per PR); pilots run 5–10, scaled production crosses 100/day.
Bars share one scale across rows and bands. Intent-based routing assumes a 70% / 20% / 10% split across reflex / production / reasoning tiers, filled by Claude Haiku 4.5 · Claude Sonnet 4.6 · Claude Opus 4.7. The Crew band credits a midpoint 25% reduction on routed cost (modelled at 15%–35% depending on cache hit rate), applied only to multi-agent because Crew is the multi-agent product. Click the i badge on each band for the mechanisms. Pricing as of 2026-05-01; verify against live API docs before publishing.
AnyForge Platform Fee Calculator
Three columns: same workload running on raw provider API (“DIY direct”), through AnyForge Control proxy, and on AnyForge Crew with managed service. Routing is projected to cut modelled model spend on the same work by 30–50% (the calculator uses 40%), and a small flat platform fee applies to what flows. Numbers update live and are illustrative — the actual rate is shared with design partners and platform accounts.
Claude Code as primary IDE, throughout the day
Sonnet 4 with heavy prompt caching
Raw provider API. No routing, partial caching, no portable memory or audit.
Same workload through AnyForge Control: routing is projected to cut modelled model spend 30–50% (40% shown).
Pick the Full Crew adoption preset to see the Crew + Managed Service breakdown.
Estimates based on industry-typical token volumes for adoption levels and blended provider rates with caching. The AnyForge platform fee and Crew Managed Service figures here are illustrative, provider-agnostic assumptions. Actual rates are shared with design partners and platform accounts. DIY baseline assumes the same workload running on raw provider APIs without routing, which routing is projected to cut by 30–50% of modelled model spend (40% shown). Self-hosted provider shows $0 model spend. You pay AnyForge for the orchestration, not the inference. Crew Managed Service is a separate contract; an illustrative floor is shown for the selected team size.
Model ladder · 2026 pricing
Three tiers, organised by capability and price band. Reference list: set what your own routing mix uses up in the calculator. The calculator launches with the Anthropic ladder (Haiku 4.5 / Sonnet 4.6 / Opus 4.7) as a recognisable starting point: Anthropic and OpenAI both ship full three-tier stacks, so mix providers freely. Prices are dollars per million tokens.
Tier · reflex
Classification, routing, extraction, simple summarisation
Tier · production
Drafting, RAG, customer chat, tool-using agents
Tier · reasoning
Complex coding, multi-step planning, contract analysis
Routes & agent frameworks
Per-token list price for the same model is essentially identical across native API, Bedrock, Vertex, and Azure. The interesting cost differences are commitment-driven — EDP credits, CUDs, MACC, and aren't generic. The exception is OpenRouter, which adds a structural ~5% markup. The calculator above does not model commitment-derived discounts because they depend on your existing cloud spend.
Anthropic native
source →Claude only
Published list price
Volume tiers, prompt caching API, batch API (50% off), latest features ship here first
AWS Bedrock
source →Claude, Cohere, Mistral, AI21, Llama, Amazon Titan
Same as native list price for each model
AWS EDP credits, Provisioned Throughput, region availability, no Anthropic features that have not been ported
Google Vertex AI
source →Claude, Gemini, PaLM, third-party
Same as native list for each model
GCP Committed Use Discounts, regional residency, Gemini-only features (Google Search grounding, etc.)
Azure (AI Foundry / Azure OpenAI)
source →OpenAI, Llama, Mistral, Cohere, Phi: no Anthropic, no Gemini
Same as OpenAI list; sometimes a small premium
Microsoft EA / MACC commitments, PTUs, enterprise procurement, US-Government regions
OpenRouter
source →Anthropic, OpenAI, Google, open-source: many providers behind one API
Native list + ~5% markup
One-API convenience, no commitment, useful for spike traffic: worse for steady-state cost
Vendor agent frameworks (Bedrock Agents, Vertex Agent Engine, Azure AI Agents, OpenAI Assistants) lock you into the underlying cloud or provider. AnyForge sits in the bring-your-own-harness row: governance applies regardless of route, so the savings story above holds whichever cloud you commit to.
Bring your own harness (AnyForge)
Any LLM, any route
yes
Raw API calls, your own agent loop. Governance applies regardless of route. The same Crew runs on Bedrock, Vertex, or native APIs.
AWS Bedrock Agents
Any model in Bedrock
no
Action groups, Knowledge Bases, multi-agent collaboration. Tied to AWS console, IAM, observability. Lock-in to AWS.
Google Vertex Agent Builder / Engine
Gemini natively, Anthropic via Vertex, others
no
GCP-shaped. Tooling, eval harness, deployment all assume GCP IAM and services.
Azure AI Foundry Agent Service
OpenAI + Llama + Mistral via Azure
no
Azure-only. No Anthropic, no Gemini. Useful for shops standardised on MS stack.
OpenAI Assistants / Anthropic vendor SDKs
That vendor only
no
Vendor-native agent primitives. Tied to one provider; cannot route across.
From spreadsheet to production
AnyForge does this for you: routing as policy, role-bounded crews, an audit trail your CFO can actually query.