Sep 24
Usage-Based Billing
Implement a billing system based on actual usage. Details will be added later after discussing with the team.
In Progress
Jan 30, 2026
Thanks for the breakdown! Quick clarification — in the example with 20k events/day (7.3M/year), that's under the 12M annual allowance (1M/month × 12). Where does the $13.01 "Overage Storage" come from? Is that for data retention beyond a default period, or am I missing something?
Jan 30, 2026
Yes, it’s a bit confusing. The overage rate is $0.40 per 1M stored events per month, and excess events are charged proportionally per day based on how long they remain stored. Example: Daily price per 1M events is $0.40 ÷ 30 ≈ $0.0133, so 100 excess events cost 100 × ($0.40 / 1,000,000) ÷ 30 ≈ $0.00000133 per day. Month 1: Day 1 you store 1,000,000 events (no overage). Days 2–30 you store 1,000,100 events, meaning 100 excess events for 29 days. Overage cost: $0.00000133 × 29 ≈ $0.0000386. Month 2: You already have 1,000,100 events stored for the full month (30 days). Overage cost: $0.00000133 × 30 ≈ $0.0000399. In short: you only pay for events above the limit, and only for the days they remain stored—small overages result in extremely small charges.
Jan 19, 2026
Retention limits, you can set your own boundaries based on time or total event count, ensuring you only pay for the data you actually need. Simple, Scalable Pricing: - Base Subscription: Includes 1M events per month. - Overages: $0.40 per million events (per month) for anything over your limit. Example Calculation: If you average 20,000 events per day on an annual plan: Total Annual Events: 7.30M Base Subscription: $12.00/year Overage Storage: $13.01/year Total Annual Cost: $25.01
For now, we’re working on usage-based billing. We’ll add all relevant details later. At the moment, there are no limits on number of sites or events.