inetGeek docs
Guides

Estimate a monthly cost

What each provider charges at your volume, and how to read the answer

estimate_monthly_cost answers one question: at this monthly volume, what does each provider that publishes a per-volume price charge? It covers web analytics (pageviews or events), email (emails sent) and auth (monthly active users).

Get the volume from the project

Use real numbers from the project's own analytics, logs or dashboards, and state the unit. A vendor that bills in events is not billing in pageviews: pass events_per_pageview when you compare the two (a vendor's page usually says how it counts; the generated caption shown beside a converted line repeats it).

Reading a line

$15.00/mo — Fathom Analytics — 100,000 pageviews: $15/mo, covers up to 100,000 pageviews — … — read 2026-10-25, https://usefathom.com/pricing

The plan, the fee, what it covers, the inetGeek page, the date the vendor's pricing page was read, and the URL. Lines are sorted cheapest first.

Reading what is not a plain price

  • A range ($500–$2500/mo): the vendor prints a per-block rate and does not say whether a part block is prorated or billed whole. Both ends are shown.
  • + $49 one time: a one-off licence, shown beside any monthly fee.
  • Fair use / unlimited: the plan has no number to print; the line says which.
  • Marginal rates: where a vendor's per-unit rate falls with volume, the line lists the rates and the cost applies each to its own band.
  • Quote-only: above a volume the vendor prints no price and sells by quote; the line names the plans and the threshold.
  • Another currency: named, never converted.

What it will not do

It does not know taxes, annual discounts or a vendor's own definition of its unit beyond what its page states, and it does not extrapolate past the highest band a vendor prints. A provider with no readable per-volume price is listed with what its own pricing page says, not compared.

Everything it computes is inetGeek's arithmetic on published rates, not a quote. The generated rows behind it are at /usage-pricing.json.

On this page