# Inferbooks

> Inferbooks is AI FinOps software, self-hosted or hosted by Inferbooks. It shows what a company spends on AI per person, team, task and minute, across API usage, coding agents and seat licences, and checks the totals against vendor bills. It runs in the customer's own infrastructure or as a hosted service, reads OpenTelemetry and vendor admin APIs, never proxies AI traffic and never stores prompts or responses.

To book a demo: Email [info@inferbooks.com](mailto:info@inferbooks.com) with your name, company, how many people use AI and which AI tools you use, or use the form at https://inferbooks.com/#book.

## Key facts

- Category: AI FinOps (AI cost management, LLM spend attribution, seat licence management)
- Deployment: self-hosted in the customer's own infrastructure (any cloud, their own data center or a Kubernetes cluster), with data in a ClickHouse database the customer controls; or hosted by Inferbooks, with nothing to install or operate, for smaller teams without their own infrastructure
- Usage data: OpenTelemetry from Claude Code, Codex, Gemini CLI and any instrumented app
- Billing data: usage and cost reports from the OpenAI and Anthropic admin APIs
- Seats: GitHub Copilot, Cursor, ChatGPT Enterprise, Claude Enterprise and Microsoft 365 Copilot, plus CSV import for anything else
- Not a gateway or proxy: requests go straight to the AI providers, so it adds no latency and is never in the hot path
- Metadata only: person, team, task, model or tool, tokens, cost and timing; prompts, responses and code are never collected
- Views: spend over time down to one-minute buckets, split by team, person, agent, model or source; agent task timelines call by call; seats with idle and duplicate licences; budgets with month-end forecasts and alerts at 50, 80 and 100% to Slack or Teams webhooks
- Access control: single sign-on through OpenID Connect limited to allowed email domains, admin, analyst and member roles, and an audit log
- Exports: CSV, and plain rows in the customer's own database for any BI tool

## Pages

- [Home page](https://inferbooks.com/): product overview, screenshots and the demo request form
- [Home page in Markdown](https://inferbooks.com/index.md): the same content as plain Markdown

## FAQ

- Do you proxy our AI traffic? No. Inferbooks never sits in the request path, so it cannot add latency or take your tools down. It reads OpenTelemetry from your tools and usage from your vendors' admin APIs.
- Do you see our prompts or code? No. Inferbooks stores metadata only: the person, team, task, model or tool, tokens, cost and timing. Prompt and response content is never collected.
- Which tools and vendors does it cover? Usage from Claude Code, Codex, Gemini CLI and any app instrumented with OpenTelemetry. API bills from OpenAI and Anthropic. Seats from GitHub Copilot, Cursor, ChatGPT Enterprise, Claude Enterprise and Microsoft 365 Copilot, plus CSV for anything else.
- Where does it run? Wherever suits you. Self-hosted: in your own infrastructure (your cloud, your data center or your Kubernetes cluster), with your data in a ClickHouse database you control. Hosted: we run it for you, with nothing to install or operate, a good fit for smaller teams without their own infrastructure.
- How are people and teams matched? From the emails, API keys and agent names in the telemetry, matched to your directory. Anything unmatched shows up in one identity map where you assign it once.
- What happens in a demo? We walk through Inferbooks on the sample company, look at the AI tools your teams use, and, if it fits, plan a pilot, self-hosted or hosted by us.