Plans are sized by virtual user-minutes. One virtual user running for one minute. Every plan includes Web Vitals capture, session video, and full logs for every user. Tell us roughly what you'll run; we'll point you at the right tier.
For small teams trying performance testing as part of their release process.
For SaaS and e-commerce teams where performance affects revenue and you test every release.
For mid-market teams running serious cross-region load tests as a core engineering practice.
We don't gate the reporting features behind tiers. Whether you're on Starter or Scale, every test produces the same forensic report. Web Vitals captured at load, session video for every user, network and console logs you can search across millions of rows.
LCP, INP, CLS, FCP measured by every virtual user, every plan.
Every virtual user's session recorded and replayable.
Full waterfall and console output per session, every plan.
Reusable user journeys with parameterised data. Same builder, every plan.
Project-level rules for cookie banners and modals. Always included.
Configure browser conditions per run. No surcharge per environment.
One virtual user running for one minute equals one VU-minute. A test that ramps 1,000 users up to peak and holds them for 60 minutes is roughly 60,000 VU-minutes. We measure exact runtime per user, not target concurrency, so partial-minutes get prorated.
We'll let you know before you hit your monthly cap. You can either upgrade or buy a top-up pack. We don't auto-bill overages without your say-so.
Demo-led onboarding. We'd rather walk you through the product on your site and give you trial credits afterwards than throw you at a signup page cold. Book a demo →
Because the right number depends on your testing volume and the conversation is worth having properly. We're a small team. You'll talk to someone who can actually answer your questions.
Yes. Every plan can be billed monthly or annually, and annual contracts get a meaningful discount versus monthly.
Take the most ambitious test you can imagine running monthly (peak concurrency, peak duration, peak frequency), multiply through, and add a 20% buffer for retries and ad-hoc tests. We'll size the right tier with you on the demo call and check your math.