Time Machine

Time Machine lets you clone your organisation's own data into a private, isolated sandbox, then fast-forward that sandbox's clock to see exactly what happens — without ever touching your real customers, sending a real email or webhook, or creating a real charge.

What this does for you

Think of it as a safe rehearsal space for time-based billing behaviour. Instead of waiting for a real billing cycle to roll over to see what an invoice or a usage debit will look like, you create a sandbox (a full copy of your org's data in its own database), move its clock forward to whatever date you want to test, and inspect exactly what fired and what changed — with a guarantee that nothing in the sandbox can ever reach a real customer, post a real charge, or affect your live data.

Today, advancing a sandbox's clock runs one scheduled process: the daily usage-to-wallet debit (the same job that runs against your real data every day). Other time-based jobs — renewal invoices, credit expiry, trial-to-active transitions, dunning — aren't wired into sandboxes yet.

Who can use it

Time Machine is gated by both a feature flag and a set of permissions, so it may not be visible to you even as an admin.

• The feature must be turned on for your organisation — if you don't see Time Machine under Settings, ask your Kribana contact to confirm it's enabled.
• Viewing sandboxes, their timeline, and wallet state requires timeMachine.view.
• Creating a sandbox requires timeMachine.create.
• Advancing a sandbox's clock requires timeMachine.run.
• Destroying a sandbox requires timeMachine.delete.

These are ordinary, grantable permissions — your organisation's admin can assign them to any role from Users & Roles, the same way any other permission is granted.

Where to find it

• Settings → Customizations → Time Machine — the main entry point. The page is a three-step guided flow: Create, Advance, and Inspect.
• Directly from a Company or Subscription record — click the Time Machine button next to Edit on either detail page to jump straight in. Sandboxes clone your whole organisation, not just one company or subscription, so this is a shortcut to the same page rather than a scoped view.

How to use it

Once inside, a small clock reading in the top-right corner always shows your sandbox's current virtual time, so it's never ambiguous whether you're looking at a simulated moment or the real present.

1. Create (or resume) a sandbox. If your org doesn't already have one, click Create sandbox to start cloning your organisation's data — this usually takes a few seconds. Your org can have one active sandbox at a time; if one already exists, it's shown here instead of the Create button, so you can resume it or Destroy it to start fresh. A failed creation shows a Try again option.
2. Advance the clock. Once the sandbox is ready, drag the duration slider — 2 weeks, 1 month, 1 quarter, 6 months, 1 year, 18 months, or 4 years, defaulting to 6 months — or pick a specific date and time, then click Advance clock. You can only move the clock forward — a date at or before the current virtual clock isn't accepted.
3. Inspect the results. Review the sandbox's wallet balances and a Timeline of every event the advance produced; click any row for full details. Use Advance again to keep testing, or go back to the Create step to destroy the sandbox.

Tips / things to know

• Nothing that happens in a sandbox is visible anywhere else — it's a separate database, with its own clock, that never reads from or writes to your live data.
• If any action inside the sandbox would normally send a real email, webhook, or payment/tax provider call, it's automatically intercepted and blocked instead — you'll see a note if this happened during your last advance.
• Your sandbox isn't deleted automatically — destroy it yourself once you're done, especially since your org can only have one at a time.
• Advancing the clock currently runs only the daily usage-to-wallet debit — it doesn't yet simulate renewal invoices, credit expiry, trial/pause transitions, dunning, or tax/proration.
• There's no way to roll a sandbox back to an earlier point (no snapshot/restore) and no way to save a sequence of clock moves as a reusable scenario — destroy and re-create if you need a fresh start.
• A sandbox isn't cleaned up automatically after a period of inactivity — it stays until destroyed.