Your Workspace's Own Encryption Key

Our Commitment MountDev Ops is built security first. Your business data belongs to you, and you can export all of it at any time. We never use analytics or tracking of any kind inside MountDev Ops.

Your workspace has its own encryption key, made when your workspace was made. It protects the keys and passwords you save here, such as the keys for your connected services, and the files you upload. It is random, it is not worked out from anything shared, and no other workspace has it. No key or password held by MountDev Ops can open more than one workspace.

Where It Lives

The key is kept only inside your workspace, in your data region. It is never shown on any screen, never sent to Cascadia or anywhere else, and never put in a log, an export, or an error message. Only your workspace's own code uses it, to seal a saved key when you save it and to open it when a connection needs it.

See Where It Stands

Status (owners only; action core.account_key.status) shows whether your workspace has its own key, the key's short id, and how moving older saved keys to it is going (counts only). It never shows the key.

Change the Key

Rotate (owners only; action core.account_key.rotate) makes a new key and seals every saved key and password again with it, checking each one. The old key is kept only until the last one is checked, and then it is overwritten. If a check fails, nothing is lost: the saved value and the old key stay as they were, and the status shows how many failed. Rotating your key touches no other workspace.

If the Key Is Lost

Because the key lives only in your workspace, a lost key means saved keys cannot be read. MountDev Ops then asks you plainly to enter them again. Your workspace's key is part of your workspace's own backup, inside your data region, and nowhere else.

Good to Know

• Rotating the key does not change any key at an outside service. If you want a new key from a service, make it there and save it here.
• Files and search tags made before your workspace had its own key keep opening: the key they used is held inside your workspace now.
• AI agents and API keys cannot see or rotate the key.