Menu
FinOps for production AI

AI cost control for the era of tokens.

We find, cut and keep your LLM savings. Tidal Audit maps the spend for free. Tidal Gateway, a LiteLLM gateway we deploy and operate in your cloud, makes the changes stick. Tidal Telemetry shows live cost by team, feature and workflow, reconciled to your provider invoices. You pay a flat 20% of the savings we verify, and nothing else.

● Invoice-first audits ● 40–60% typical reduction ● Read-only by default ● Multi-cloud
Tidal Telemetry · OpenLIT-based

Live LLM cost, straight from your traces.

Tidal Telemetry is the live cost view in the Tidal suite, built on OpenLIT. Send OpenTelemetry data and explore traces with token usage, estimated cost, latency and errors. It is included in the engagement and open now as a live trial.

Cost & tokens

Inspect token usage and estimated per-call cost in LLM traces.

Latency & errors

Review request timing and errors alongside usage.

OpenTelemetry

Send traces, metrics and logs through OTLP.

Agent setup

Connect a coding agent to the hosted MCP server for setup and troubleshooting.

FIG. 01 — Request routing schematic · per-request cost
Reconciled against → OpenAIAnthropicGeminiBedrockAzureGroqTogetherMistral
SEC. 01 — Platform

FinOps for AI, on four pillars.

The FinOps Foundation framework — visibility, attribution, optimization, accountability — applied to LLM spend. Same discipline. Different unit of cost.

FIG. 02-APILLAR 01

Visibility

Token-level cost data ingested from every provider. Reconciled hourly. Filterable by provider, model, feature, team, customer, environment.

  • OpenAI · Anthropic · Bedrock · Gemini · Azure · Groq · Together · Mistral
  • Hourly ingestion · <5 min reconciliation lag
  • Read-only by default · NDA + DPA on request
FIG. 02-BPILLAR 02

Attribution & chargeback

Every token mapped to a feature, team, and customer cohort. Monthly chargeback and showback, exported to your finance system or as CSV.

  • Custom dimensions · feature, team, tier, region
  • Cohort spend · customer-tier P&L
  • NetSuite · QuickBooks · CSV · API
FIG. 02-CPILLAR 03

Anomaly detection

Real-time alerts when spend, latency, or quality deviates from a feature's rolling baseline. Slack, PagerDuty, email — and auto-throttle when it matters.

  • Per-feature rolling baselines · seasonality-aware
  • Slack · PagerDuty · email · webhook
  • Optional auto-throttle & budget enforcement
FIG. 02-DPILLAR 04

Automated optimization

Routing, caching, and compression deployed behind feature flags, A/B tested seven days minimum, graduated only on quality & cost wins.

  • Routing tree · per-request quality classification
  • Semantic cache · sub-10ms hit latency
  • Quality SLO + auto-rollback on regression
SEC. 02 — Optimization

Six levers, one parts list.

Most teams combine three or four. The audit ranks which dominate your spend surface and projects savings before any commitment.

PART №LEVERFUNCTIONRANGE
OPT-01

Model routing

Each request classified by complexity and routed to the cheapest model that meets your quality bar.

30–50%
OPT-02

Semantic caching

Near-duplicate prompts fingerprinted with embeddings; identical answers served from sub-10ms cache.

20–40%
OPT-03

Prompt compression

System prompts audited, examples deduplicated, retrieved context compressed. Every change A/B tested.

15–30%
OPT-04

Batch & async pricing

Non-interactive workloads routed to batch endpoints (up to 50% discount) with SLO-aware queueing.

10–50%
OPT-05

Provider arbitrage

Identical capability often costs 2–3× more at one provider. Route by capability-per-dollar.

20–35%
OPT-06

Fallback chains

Smart retries and tiered fallbacks beat worst-case over-provisioning while holding SLO.

5–15%
SEC. 03 — Engagement

Assembly sequence: five weeks.

Every engagement follows the same four phases. Most customers see their first reconciled provider invoice by the end of week five.

STEP 01 · WEEK 01

Audit — map every dollar.

Ingest provider invoices, gateway logs, usage telemetry. Full spend map by provider, model, feature, team — ranked by dollar waste.

STEP 02 · WEEK 02

Agree — lock the baseline.

We set the baseline against your invoices, the quality guardrails and the contract. You sign off on every change.

STEP 03 · WEEKS 03–05

Implement — deploy Tidal Gateway.

We deploy a LiteLLM gateway in your cloud and ship the changes through it: A/B tested 7 days vs. baseline, then graduated to 100% traffic.

