Plans
Price, included pageviews, site limit, and retention for Starter, Pro, and Business, the trial, and what happens when you exceed your plan.
Three plans, all metered on pageviews. Every price and limit below is copied directly from the plan catalog mrkr's billing code reads from: nothing here is rounded or approximated.
The plan table
| Plan | Price / mo | Included pageviews / mo | Site limit | Retention | Overage |
|---|---|---|---|---|---|
| Starter | $5 | 100,000 | 3 | 1 year | $0.05 per 1,000 |
| Pro | $14 | 300,000 | 10 | 2 years | $0.05 per 1,000 |
| Business | $29 | 1,000,000 | Unlimited | 3 years | $0.05 per 1,000 |
The overage rate is identical on all three, so a higher tier never buys you cheaper excess traffic. What it buys is a larger included allowance, more sites, and a longer retention window. Pick the tier whose included allowance is close to your real monthly traffic and let overage cover the spikes.
The trial
The trial is paid, not free. Starting any plan charges a one-time $1 immediately and gives you 14 days of that plan in full. A card is required up front, and the $1 is a real charge rather than a hold. When the 14 days are up your card is charged the plan's monthly price automatically, and monthly from then on until you cancel.
Cancel before the 14 days end and nothing further is charged; the $1 is not refunded, since it paid for the days you had. There is no free tier to fall back to at any point.
What happens when you exceed your plan
Nothing stops. Every currently-offered plan carries a Stripe metered overage price, so going over the included allowance is a billing event rather than an ingest error: your pageviews keep being recorded in full and the excess is billed per 1,000 on your next invoice. Refusing to record traffic a customer is willing to pay for would destroy data that cannot be recovered afterwards, which is the whole argument for metering rather than blocking.
The single exception is a workspace grandfathered onto the retired free plan. That plan has no metered price in Stripe, so there is nowhere to bill its excess and its allowance is enforced as a hard ceiling: new events past it are silently not recorded (the tracker still gets a success response, so it doesn't retry) until the month resets or the workspace upgrades.
Site limits are enforced differently
Unlike the pageview allowance, the site limit is a hard cap on every plan: there's no metered "extra site" price. Creating a site is a rare, deliberate action, so refusing it synchronously with a clear error is the right trade; unlike ingest, there's no risk of silently losing a visitor's traffic by blocking it.
Quota enforcement also lags slightly by design: the over-quota check is cached for 5 minutes per site so ingest doesn't pay for a database aggregate on every single event. An upgrade clears that cache immediately, so a plan change takes effect right away rather than waiting out the cache window. If the quota check itself fails for any reason (a database or cache outage), it fails open: your events keep being recorded rather than risk dropping real traffic over an infrastructure hiccup.