Event tracking & ingest
Dual MTU + event metering means a viral week or a noisy SDK can trip either ceiling, and overages bill at 1.2x without warning.
What people actually say
✕Amplitude meters MTUs and events independently — a product with 5,000 power users firing 3,000 events each blows the 10M event cap while sitting well under the user cap, and both ceilings overage independently.
Source: Quackback, Amplitude Pricing 2026 ↗✕Overages are charged at 1.2x the contracted rate, and Vendr's deal data shows real overage rates landing 20-50% above the negotiated per-MTU price — bot traffic or campaign spikes turn into surprise invoices.
Source: Vendr, Amplitude pricing & plans 2026 ↗✕Reviewers describe the pricing model as confusing and hard to forecast — costs scale unpredictably with MTUs, so rapidly scaling teams routinely blow their monthly budget.
Source: Userpilot, Amplitude Pricing 2026 ↗
Event ingest is a Snowplow or Rudderstack collector landing into your own Postgres (or ClickHouse once you outgrow it), with dbt models living in your repo. No MTU counter, no event meter, no 1.2x overage multiplier — your bill is RDS plus the EC2 it takes to ingest.