CEDX Sandbox · Developer & low-code
Sandbox clones the estate so you can break it: 320 environments with isolation and leak scores, seed packs classed by PII, clone operations priced per run — and idle burn flagged by name before the invoice arrives.
The top alert is the one most tools would rather not print: billing full QA publicly reachable — leak 91, 42 unmasked PII columns. A sandbox tool earns its keep by finding that first.
Runs on demo data — Northline Env Ops is the demo workspace, not a customer.
What it is
320 environments with type, kind, status, gigabytes, isolation and leak per row. sbx-auth-full-qa-38 is a full data-copy at 282GB, ready, isolation 29, leak 98 — the row tells you the size of the problem and its shape. Sleeping and archived states keep the bill honest.
96 seed packs, each classed Raw, Masked or Safe, with rows, apply success and staleness. 18 raw packs carry a prefer-mask flag; seed-auth-masked-v5.7 holds 3.49M rows at 99% apply success. What is in a seed is a column, not an assumption.
220 clone operations with source, destination, type, status, gigabytes and cost. cl-4710 cloned a synthetic source into a full sandbox at 430GB for $275; 31 operations failed and are listed for retry. The window moved 24.8TiB at an average of 51 minutes.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/sandbox.
01 — Overview
186 active of 320 environments, isolation health at 72%, mask coverage at 50% — and the alerts that make those numbers worth reading: a partner preview with a shared secret on a public URL, 15 full copies idle over 14 days still on hot compute, and a stale orders preview whose production data is 120 days old.
02 — Sandboxes
1–25 of 320 with owner, size and scores. The failures are as visible as the ready ones: sbx-billing-full-train-55 shows Failed at 501GB. High leak ≥55 catches 82 environments — a filter chip, not a quarterly review.
03 — Seeds
Seed packs version like code — seed-auth-raw-v2.7 next to seed-auth-safe-v3.8 — with the PII class deciding where each may land. The stale column names its days: 179 for the catalog pack, on the row.
04 — Clones
Clone operations read like a ledger: prod-mirror into a payments preview at 150GB for $65, main-branch into a report branch at 51GB for $30. Running, failed and cancelled states are all on the table — including cl-4359, the failed EU catalog refresh from the overview's alerts.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Owns the estate of clones: 186 active, 11 on standby, and the 15 idle full copies still burning hot compute that the overview names.
186 active · $21K MTD
Owns the seed catalog: which packs stay raw, which get masked, and why 68 packs have gone 30 days without an apply.
96 seed packs · 18 raw
Runs suites against clones — and reads a failed seed apply as the cause of a red run before blaming the code.
220 clone ops · 31 failedThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
Data enters as a versioned pack classed Raw, Masked or Safe — 96 packs, 18 raw with a prefer-mask flag on the row.
An operation copies a source into a typed environment: 220 ops in the window, 24.8TiB moved, 51 minutes on average, priced per run.
Every environment gets a boundary score — sbx-auth-full-qa-38 at isolation 29 with leak 98 is the outlier the average of 72% is hiding.
Idle burn gets named: 15 full copies idle over 14 days on hot compute, and 11 standby code-runs costing $612 a month while paused.
One record
Sandbox works because there is one estate to clone: the same data, runtimes, suites and deploy tiers, reproduced with their scores attached.
Deploy's staging and sandbox tiers are these environments — and its 96 preview hosts clone from the same machinery.
CEDX TestE2E suites run against cloned data: a failed seed apply explains a red suite before the code does.
CEDX FunctionsCode-run sandboxes meter the same runtime — 48 in the estate, 11 paused and still costing $612 a month.
CEDX TablesMasked seed packs are how table data reaches a clone without its PII — 3.49M rows at 99% apply success.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your first clones
Sandbox with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/sandbox. It runs on demo data from the Northline Env Ops demo workspace.
An exposure score per environment built from public URLs, unmasked PII columns and shared secrets. The billing full QA clone scores 91 with 42 unmasked PII columns — and 82 environments sit at 55 or above, a filter chip away.
Three: Raw, Masked and Safe. 18 raw packs carry a prefer-mask flag; the masked catalog runs to 3.49M rows at 99% apply success. The class decides where a pack may land, and the table shows it on every row.
Priced per operation: 220 ops in the window sum to $11K across 24.8TiB, with the largest single clone at $275 for 430GB. Standby code-runs add $612 a month while paused. All of it is on screen, none of it is a price list.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then ask which of your clones currently holds unmasked production data.