Sandbox
Synthetic preview only. The hosted, isolated API sandbox is not available yet. This portal uses fixed fictional fixtures; the registration preview runs in your browser with no network API calls.
| Fixture | Country | Currency | Time zone |
|---|---|---|---|
| ACME-LK · Synthetic Lanka Company | LK | LKR | Asia/Colombo |
| ACME-SG · Synthetic Singapore Company | SG | SGD | Asia/Singapore |
The fictional publisher is ACME Developer Studio and its fictional contact is Maya Sen at maya@acme.example. Examples do not represent real companies, people or tax assertions. Do not enter real personal, financial or customer data, keys or credentials.
Preview reset policy
Section titled “Preview reset policy”Mock registration records live only in page memory. Reloading, navigating away or closing the page clears them. Reset preview session clears all registrations and selections immediately and restores the fixed ACME form defaults. No backend, cookies, localStorage, sessionStorage, IndexedDB or service worker stores registration data. Starlight may retain the light/dark theme preference separately.
There are at most five mock registrations per page session. The reset control affects only your current page. It does not reset an API, another developer’s fixtures or a real installation.
Future hosted sandbox
Section titled “Future hosted sandbox”The planned sandbox must have separate issuer/audience, client identities, credentials and data; no production copies, mounts, backups or connections. A reset will restore a published fixture version within the requesting app’s authorized boundary, with reset/seed audit and containment tests.
Outbound email and payments will be stubbed; webhooks will use isolated allowlisted sinks. Retention, reset cadence, fixture version and availability will be published with that service. No nightly schedule or persistence guarantee is promised here. Kubernetes policy alone is not evidence of isolation; infrastructure and egress controls still need proof.

