Which Stealth Analytics Plan Fits My Event Volume and Number of Sites?

Stealth Analytics charges by total event volume across your whole portfolio, not by domain — so the number of sites you run never changes your bill. Pick a plan by matching your combined monthly events and your retention and custom-event needs: Free ($0, 5,000 events, 30-day retention, 2 custom events per project) for hobby projects, Indie Hackers ($14/mo, 50,000 events, unlimited retention, 10 custom events) for projects with real traction, and Pro ($39/mo, 250,000 events, unlimited retention, 50 custom events) for scaling SaaS and ecommerce.

The three plans side by side

The only things that scale with price are event volume, retention, and the custom-event ceiling per project. Everything else — unlimited sites, full CSV exports — is identical across tiers.

Why site count doesn't decide your plan

The pricing page states it directly: "We do not charge you per domain. Our usage based buckets cover your entire portfolio. Track one site or fifty, it all counts toward the same limit."

That means a single 5,000-event bucket covers every property you own. If you run five small sites that each generate 900 events a month, you're at 4,500 total and still on Free. If one site alone pushes 6,000 events, you've outgrown Free regardless of how many other domains you have.

The practical consequence: consolidate your thinking. Add up events across all sites, workers, and backend systems before choosing a tier.

What counts as an event

Stealth Analytics is built around raw event ingestion, not just pageviews. The homepage describes sending telemetry "from your website, your background worker, your payment funnel, or that robotics project in your garage," and notes you can "bypass the browser completely and hit our edge workers directly" via a standard JSON POST request.

So your event count isn't just traffic. It includes:

• Frontend pageviews from the 0.7 KB script
• Backend system events from your server
• Custom conversions and funnel steps
• Any other POST payload you send to the edge endpoint

If you're tracking server-side database processes or payment funnel steps alongside web traffic, those all draw from the same bucket. A site with modest traffic but heavy backend instrumentation can burn through events faster than raw pageview counts suggest.

Matching your situation to a plan

Free — hobbyists and side projects. The page labels it "Perfect for hobbyists." Choose it if your combined monthly events stay under 5,000, you only need 30 days of history, and two custom events per project covers your tracking. The 30-day retention is the real constraint here: if you want to compare this month to six months ago, Free won't have the data.

Indie Hackers — projects with traction. At $14/mo you get 10x the events (50,000), unlimited retention, and 10 custom events per project. The jump to unlimited retention is the meaningful upgrade — it's what lets you keep historical baselines. Pick this if you've outgrown 5,000 events, need long-term data, or your custom-event definitions have grown past two per project.

Pro — scaling SaaS and ecommerce. $39/mo covers 250,000 events, unlimited retention, and 50 custom events per project. This is for portfolios where event volume is genuinely large — high-traffic sites, or products instrumenting many distinct conversion and backend events.

How to estimate before you commit

1. Count events per site. For web traffic, estimate monthly pageviews. For backend events, count how often each tracked process fires per month.
2. Add them all up. Remember every site, worker, and funnel counts toward one shared limit.
3. Check your custom-event needs. Count how many distinct named events you want per project — the Free tier caps this at 2, Indie Hackers at 10, Pro at 50.
4. Decide on retention. If you need history beyond 30 days, Free is out.
5. Start on Free and upgrade when you cross a threshold. The page shows an "Upgrade" path, so you can begin at $0 and move up as volume grows.

Common sticking points

• Assuming per-site pricing. The most common miscalculation is budgeting per domain. It's one pooled bucket — fifty sites cost the same as one at equal total volume.
• Forgetting backend events. Server-side and funnel events share the same limit as pageviews. Teams that only count browser traffic often underestimate.
• Overlooking the custom-event cap. Event volume and custom-event count are separate limits. You can be well under your event ceiling and still hit the per-project custom-event cap.
• Treating 30-day retention as enough. If your reporting needs year-over-year or even quarter-over-quarter comparisons, the Free tier's 30-day window will force an upgrade regardless of volume.

If you're unsure, start on Free, watch your actual event consumption for a month, and let the real number — not a guess — tell you whether Indie Hackers or Pro is the right fit.