RudderStack Pricing: The Event Count Is the Cheap Axis
Free at 250,000 events a month, and for a B2B programme the volume is never what binds. Sync latency, connection counts and the Enterprise-only apps decide the tier.
RudderStack publishes a free tier at 250,000 events a month with a working pipeline, a Growth tier from $265 a month at one million events with a selector up to 25 million, and a quoted Enterprise tier. Warehouse sync latency, Reverse ETL connections and the Enterprise-only Profiles applications usually bind before volume does.
Key takeaways
- An event is defined on the page as a data point, with a single page load counting as one, so the meter tracks instrumentation rather than audience size and a B2B programme rarely approaches the free allowance.
- Warehouse sync steps three hours, 30 minutes and five minutes across the three tiers, and Reverse ETL connections step 10, 25 and unlimited, which is what actually moves a low-volume team up the ladder.
- Every row in the Profiles and Data Apps section, including attribution, identity resolution and propensity scores, is marked against Enterprise only, so the packaged version of the work a GTM team wants sits on the quoted tier.
- On the free tier, exceeding the allowance stops data processing after a second consecutive overage rather than billing for it, which makes the failure mode missing data instead of an unexpected invoice.
Reviewed and updated August 30, 2026
RudderStack Pricing: The Event Count Is the Cheap Axis
A revenue operations team prices RudderStack against its monthly event volume, finds the number comfortably inside a free tier billed at "$0 free forever", and concludes the platform costs nothing. Three weeks later the attribution work it was bought for turns out to sit on the quoted tier, and the conversation restarts from the top.
The event count is the axis the pricing page leads with, and for a B2B programme it is usually the least binding one. Three other axes decide the tier, and none of them is a volume.
Here is the ladder as it stands, what each of the four axes actually gates, and one contradiction worth knowing about before quoting anything from it.
The published ladder
| RudderStack plan | Rate as listed | Event allowance | Warehouse sync | Team members |
|---|---|---|---|---|
| Free, per the pricing page | $0, described as free forever | 250K events a month | 3 hours | 10 |
| Growth, per the pricing page | $265 a month at the entry volume | 1 million events a month, selectable upward | 30 minutes | Unlimited |
| Enterprise, per the pricing page | Custom, contact sales | Enterprise-grade volume | 5 minutes | Unlimited |
Growth carries a volume selector on the card itself, opening at "1 million events/month" and stepping to 3, 5, 7, 10 and 25 million, with anything above that directed to sales. The pricing page also offers "Save 15% with annual billing" and "Try 30 days free" on that card.
The free tier is not a stub. It includes the 16 SDK sources, more than 200 cloud destinations, warehouse destinations and Reverse ETL, which is a genuinely working pipeline rather than a demo.
What an event is, and why 250,000 is a lot for outbound
The pricing FAQ defines the unit without ambiguity: "An event is a data point generated by a website, app, server, or cloud application. For example, let's say you're browsing a website. When the page loads, that generates a page call that counts as 1 event."
So the meter counts page loads, clicks, server calls and cloud application records, not people and not sessions. That is the right way round for anyone who has been billed per monthly tracked user, because a chatty product no longer pays for the same person repeatedly.
It also means the volume you generate depends on what you instrument rather than on how big your audience is. A consumer product with a signed-in application produces events in the hundreds of millions. A B2B outbound programme produces a page load on a campaign landing page, a form submission, a reply, a meeting booked. Even instrumented enthusiastically, that is unlikely to trouble a quarter of a million events a month.
Which is the point. For this reader, the free tier's allowance is not the constraint, so pricing the platform on volume answers the wrong question.
- Event allowance per month
- Selectable upward on the middle tier
- Rarely binding for B2B outbound
- Free tier includes a working pipeline
- Warehouse sync times
- Transformation limit
- Reverse ETL connections
- Tracking plans and tracking plan events
- Profiles and the data applications
- Data retention settings
- Single sign on and VPC deployment
- HIPAA and a custom master agreement
The axis that actually moves teams up: latency and connection count
Read across the comparison table and the interesting steps are not the event numbers.
Warehouse sync runs three hours on Free, 30 minutes on Growth and five minutes on Enterprise. Reverse ETL connections run 10, 25 and unlimited. The transformation limit runs 5, 25 and unlimited. Tracking plans run one, then unlimited, and tracking plan events run 5, then 75, then unlimited. Team members run 10, then unlimited. Workspaces run production only, then development plus production, then custom.
For a team with modest volume, the first of those to bind is usually the sync interval or the connection count. A three-hour warehouse sync is fine for reporting and awkward for anything that triggers a workflow, and ten Reverse ETL connections runs out faster than it sounds once each destination tool wants its own.
The development workspace is the other quiet one. On the free tier there is production only, which means changes to pipelines are tested in the place they run.
Where attribution sits, and it is worth checking early
The comparison table lists a Profiles and Data Apps section containing identity resolution, a feature builder, a customer 360 table, an audience builder, activations, attribution, propensity scores, a real-time activation API and an activation API Redis cache. Every one of those rows is marked available against Enterprise.
That matters disproportionately for a GTM buyer, because attribution and identity resolution are frequently the reason the platform is being evaluated at all. Whichever model a team has settled on, and the tradeoffs are set out in last-touch attribution, position-based attribution and time decay attribution, the packaged application that computes it here sits on the quoted tier rather than on a published one.
The underlying data is still yours either way, which is the architectural point covered in what RudderStack is: the platform stores nothing, so the events land in your warehouse on any tier and a data team can model attribution there directly. The Enterprise rows buy the packaged version of that work, not access to the data.
Two things on the page that need care
The overage formula is unusual, and worth reading twice. The FAQ states that on a paid plan "the overage fee is calculated as the difference between the next tier's pricing and your current plan's pricing." That is not a per-unit rate. It means exceeding an allowance effectively charges the step up to the next volume band, so a small overshoot and a large one inside the same band cost the same, and the sensible response to a sustained overage is to move bands rather than to absorb the fee.
On the free tier, exceeding the allowance stops the pipeline. The same FAQ says data processing "will stop after your second consecutive overage". Not throttled, not billed. Stopped. For anyone running production instrumentation on the free tier, that is the single most important line on the page, because the failure mode is missing data rather than an unexpected invoice.
And a plan is named that is not on the ladder. The cards read Free, Growth and Enterprise. The overage answer in the FAQ underneath opens "If you're on the Starter plan", and "the Starter plan" appears nowhere above it. The most likely explanation is a renamed tier and a stale FAQ, and the safe course is to confirm the overage terms in writing rather than quote them from here.
- Yes: You know what warehouse sync interval your workflows actually need
- Yes: You counted the Reverse ETL destinations you will connect
- Yes: You checked whether the capability you want is in the Enterprise-only section
- Yes: You know whether you need a development workspace separate from production
- No: You priced the platform on your monthly event count alone
- No: You are running production instrumentation on the free tier without watching the allowance
Where the security and compliance rows land
Three rows in the comparison table decide whether a published tier is available to a regulated or security-reviewed buyer at all, and all three sit above Growth.
Single sign on is marked against Enterprise. VPC deployment is marked talk to sales. HIPAA and a business associate agreement, and a custom master service agreement, are both Enterprise rows. Enterprise access management appears as three groups on Growth and custom on Enterprise, and data retention settings are an Enterprise row entirely.
An SSH tunnel is the one security control that appears lower down, available from Growth. The practical shape is familiar from other categories: the volume ladder and the procurement ladder are different ladders, and a small team with a security review to pass reaches the quoted tier long before its event count suggests it should.
Support follows the same line. The FAQ states there is no dedicated support on the free tier, only a community Slack, that paid plans carry some level of team support, and that Enterprise adds an account manager and a dedicated Slack channel. Onboarding support is listed as up to six months on Enterprise.
The self-hosted route, and what it does and does not include
The FAQ answers the self-hosting question directly. The project is released under Elastic 2.0, the core data processing layer is described as the same for the Community and Enterprise editions, and the Enterprise edition adds reporting and clustering features built on top of the data plane. Running open source for event streaming means standing up and operating your own data plane, which the documentation describes as suited to highly technical data teams with platform engineering resources.
That is a genuine option and it is not a cheaper version of the managed product. It trades a subscription for engineering time, and the calculation only works for a team that already has the second thing.
The short version
There is a free tier at "250K Events/month" that includes a working pipeline, a Growth tier from $265 a month at "1 million events/month" with a selector up to 25 million, and a quoted Enterprise tier. Events are counted as data points, with a page load equal to one.
For a B2B outbound programme the event allowance is rarely what binds. Warehouse sync latency, Reverse ETL connection count, transformation limits and the absence of a development workspace bind first, and the Profiles and data applications, including attribution and identity resolution, sit on the quoted tier. The free tier stops processing after a second consecutive overage, and the FAQ describes overage terms for a plan the ladder no longer lists.
Price it on latency and capability rather than on volume, and confirm the overage terms in writing. When the missing piece is the flow of qualified conversations rather than the infrastructure to measure it, see what a first campaign produces against your own market.
Plan names, rates, allowances and comparison table rows above were read from rudderstack.com/pricing on 30 August 2026, in the currency and billing view it served. Vendor pricing moves. Verify current terms with the vendor before relying on them.
Frequently asked questions.
Frequently asked questions- How much does RudderStack cost?
- As published on 30 August 2026, the Free tier is $0 with 250,000 events a month, and Growth starts at $265 a month for one million events with a selector stepping to 3, 5, 7, 10 and 25 million. Above that the page directs to sales, as it does for Enterprise. Annual billing is offered with a stated 15 percent saving, and Growth carries a 30-day free trial.
- What counts as an event?
- The pricing FAQ defines it as a data point generated by a website, app, server or cloud application, and gives the example that a page loading generates a page call counting as one event. So the meter counts loads, clicks and server calls rather than users or sessions, which means your volume follows what you instrument rather than how large your audience is.
- What happens if I go over the event limit?
- It depends on the tier. On the free plan the FAQ states data processing stops after a second consecutive overage. On a paid plan it states the overage fee is the difference between the next tier's pricing and your current plan's, so an overshoot effectively charges the step up to the next band. Note the FAQ names a Starter plan that no longer appears on the ladder, so confirm the terms in writing.
- Which tier do I need for attribution?
- On the published comparison table, attribution sits inside the Profiles and Data Apps section, and every row there is marked available against Enterprise. The underlying event data lands in your own warehouse on any tier because the platform stores nothing, so a data team can model attribution directly. The Enterprise rows buy the packaged application rather than access to the data.
About the author.
Ben Carden is CRO at RevenueFlow, which builds and operates outbound revenue engines for B2B companies. Previously at Gartner Enterprise. Studied at London School of Economics.
Ben Carden · CRO
Connect on LinkedIn →Explore more.
Ready to scale your outreach?
We build GTM engines that book real meetings. See the receipts.
Related articles.
What RudderStack Is: A Customer Data Platform That Holds None of Your Data
RudderStack is warehouse-native, which its own docs define as storing and persisting nothing. What that changes about ownership, attribution and the exit cost.
Northbeam Pricing: Banded by Your Ad Spend, Quoted on Every Tier
Four tiers banded by your own ad spend, all four asking you to contact sales. Two print a figure anyway, and only one of those states a period.
ClickFunnels Pricing: The Meter Is Contacts and Emails, Not Traffic
Four published tiers, and visitors are unlimited on every one of them. What ClickFunnels actually meters, and the tier where webhooks and the API appear.
BigMarker Pricing: What the Vendor Publishes Instead of a Rate
BigMarker prints Request a Quote against all three plans. The structure it does publish, and the meter that caps attendance rather than registration.
Jotform Pricing: Four Meters, One Seat, and the Number Everyone Quotes Wrong
Every Jotform plan card carries four separate ceilings, two of them about submissions. Third-party explainers keep quoting the wrong one as the monthly limit.
B2B Lead Generation Companies Grouped by Pricing Model: What 15 Vendors Publish
Nine of fifteen B2B lead generation vendors publish a dollar figure and six publish none. The five pricing models behind the numbers, each figure cited to its page.