Guides
Plans and billing
What tested visitors are, what happens past the limit, and changing or cancelling a plan.
On LiftCanary Cloud you pay for the visitors in your experiments, nothing else. Feature flags, rollouts and their traffic are unlimited on every plan, analytics is included, and paid plans have unlimited seats. Prices are on the pricing page. A self-hosted installation (available on Enterprise) has every feature and no plan limits.
Tested visitors#
A tested visitor is someone who entered at least one experiment during the calendar month (UTC): an A/B, redirect or no-code test. They count once however many experiments they saw and however often they came back. Someone who browsed anonymously and then signed in counts once more as the signed-in user. Visitors who only get feature flags or rollouts don't count, and neither do events from visitors in no experiment.
Settings → Usage shows this month's count, per project, updated every few minutes. Admins get an email at 80% and at 100% of the plan, once each per month.
Plans#
| Plan | Tested visitors a month | Projects | Seats | Experiments at once | Paid features |
|---|---|---|---|---|---|
| Free | 25K | 1 | 3 | 2 | None |
| Starter | 100K | 5 | Unlimited | Unlimited | Results by segment, funnels, guardrails, integrations |
| Growth | 500K | Unlimited | Unlimited | Unlimited | Results by segment, funnels, guardrails, integrations |
| Scale | 2M | Unlimited | Unlimited | Unlimited | Results by segment, funnels, guardrails, integrations |
| Enterprise | By agreement | Unlimited | Unlimited | Unlimited | Results by segment, funnels, guardrails, integrations, hybrid deployment |
Seats are members plus pending invitations. Experiments at once counts experiments running at the same time across the organization's projects; drafts, ended experiments and personalizations don't count, so you can prepare as many as you like. Starting one past the limit (with Start, a scheduled start, or by giving its rule traffic) is refused until another ends; a scheduled start that finds no free slot stays a draft and editors get an email. Fair use on every plan: on average up to 1,000 events per tested visitor a month across the organization, far above what a website sends. Free features include flags, rollouts, A/B, redirect and no-code tests, the visual editor, goals, audiences and full statistics.
Going over#
Flags and experiments always keep working for your visitors: usage never changes what they see.
- Free: past the limit (with a 10% margin), new experiment results stop being recorded until the 1st of the next month, or until you upgrade.
- Paid plans: results keep being recorded. If you're over two months in a row, we'll ask you to move to a plan that fits.
Upgrading, changing and cancelling#
Admins and owners manage the plan under Settings → Plan & billing. The first upgrade opens a secure checkout; closing it, or a checkout that can't open, brings you back to the same page with nothing charged (a declined card can be retried in the checkout). After that:
- Changing plan or billing period applies at once; the price difference for the rest of the period is charged or credited.
- Cancelling (Move to Free) takes effect at the end of the paid period, and can be undone until then.
- Invoices, payment method, billing address and tax number are under Invoices & payment method, in the payment provider's portal.
- Moving to a smaller plan deletes nothing: projects, experiments, results and the team stay. Experiments already running keep running. You just can't add projects, seats, funnels, guardrails or integrations, or start experiments, beyond the new plan until you upgrade again.
When a feature needs a paid plan#
Adding something your plan doesn't include answers 402 with error: "plan_required" (or "plan_limit" for projects, seats and experiments at once), the feature or limit, and the plan that includes it. The dashboard shows the same message with a link to upgrade. Clearing or turning off a paid feature never needs a plan.