STEP 04 · ONGOING

Operate & reconcile.

We run the gateway, so savings don't drift back. Tidal Telemetry measures the result and every month closes with a signed Statement of Savings.

SEC. 04 — Pricing

Pay on results.

One fee: a flat 20% of the savings we verify. Tidal Audit, Gateway and Telemetry operations are included. No licence.

★ MOST POPULAR · PAY ON RESULTS

Performance

Free audit. Then you only pay when we save you money — measured against a locked baseline, reconciled to provider invoices.

20%
of verified savings · no savings, no fee
  • Free audit · 1-week turnaround · countersigned baseline
  • We implement, not just recommend · Tidal Gateway deployed and run by us
  • Tidal Telemetry · live cost, chargeback and monthly signed statements
  • Engineering pair · weekly reviews
  • Quality SLO enforcement & auto-rollback
  • No minimum spend · no down payment · 30 days' notice
Book free audit →
INCLUDED · THE TIDAL SUITE

Audit, Gateway, Telemetry

Three products, one fee. Our team runs all three. None is licensed or priced separately.

Incl. in the 20%
audit free · gateway and telemetry operations included
  • Tidal Audit · free, read-only review of invoices and usage logs, run by our team
  • Tidal Gateway · a LiteLLM gateway we deploy and operate in your cloud: routing, fallbacks, caching, batching, per-team budgets, hard stops
  • Tidal Telemetry · live cost by provider, model, feature, team and workflow, and the evidence behind each monthly statement
  • Baseline locked to invoices · provider price cuts excluded · quality regressions don't count
  • No licence · no down payment · no minimum
See Tidal Telemetry →
SEC. 05 — Reference

Common questions.

Missing something? Email hello@finopsllm.com — we respond within one business day.

What is FinOps for LLM? [+]
FinOps for LLM brings the FinOps Foundation framework - visibility, attribution, optimization, and accountability - to LLM and GenAI spend. It includes per-feature and per-team chargeback, anomaly detection, budget governance, and continuous optimization of model routing, caching, and prompts.
What does FinOps LLM do? [+]
FinOps LLM finds, cuts and keeps your LLM savings. It is a managed engagement built on three products we run for you: Tidal Audit (free, read-only), Tidal Gateway (a LiteLLM gateway we deploy and operate in your cloud for routing, fallbacks, caching, batching, per-team budgets and hard stops) and Tidal Telemetry (live cost by provider, model, feature, team and workflow). Savings are reconciled monthly against provider invoices.
How is pricing structured? [+]
One model. Free audit, then a flat 20% of verified monthly savings, measured against a baseline locked before anything changes. No licence fee, no seat count, no minimum. Tidal Gateway and Tidal Telemetry operations are included in the 20%.
How much can we save? [+]
Typical reduction in the first full billing cycle after implementation is 40–60%, depending on architecture and traffic mix. Real targets are set after a provider-invoice audit and workload review.
Which providers are supported? [+]
OpenAI, Anthropic, Gemini & Vertex AI, AWS Bedrock, Azure OpenAI, Groq, Together, Mistral, Cohere, Fireworks, Replicate, and most OSS endpoints. Multi-provider deployments typically have the largest savings surface.
Does FinOps LLM support chargeback & showback? [+]
Yes. Token-level attribution to providers, models, features, teams, and customer cohorts. Monthly chargeback and showback exported to NetSuite, QuickBooks, CSV, or API. Custom dimensions supported.
How do you handle customer data? [+]
Read-only by default. Billing and usage data is enough for most attribution work. Prompt and output data is only accessed with explicit approval, for specific optimizations that require it. NDA and DPA available on request.
How long does implementation take? [+]
Attribution and dashboards go live in under a week. Optimization implementation takes 3–5 weeks; savings appear on the first full provider invoice after go-live.
Will optimization hurt output quality? [+]
No. Every routing, caching, and compression change is A/B tested against production for seven days minimum before promotion. Regressions auto-rollback. Quality is monitored continuously alongside cost.
SEC. 06 — Research

Engineering guides that show up in AI answers.

Deep dives on LLM cost attribution, monitoring, caching, and governance. Cited by Microsoft Copilot when buyers research AI FinOps.

Browse all research →

SEC. 07 — Start here

Start with a clear picture of your AI spend.

About a week. Read-only access. We return with a full map of your spend, ranked by waste, plus a baseline Tidal Telemetry can track against. Free. No implementation commitment.

30-min discovery · read-only by default · NDA + DPA on request · no commitment