Taken from Helicone's own pricing page. Plans are metered on requests and log ingestion rate.
| Plan | Price | Included | Retention |
|---|---|---|---|
| Hobby | Free | 10,000 requests, 1 GB storage, 1 seat, 10 logs/min | 7 days |
| Pro | $79/month | 10k requests then usage based, unlimited seats, alerts, reports, 1,000 logs/min. 7 day trial | 1 month |
| Team | $799/month | 5 organizations, SOC 2 and HIPAA, 15,000 logs/min | 3 months |
| Enterprise | Contact them | Custom MSA, SAML SSO, on-prem, 30,000 logs/min | Forever |
Helicone shows you what happened. Every request, latency, tokens, errors, traced and searchable. That is genuinely useful and it is the thing most teams are missing.
What it is not is a spending limit. Seeing a bill climb in a dashboard and stopping it are different features, and a tool built for the first does not automatically do the second. If your actual problem is that a bill surprised you, check whether the tool you are evaluating enforces a cap or just draws you a chart of the damage.
✓ You are debugging LLM behavior and need request level traces
✓ You want prompt and response logging without building the pipeline
✓ Your team needs alerts and reports on production traffic
✓ You need SOC 2 or HIPAA on the observability layer
✓ You are pre-production. The free Hobby tier covers you, though 7 day retention is short
✓ You want routing and failover more than logging. That is a gateway job, look at LiteLLM or Portkey
✓ Your real problem is which client the spend belongs to. See below
Every tool on this page is built for engineers. They answer which model handled a request, how long it took, and what it cost in aggregate. That is the right shape for a product team.
It is the wrong shape for an agency. If you are billing eleven clients and running AI inside deliverables for all of them, the month-end question is not what your OpenAI bill was. It is which client is eating your margin. That means tying every call to a client, a deliverable and a rate card, then putting it somewhere your billing process can read. A gateway gives you raw usage. It does not give you attribution, and it does not put it on an invoice.
That is the part I build. Not a gateway, and not a product with a monthly fee. A cost attribution and reporting layer that sits on top of whichever gateway you already picked, wired into how you actually bill.
If your AI bill is fine but your client margins are not, that is a different problem. Worth 30 minutes.
Talk through your AI costs →