The dashboard sandbox lets you click through the entire operator dashboard on an isolated copy of your catalog and sample data. It’s for learning the product, demoing it, and rehearsing a change before you do it for real.
This is different from the API sandbox, which is for developers testing an integration with krnl_sb_ keys. This one is the in-dashboard safe mode for operators.

​
What’s safe about it

Isolated data

You see mirrored sample plans and subscriptions — never your real subscribers.

No real network

Toggling a line or provisioning a port only changes simulated state — no switch is touched.

No real billing

Bill runs and payments are replayed against sample data; no card is charged.

No real emails

Triggered events (bounce, recover, outage) go to an in-sandbox outbox — never to real inboxes or Zammad.

​
Enter the sandbox

1

Start it

Click Enter sandbox at the bottom of the sidebar. The dashboard swaps to the sandbox context and shows a persistent banner so you always know you’re in it.
Enter sandbox control

Enter sandbox from the sidebar

2

Explore

Every page works as normal — subscribers, plans, billing, network — but on sample data. Nothing you do here reaches production.
Sandbox control panel

The sandbox panel

3

Fire event triggers

From the sandbox panel, trigger scenarios — a failed payment, a recovery, a line going down — to see how the dashboard and comms respond, safely.
4

Time-travel

Advance the sandbox’s clock to see what happens across a billing cycle or a dunning window without waiting real days.
Sandbox triggers and time-travel

Time-travel and triggers

5

Reset or leave

Reset returns the sandbox to a clean sample state. Leave sandbox takes you back to your real dashboard — your production data was never touched.
The sandbox is the best place to follow the Add a subscriber and Build your catalog guides for the first time.