OneEnv
← All posts📤 Part 20 of 21

Your Data Can Walk Out the Door

ShareLinkedInX

The easiest way to trust a tool with your configuration is knowing you can leave with it. OneEnv ships two one-click workspace takeouts — a JSON bundle of every service's fully-resolved config, and a nine-sheet Excel workbook of the entire workspace — plus a data lifecycle that never deletes anything by surprise. Lock-in is a business model; it isn't ours.

Two takeouts, two audiences

JSON takeout
Machine-readable: every active service's resolved env config in its own export format — the irreplaceable part, decrypted and override-resolved exactly as the service would pull it.
Excel takeout
Human-readable: one workbook — services, resolved env values, masters, members, DB structure, API routes, validations, and billing, one sheet each.
Per-service export
Any single service's config as .env, shell, HOCON, or a custom template — the same endpoint CI pulls with a scoped token.
Owner/Admin gated
A takeout contains real secrets, so it's held to the same bar as every other privileged read.

Leaving is a flow, not a support ticket

Takeout
download everything
→
Archive
immediate, reversible
→
30-day grace
restore any time
→
Purge
explicit, permanent

Archiving a workspace hides it but destroys nothing, and restore is one click for thirty days. Only after that grace period can the Owner — nobody else, and never a background job — permanently purge it. The destructive action exists, but it is always explicit, always gated, and always preceded by the chance to take your data with you. The same principle shows up in billing: a lapsed trial reverts your capacity, it never deletes what you built.

Why we built the Excel one

Because the audience for "what's in our workspace?" is bigger than the people with API access. An auditor, a new lead, a compliance review — they get a workbook they can open, filter, and annotate, with secrets already resolved through the same approval-respecting pipeline the real exports use. Data freedom isn't just an offboarding feature; it's how the workspace explains itself to people outside the tool. More on the export pipeline itself in Export & Publish, In Depth.

ShareLinkedInX