--- title: The intelligence layer of your org description: AI spend and usage intelligence for the whole org. Caliber puts every seat, token and agent your company pays for on the org tree from your HRIS: spend by team and owner, budgets that hold at the vendor, and insights that help every person get better. url: https://trycaliber.ai/ --- # The intelligence layer of your org. Plug in your HRIS and see AI spend by team and owner, the cost of every shipped item, and every seat, key and agent your org pays for, including the ones nobody uses. Already live with paying customers. ## The full picture: Finally see how your org runs on AI. Caliber joins your tools with your org tree and permissions, so every answer is scoped to who is asking: the company for an executive, the team for a manager, themselves for everyone else. - AI tools: Claude (Team, Enterprise, Claude Code), Cursor, OpenAI (ChatGPT, Codex, API), Amazon Bedrock. - AI gateways: Portkey and LiteLLM, with cost by person, model, token type and reasoning effort. - Org tree, roles and sign-in: HiBob, Shapes, BambooHR, Okta, Microsoft Entra ID (SAML and OIDC too). A person's place in the org decides what they see. - Delivery: Jira, Linear, GitHub. - Business systems: Salesforce, Zendesk, Slack. Insights Caliber runs on its own, every day: - Non-R&D people who put 80% or more of their AI spend on frontier models such as Opus. - People who do a large share of their work on a model a major version behind. - People who stopped using AI after weeks of regular use. - People who left the company, per the HRIS, but still hold paid seats or spend. - Seats idle for 30 days, and keys and agents with no owner. - Teams running maximum reasoning effort on routine work. ## The org canvas: Your whole company, one canvas. Every department from your HRIS, with its headcount, spend per person, adoption, budget and top alert. Open a team to see spend by provider, its skills and work mix, or open a person to see their level and what to try next. ## What Caliber does ### Live today - Spend by team and owner: Every AI dollar, seats and usage together, on the org tree from your HRIS. Down to the team and the person who owns it. - Cost per shipped item: What each merged PR and closed issue cost in AI, per team. Spend tied to output, not to logins. - Seats, keys and agents, reconciled: Every seat, API key and agent reconciled to an owner and a team, including the ones nobody uses. - Budgets per person, team and work type: Budgets for every person, department and type of work, seats and usage together. When one runs out, the cap is set at Anthropic and Cursor. - What the AI work is: Every session classified by objective: feature, bug fix, initiative. Plus the share of merged code AI wrote, line by line. - Ask your org anything: A question in plain language, answered for your position: a team lead sees their team, an executive sees the company. In the app or over MCP. - Skills and agents, by team: Which skills, agents and MCP servers each team runs, how often, and what they cost. See what spreads, and what nobody opens. - Recommendations for every person: Each person gets their level, the next practice to try, and the skills their best teammates already use, recommended where they work. ### Coming next - Find the bottlenecks: Where work waits from prompt to production: review queues, handoffs, rework. With the cost of each delay. ## Security: Your data plane, in your VPC. Caliber installs into your cloud with Helm and only ever talks outbound. Raw prompts, identities and keys stay with you; the hosted app sees de-identified aggregates. - Helm, in your namespace: A from-zero install into a dedicated namespace in your VPC, pinned by digest. - Outbound 443 only: No inbound ports, and no Caliber access into your perimeter. - Prompts stay home: Raw prompts, identifiers and credentials never leave. We receive de-identified, aggregated metrics. - Metadata, not transcripts: A lead sees that a session ran long and why. A lead cannot read the session. - Roles from the org chart: Sign in with Entra ID, SAML or OIDC. Access follows the HR reporting line. - Encrypted and isolated: AES-256-GCM at rest and row-level security per tenant. A guard at boot refuses to start without it. ## Compared with engineering intelligence tools Caliber is compared on the site with DX, Jellyfish, LinearB, Swarmia, Span, Waydev, Weave. Caliber starts where engineering intelligence stops: every team on the org tree, every seat, key and agent with an owner, and budgets that hold. The right column describes the category in general terms, not a feature audit. | Topic | Caliber | Engineering intelligence, typically | | --- | --- | --- | | Who it is for | Every team on the org tree, engineering or not. | Engineering leadership and R&D. | | Where the numbers hang | On the org chart from your HRIS: HiBob, Shapes, Entra ID. | On engineering teams and repositories. | | Seats, keys and agents | Every seat, API key and agent reconciled to an owner and a team. Unused ones flagged. | Not the focus. | | Budgets | Per person, department and work type. Over budget, the cap is set at the vendor. | Reporting, not enforcement. | | How you ask | In plain language, answered for your position. In the app or over MCP. | Dashboards and reports. | | Where it runs | Your VPC via Helm, outbound 443 only. Prompts never leave. | Vendor-hosted, typically. | ## Questions and answers ### What is Caliber? Caliber is the intelligence layer of your org. It connects every AI tool, agent and dollar a company pays for to the org chart from its HRIS, so every leader sees what their people use, what it costs and what it ships: AI spend by team and owner, cost per shipped item, and every seat, key and agent reconciled to an owner and a team. ### Is Caliber only for engineering teams? No. Engineering intelligence tools stop at R&D. Caliber measures every team on the org tree, engineering or not, because the roster comes from the HRIS. Support, sales, marketing, finance and people teams get the same view of adoption, spend and ownership. ### What does Caliber show today? AI spend by team and owner, seats and usage together. Cost per merged PR and closed issue. Every seat, API key, agent and Bedrock account reconciled to an owner and a team, with unused ones flagged. Budgets per person, department and type of work, with caps pushed to Anthropic and Cursor when one runs out. The work mix of every AI session (feature, bug fix, initiative) and the share of merged code AI wrote, line by line. And plain-language questions, answered for the asker's position, in the app or over MCP. ### Does Caliber help people get better, or only measure them? Both, and the individual comes first. Every person gets their level, the next practice to try and the skills their best teammates already use, recommended where they work. Leaders see which skills, agents and MCP servers each team runs, so a practice that works in one team spreads to the rest. ### What insights does Caliber surface on its own? A daily run of insights across the org, for example: non-R&D people who put 80% or more of their AI spend on frontier models like Opus, people who do much of their work on a model a major version behind, people who stopped using AI after weeks of regular use, people who left the company but still hold paid seats, keys with no owner, and teams running maximum reasoning effort on routine work. ### What does Caliber connect to? AI tools: Claude (Team, Enterprise, Claude Code), Cursor, OpenAI (ChatGPT, Codex, API) and Amazon Bedrock. AI gateways: Portkey and LiteLLM, with cost by person, model, token type and reasoning effort. The org tree, roles and sign-in: HiBob, Shapes, BambooHR, Okta and Microsoft Entra ID, so every person sees what their place in the org allows. Delivery: Jira, Linear and GitHub. Business systems: Salesforce, Zendesk and Slack. ### Can a manager read someone's AI sessions? No. Caliber keeps metadata, never transcripts. A lead sees that a session ran long and why, never the words. Managers see their own team, an executive sees the company, and a person sees themselves. ### Where does Caliber run? As a hybrid data plane in your own cloud: installed with Helm into a dedicated namespace in your VPC, talking only outbound over port 443, with no inbound ports. Raw prompts, identities and credentials stay with you; the hosted app sees de-identified aggregates. Sign-in and roles come from Entra ID, SAML or OIDC, and a team is live inside a week. ### What is coming next? Delivery intelligence on the same org tree: where work waits from prompt to production (review queues, handoffs, rework) and what each delay costs. ### Who uses Caliber today? Caliber is live with paying customers, from fintech to software companies. Customer names and figures are published once each customer approves. ### How does Caliber compare to DX, Jellyfish, LinearB, Swarmia, Span, Waydev or Weave? Those are engineering intelligence tools: engineering leadership, R&D, repositories. Caliber starts where they stop: every team on the org tree, every seat, key and agent with an owner, and budgets that hold at the vendor. They go deeper on engineering delivery metrics today; delivery bottlenecks are on Caliber's roadmap. Comparisons live at trycaliber.ai/solution/vs/. ### Is any of Caliber open source? Yes. Caliber began as ai-setup, an MIT-licensed CLI on GitHub (caliber-ai-org/ai-setup, on npm as @rely-ai/caliber) that reads a codebase and writes the configs AI coding agents need: CLAUDE.md, .cursorrules, AGENTS.md, skills and MCP servers. ### How do I get started? Book thirty minutes with the founding team at trycaliber.ai/get-a-demo, or write to sales@trycaliber.ai. You walk out with a roadmap for your org, zero slides. ## Next step Sleep better, knowing you're in control. Thirty minutes with the founding team. You walk out with a roadmap for your org, and every seat, key and dollar accounted for. Book a demo: https://trycaliber.ai/get-a-demo ยท sales@trycaliber.ai