Pricing
Platform · Operate

Change anything without a ticket.

New price in Kenya. A World Cup pass. A gateway swap two weeks before launch. Your team does it, today, and knows it works before anyone feels it.

Your catalog is versioned, like software

Clone the live catalog as a draft. Change what you need. Publish when it's ready.

  • Published versions lock their commercial configuration, so nobody edits a live price by accident
  • Names and descriptions stay editable — pricing and plan rules don't
  • Every version keeps its history: who created it, when it went live, when it was archived
v4 — LiveLive
v5 — DraftDraft
v3 — ArchivedArchived
Seven checks before anything goes live

Every catalog version is validated before you can publish it.

The kind of mistake that takes a quarter to notice, caught in a second.

  • At least one active product
  • Every active product has at least one active plan
  • Every active plan has at least one active price
  • Every active plan is linked to an entitlement package
  • No duplicate product codes
  • No duplicate plan codes
  • No duplicate price for the same plan, country and currency
Watch next month happen, today

Create a virtual clock. Attach a subscriber to it. Move time forward.

The renewal charges. The payment fails. The retry ladder runs on schedule. The invoice is generated. The dunning email sends. The events fire.

All of it in seconds, in sandbox, tagged as simulation — so you can test a four-step retry ladder in an afternoon instead of finding out on renewal day.

Worth asking any vendor: how long does a price change take, and how do you test a renewal? On most platforms the first answer is a support ticket and the second is "wait a month."

The standing work runs itself

Nobody has to remember to run any of it.

Renewal scans

Run on their own schedule, every time.

Lifecycle sweeps

Suspend access automatically when grace periods expire.

Dunning execution

Runs on schedule, no manual chasing.

Price migrations

Each job has a failure threshold that disables it automatically if it starts misbehaving — instead of letting it run wrong all night.

Set the policy once

Configure it per environment, and every subscription follows it.

  • What happens when a payment fails — grace period, pause, continue, cancel, expire at period end
  • Who's eligible for a free trial
  • How long past due is too long
  • Password rules and session length for your subscribers
Get Started

See a renewal run in seconds.

Book a walkthrough with our team — we'll fast-forward a virtual clock through a real renewal and retry ladder, live.

Request a Demo