Helicone Pricing
Helicone's Team plan includes 10,000 free requests a month. One widely cited write-up says 10 million
Helicone's real numbers, verified straight from its own pricing page: Hobby is free for one seat and 10,000 requests a month, Pro is $79 a month for unlimited seats and the same 10,000-request starting allowance, Team is $799 a month for up to five organizations and SOC 2 plus HIPAA compliance, and Enterprise has no published price. Every paid tier lists the identical 10,000-request free allowance before usage-based billing applies, and Helicone's page never states the per-request rate that kicks in past it. This page verifies every figure against the vendor's own page, reconciles that against a third-party number that's off by a factor of a thousand, and covers the one question no tier answers: what your own customer never sees no matter which plan you're on.
Verified against Helicone's own pricing page
What Helicone actually costs
Helicone's pricing runs four tiers, and every figure below comes from Helicone's own current pricing page. Hobby costs $0 a month, caps at one seat and one organization, and includes 10,000 requests a month with seven days of data retention and a 10-logs-a-minute ingestion limit. It's built for one person testing an integration, not a team running production traffic.
Pro costs $79 a month, removes the seat cap entirely within a single organization, extends retention to one month, and raises the ingestion ceiling to 1,000 logs a minute. Team costs $799 a month, supports up to five organizations, extends retention to three months, adds SOC 2 and HIPAA compliance, and raises ingestion to 15,000 logs a minute. Enterprise has no dollar figure published anywhere on Helicone's site, quoted only through a sales conversation, and adds unlimited organizations, contract-length retention, a 30,000-logs-a-minute ceiling, custom SSO, on-premise deployment, and a dedicated support engineer.
Four tiers, one constant
The four Helicone tiers, in plain numbers
Straight from Helicone's own pricing page, not a third-party estimate.
Hobby: $0 a month
1 seat, 1 organization, 10,000 requests a month, 7-day retention, 10 logs a minute. Community support only.
Pro: $79 a month
Unlimited seats, 1 organization, the same 10,000-request starting allowance, 1-month retention, 1,000 logs a minute.
Team: $799 a month
Up to 5 organizations, 3-month retention, SOC 2 and HIPAA compliance, 15,000 logs a minute, a dedicated Slack channel.
Enterprise: custom pricing
No published number. Unlimited organizations, contract-length retention, custom SSO, on-premise deployment, bulk discounts.
The number one write-up gets wrong
10,000 free requests, not 10 million
Helicone's own pricing page is unambiguous on this point: Hobby, Pro, Team, and Enterprise all list the same starting allowance, 10,000 free requests a month, before usage-based billing applies. The tier price buys more seats, longer retention, a higher ingestion ceiling, and compliance certifications; it does not buy a bigger free request pool. That number stays flat across all four tiers on the vendor's own page.
One widely cited third-party cost breakdown states the Team plan's included allowance as 10 million free requests, a hundred-thousand-times larger figure than what Helicone itself publishes for that tier. Neither Helicone's pricing page nor its documentation shows any tier-specific jump in the free allowance; the number stays 10,000 across the board. A team that budgets off the third-party figure instead of checking the vendor's own page would badly underestimate the point at which usage-based billing starts, and Helicone's page compounds the problem by never publishing the per-request rate that applies once that 10,000-request line is crossed on any tier.
Two ceilings, not one
The rate limits that throttle a workspace before its request count ever does
Confirmed on Helicone's own pricing page: an ingestion ceiling and a dashboard API ceiling, separate from the monthly request allowance.
Logs a minute caps how fast the proxy records data
10 a minute on Hobby, 1,000 on Pro, 15,000 on Team, 30,000 on Enterprise. A workspace comfortably under its monthly request allowance can still get throttled mid-burst if traffic spikes past its tier's ingestion ceiling for even a minute.
API calls a minute caps how often you can pull data back out
10 a minute on Hobby, 60 on Pro, 1,000 on Team, with no published rate for Enterprise beyond a custom conversation. This throttles dashboard queries and integrations reading Helicone's data, separate from the ingestion limit above it.
What the meter doesn't show
Helicone's logs tell your team what a request cost. They tell your customer nothing
Every number on Helicone's pricing page, the request count climbing toward its 10,000-request allowance, a logs-a-minute spike against the ingestion ceiling, a retention window counting down toward seven days or three months, describes what it cost your own team to log and inspect an agent's requests. Unlimited seats on Pro and multiple organizations on Team both decide who on your own team can see that workspace; neither adds a second, scoped view for a customer sitting outside your company, and nothing in Helicone's own tier documentation, Hobby through Enterprise, mentions isolating a result to one specific end customer.
If you sell an AI agent inside a product other companies pay for, that gap surfaces the moment a customer asks what the agent actually did for their account this month, a question no request count or ingestion ceiling answers on its own. AiAgRe's Node SDK reads the same kind of agent events Helicone's proxy already logs, through the same one-line integration pattern, and tags each one with an organization identity and a customer identity at the point of ingestion. That turns into white-labeled dashboard components your customer sees inside your own product, scoped so tightly that one customer's numbers never reach another customer's view. It doesn't replace Helicone's own request logging, and most teams run both: Helicone for what a request cost and how it logged, AiAgRe for what that same activity was worth to the person paying for it.
Pricing on the rest of the category
Verified pricing on the other tools teams shortlist alongside Helicone
Helicone isn't the only proxy or tracer teams put on a shortlist next to it. If your comparison also includes Langfuse's full tier breakdown, Portkey pricing, Arize pricing, Braintrust pricing, Datadog LLM Observability pricing, or Galileo AI pricing, each of those pages verifies the current published tiers line by line, the same way this one does for Helicone. None of them add the customer-facing layer either; the gap above holds across the whole category, not just this one proxy.
FAQs
Helicone pricing: frequently asked questions
Common questions from teams pricing Helicone against their own request volume before they commit to a tier, or before they add a second layer on top.
How much does Helicone actually cost?
Four tiers, verified straight from Helicone's own pricing page. Hobby is free, capped at one seat and one organization, and includes 10,000 requests a month with seven days of data retention. Pro costs $79 a month, opens up unlimited seats within one organization, extends retention to one month, and raises the ingestion limit to 1,000 logs a minute. Team costs $799 a month, adds up to five organizations, three months of retention, SOC 2 and HIPAA compliance, and a 15,000-logs-a-minute ingestion ceiling. Enterprise has no published number, quoted only through a sales conversation, and adds unlimited organizations, retention kept for as long as the contract specifies, and a 30,000-logs-a-minute ceiling.
What happens once a workspace clears its free request allowance?
Every tier above Hobby, Pro, Team, and Enterprise alike, lists the identical starting allowance on Helicone's own pricing page: 10,000 free requests, then usage-based billing on top. Past that point, the page states plainly that further usage is billed, but nowhere on it does Helicone publish the per-request or per-thousand-request rate a workspace actually pays once it crosses that line. A team can read every tier's seat price, retention window, and rate limit in exact numbers and still not be able to calculate next month's bill from the page alone.
Does the Team plan really include 10 million free requests, or 10,000?
It's 10,000, the same starting allowance as every other paid tier. One widely cited third-party cost breakdown lists Team's included allowance as 10 million free requests before usage-based billing applies, a hundred-thousand-times larger number than what Helicone's own pricing page actually states for that same tier. Helicone's page is unambiguous on this point: Hobby, Pro, Team, and Enterprise all show the same 10,000-request free allowance, with the tier price buying more seats, longer retention, higher ingestion limits, and compliance certifications, not a bigger free pool. A team budgeting off the third-party figure instead of the vendor's own page would underestimate its real bill by orders of magnitude the moment usage-based billing kicks in.
What do the logs-per-minute and API-calls-per-minute limits actually restrict?
Two separate ceilings, and neither one is the request allowance itself. The logs-per-minute limit caps how fast Helicone's proxy will ingest and record trace data as an agent runs, 10 a minute on Hobby, 1,000 on Pro, 15,000 on Team, and 30,000 on Enterprise. The API-calls-per-minute limit caps how often a team can query Helicone's own dashboard API to pull that data back out, 10 a minute on Hobby and 60 on Pro, with Team's page listing 1,000 but no published API rate for Enterprise beyond "custom." A workspace can stay well under its monthly request allowance and still get throttled mid-burst if a traffic spike briefly exceeds the ingestion ceiling for its tier.
What does Enterprise add that Team never will?
Unlimited organizations instead of five, retention configured to the contract instead of a fixed three months, a custom MSA, SAML SSO, on-premise deployment, bulk cloud discounts, and a dedicated support engineer. Team already includes SOC 2 and HIPAA compliance, so the jump to Enterprise is less about unlocking a compliance certification Team doesn't have and more about deployment control and account structure: a company running several genuinely separate business units under one contract, or one that needs its data plane to never leave its own infrastructure, is the actual buyer for that tier rather than a team that has simply outgrown Team's request volume.
How does Helicone pricing compare to Langfuse, Portkey, or Arize?
On sticker price, Helicone's $79-a-month Pro tier sits close to Langfuse's $29-a-month Core plan and under Portkey's usage-based gateway pricing, though the four don't meter the same unit: Helicone counts raw requests through its proxy, Langfuse counts observations inside a trace, Portkey combines gateway calls with a virtual key model, and Arize meters spans and ingestion volume. A dollar-for-dollar read across any two of them undercounts what each one actually charges for, the same trap the 10,000-versus-10-million mismatch above shows in miniature: two sources describing the same tier can disagree by orders of magnitude once the unit each one is counting isn't the same. The fuller side-by-side of where Helicone sits next to five other tools in this category lives on the AI agent monitoring tools comparison, and the rest of the vendors with their own dedicated breakdown are linked below. For teams pricing a swap rather than a sticker-price comparison, the Helicone alternatives breakdown covers migration effort and feature parity on top of cost.
Does any Helicone plan show pricing or ROI data to my own customers, and can I run AiAgRe alongside it?
No plan does, Hobby through Enterprise, and yes, running both is the normal setup rather than a workaround. Every number Helicone's dashboard renders, the request count climbing toward its 10,000-request allowance, a logs-per-minute spike, a retention window counting down, lives inside a workspace scoped to the account paying Helicone's own bill. Unlimited seats on Pro and multiple organizations on Team both govern who inside your company can see that workspace; neither adds a second, scoped view for a customer sitting outside it. AiAgRe's Node SDK reads the same underlying agent events Helicone's proxy already logs, through the same one-line integration pattern, and tags each one with an organization identity and a customer identity at the point of ingestion. That turns into white-labeled dashboard components your own customer sees inside your product, showing deflection rate and cost per resolution scoped so tightly that one customer's numbers never reach another's view. Installing it doesn't touch how Helicone logs a request or bills a workspace; the two SDKs read the same agent, one billed and displayed to your team, the other billed and displayed to the customer paying for it.
Already logging every request through Helicone? Now show your customer what it did.
Request access and we'll walk through how AiAgRe's embed tokens map onto the request data Helicone already logs.