Building Eventra · Part 3 of 102 min read

How Eventra is priced: three plans, hard limits, one dashboard

  • buildinpublic
  • saas
  • pricing
  • product
FREE$0100k events / month1 project2 membersPRO$291M events / month8 projects per workspace20 membersENTERPRISECustom10M+ events / monthUnlimited projectsUnlimited membersThe same full dashboard on every plan

Eventra has three plans (the current limits are always on the pricing page): Free with 100,000 events a month, Pro at $29 a month with 1,000,000 events, and Enterprise starting at 10 million events a month. This post explains how the plans work and the decisions behind them.

The order of work

The billing engine came before the pricing page. I wrote it in the third week of the project, February 15 to 17: usage tracking per workspace, limits, lock states, and a cron job that sends alerts as a workspace approaches its quota. The pricing page followed on March 6.

The engineering problems came first: count usage atomically, never lose events, handle a workspace that reaches its limit. The numbers themselves are my estimates of what small, medium and large products send.

The three plans

  • Free: 100,000 events a month, one workspace, one project, one API key, two members.
  • Pro, $29 a month: 1,000,000 events, 8 projects per workspace, 10 keys per project, 20 members.
  • Enterprise: 10,000,000 events a month and more, unlimited projects, keys and members. Limits above 10 million events are agreed individually.

On April 1 I revised the limits and reworked billing so that a full month can be cancelled. Enterprise used to say "unlimited events" on the page. It now says "10M+", which states what the plan includes without promising an unbounded volume on finite hardware.

Every plan gets the same dashboard. Nothing is locked behind a paid tier. Free workspaces see dead, declining and never-seen features, unique users and the event stream, exactly as everyone else does. Plans differ only in volume and seats.

Hard limits

When a workspace reaches its monthly event limit, ingestion stops. There is no overage billing.

I chose this so that nobody receives an unexpected bill. A traffic spike, or a bug in client code that calls a tracking function in a loop, should never turn into a charge the customer did not plan for. The trade-off is that a fast-growing workspace hits a limit and has to upgrade, instead of quietly paying more.

eventsmonthmonthly limitingestion pauses$0 extrano surprise bill
When a workspace reaches its monthly limit, ingestion pauses. There is no overage charge.

Upgrades by email

To move to Pro, write to billing@eventra.dev with the workspace and the plan you want, and the plan is switched. Payment integration will be added when there is demand for self-service checkout. Until then, upgrades by email keep the product simple and the limits exact.

The Free plan needs no card, so the easiest way to judge the limits is to create a free workspace and look at your own numbers.