Kliv
    Test before you ship

    Test your whole store before you take a cent

    Build a complete commerce backend with simulated money and no Stripe account, then fast-forward time to watch a year of renewals, trials, and failed payments play out in seconds. You see exactly what your customers will experience — long before they live it.

    Pricing
    Test your whole store before you take a cent

    The Sandbox

    A full store, with simulated money

    Every Kliv store starts in the Sandbox — a complete, working commerce backend that uses simulated money. Checkout, subscriptions, refunds, even failed payments all run exactly as they will for real customers. There's nothing to sign up for and no risk of charging anyone by mistake. Pay with test cards, prove out your whole store, and know that anything that works here will work the same way when you go live.

    Time-travel testing

    Fast-forward through the future of your store

    Some of what matters most in a store happens over time: a trial ends next week, a subscription renews next month, a card fails and gets retried for days. Fork a disposable Scenario, drag a timeline, and watch all of it happen in seconds. Try it — drag a year of this small store's life:

    Jan 1 · day 0
    $19 collected1 receipts0 emails
    today+3 months+6 months+9 months+1 year
    • New subscription · $19.00Maya Lindqvist — Pro · $19/moJan 1

    An illustration with a scripted store. In the real Sandbox, this is your actual store — your plans, your emails, your customers — running on simulated money.

    What a rehearsal shows you

    Drag the timeline and a year happens. Here is what that year contains — every beat something you'd otherwise discover live, with real money and a real customer watching.

    Week 2

    The trial converts

    A test customer signs up on day one. On day fourteen the trial converts: the charge lands, the receipt goes out, the plan's features open. You watch the whole handoff instead of assuming it.

    March

    The renewal nobody touched

    The subscription renews on schedule. The invoice is right, the entitlements stay open, and no one had to remember anything — which is the point of an engine.

    May

    A card expires

    The renewal fails. Retries begin on a schedule, and the recovery emails go out — the exact emails your customer would receive, on your templates. Access narrows the way your policy says, not all at once.

    June

    …and recovers

    The customer follows the recovery link and fixes the card. Access reopens, the subscription continues — churn that never happened, and you watched the machinery that prevented it.

    August

    The mid-year upgrade

    The customer moves up a plan mid-cycle. Fair proration splits the invoice — and you can check the math yourself on the invoice the Sandbox produced.

    October

    A cancellation, on schedule

    Someone cancels. The gates close on the schedule your policy sets — at period end, not mid-promise — and the record of the relationship stays intact.

    Year end

    Every invoice accounted

    Twelve months of receipts, renewals, recoveries, a refund that waited for your approval before money moved — all inspectable, all free, because none of the money was real. This is what you know before your first customer that most stores learn after.

    See what customers experience before they live it

    No more shipping billing changes and hoping. Watch exactly what happens when a card fails, a trial ends, or a subscription renews — and fix it while it's still simulated money. And because the Sandbox is the same engine as your live store — same catalog, same entitlements, same emails — what you rehearsed is exactly what ships.

    Common questions

    Is this Stripe's test mode?

    No — simpler. The Sandbox is Kliv's own simulated-money environment: nothing to sign up for, no Stripe account, no API keys. Checkout, subscriptions, dunning, and refunds run exactly as they will live, on money that isn't real.

    What carries over when I go live?

    The store you rehearsed is the store that ships: catalog, prices, entitlements, email templates, policies. Going live swaps simulated money for your connected Stripe account — Kliv carries your catalog over and walks you through the connection.

    Can I make payments fail on purpose?

    Yes — that's half the point. Fail a card at checkout or at renewal and watch the retries and recovery emails do their work. The unhappy paths are the ones worth rehearsing.

    How fast is a year?

    Seconds. Simulated time is a control you hold: jump to the next renewal, the end of a trial, or twelve months out — the engine runs every event in between, in order.

    Can my team rehearse too?

    Yes — the Sandbox is your real app in a rehearsal environment. Invite your team and let them shop, subscribe, cancel, and request refunds the way customers will.

    Is the Sandbox the same thing as Kliv's testing?

    They're neighbors with different jobs. The Sandbox is where you rehearse the business — money and time. Kliv separately writes and runs unit and scenario tests that verify the app itself, continuously. See Testing & quality for that half. Testing & quality →

    Build it. Test it. Then go live.

    Start in the Sandbox — there's nothing to sign up for.

    See how the Sandbox works