Caveman Cloud· HostedGet Started
Caveman Cloud: see what your agents cost and cut it
Caveman Cloud records the agents your team runs and ships, ties their cost to the work they did, and counts a saving only once production proves it.
Caveman Cloud shows what your agents cost and cuts it, with proof. It records the coding agents your team runs and the agents you ship, ties what they cost to the work they did, finds waste, and tests each proposed change against your own traffic before it ships. Traffic reaches it three ways: point an SDK at the Caveman gateway, route your coding agents through it, or send OpenTelemetry traces from a gateway you already run, such as LiteLLM.
Caveman Cloud is self-driving software for your LLM stack. Built-in agents observe your traffic, evaluate candidate changes, prove them with evidence, and propose improvements. You stay in control and approve what ships. The loop runs continuously: Observe, Diagnose, Generate, Evaluate, Deploy, Learn.
What sets Caveman apart is that it proves its own claims. Every number carries a label (measured, inferred, tested, or verified), changes ship only after they clear eval gates, the default path is byte-safe, and verified savings start at an honest $0. Read Why Caveman for the full picture.
Choose your path#
Integrate in one line, label traffic, control optimizations per request, and debug with traces, SQL, and evals.
Govern AI spend across teams, agents, and coding tools with eval-gated rollouts, RBAC, and audit.
Understand what each number means, which savings are verified, and how to report them with confidence.
Connect, diagnose, prove, and report in four weeks.
Hosting, encryption, key custody, tenant isolation, and data policy.
Hosted Cloud, your own VPC, on-prem, or local-only tools.
Let AI drive#
Give Claude Code, Codex, or Cursor access to your project over MCP.
Paste one prompt and let your coding agent wire up the gateway, evals, and baseline.
See how Ask Caveman, Improvements, judges, and rollouts work together.
Review agent-generated changes backed by Evidence reports before they ship.
Get started#
Send your first request through the Gateway and see it in Traces within minutes.
Route agent or application traffic with a base-URL swap and two headers.
Understand the Observe to Learn loop and how Caveman Cloud handles your traffic.
Point the OpenAI SDK (TypeScript or Python) at the Caveman gateway.
Trace workflows, search tools, and export telemetry from your application.
Query traces, run SQL, and operate the control plane from the terminal.
Onboarding#
Sign in to the console
Open your Caveman Cloud console and sign in. If you were invited to a project, you land directly in that workspace.
Create a project and API key
Go to Gateway, Connect to create a project, then generate a Cave API key. Copy the key and your gateway URL. The gateway URL has no trailing slash.
Set environment variables
Export
CAVE_API_KEYwith your Cave key andCAVE_GATEWAY_URLwith your gateway origin. Keep your upstream provider key separate.Swap the base URL
Change the
baseURLon your OpenAI or Anthropic client to${CAVE_GATEWAY_URL}/openai/v1or the matching provider path. Add thex-cave-upstream-keyheader when the provider key is not stored in Caveman Cloud.Send a request and view the trace
Run one chat completion or agent turn. Open Traces in the console to inspect the request, model, usage, and latency.
Core surfaces#
Savings evidence#
Caveman Cloud reports three kinds of numbers, and it keeps them separate:
- Measured spend records observed usage and its pricing basis.
- Inferred savings describe an estimate or counterfactual, not a guaranteed invoice reduction.
- Verified savings require a supported accounting method and qualifying evidence. They stay zero when that evidence is absent.
See Savings Evidence for the full contract, Optimization Catalog for what each optimization changes, and Reporting Savings for turning these numbers into a monthly finance report.