- Free allowance
- Free plan: 20,000 events per month with no credit card required; unlimited apps, EU or US data residency, built-in and live dashboards, session timeline and CSV export; there are no overage fees and past the limit analytics are paused until the start of the next month
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- free tier
- Identity
- emailno card, no phone
- Binding limit
- volume-quota20,000 events per month; past it analytics are paused until the start of the next month
- Evidence
- documented7 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-02checked 2026-11-01 (live); stale on 2026-12-02
| Free tier | Free plan: 20,000 events per month with no credit card required; unlimited apps, EU or US data residency, built-in and live dashboards, session timeline and CSV export; there are no overage fees and past the limit analytics are paused until the start of the next month unit requests; metered on request-count; The unit is the event: every call to the SDK's track function counts as one, and nothing is tracked automatically. The vocabulary has no events term, so requests is the nearest. The next plan is USD 10 a month for 200,000 events. |
|---|
| Price | none stated |
|---|
| Limits | - volume-quota (binding) 20,000 events per month; past it analytics are paused until the start of the next month source
|
|---|
| Binding | volume-quota The 20,000-event monthly cap is the only stated quota, and exceeding it pauses collection instead of billing. |
|---|
| Identity | email The pricing page states no credit card is required for the free plan; the sign-up page offers GitHub or Google sign-in, or a name and an email address that receives a magic link, in the EU or the US region. |
|---|
| Egress | Export to CSV is included on every plan; no export allowance or price beyond that is stated |
|---|
| Per-object cap | unverified: no per-event size is stated on the pages read |
|---|
| Retention | unverified: no retention period is stated on the pages read |
|---|
| Interface | unknown Events are sent by SDKs for popular platforms and read in the built-in dashboard or exported to CSV; no REST read API is named on the pages read, and the interface vocabulary has no term for an SDK-only service. |
|---|
| Tooling | SDKs for popular platforms, the dashboard and CSV export |
|---|
| Composes with | Usage events from a desktop or mobile app, up to 20,000 a month, kept in the EU or the US region. |
|---|
| Reliability | past 20,000 events a month analytics are temporarily disabled until the start of the next month; an email warns before the limit |
|---|
| Notes | Paid plans start at USD 10 a month for 200,000 events; the free plan is the lowest step of the same event ladder. |
|---|
| Evidence note | documented The plan, the overage rule and the sign-up methods are quoted from first-party pages. No account was opened, so retention and any later sign-up step are unverified: behind a sign-up. |
|---|
| Parsed numbers | |
|---|