> For the complete documentation index, see [llms.txt](https://oten.gitbook.io/drive-support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oten.gitbook.io/drive-support/concepts-in-1-minute/drive-vs-vault.md).

# Drive vs Vault

Oten Drive gives you two kinds of encrypted storage. Both are end-to-end encrypted; they differ in how you use them.

**Drive** — your everyday encrypted storage.

* One Drive per user, unlocked with your **device PIN**.
* Familiar file-and-folder experience (like an ordinary cloud drive).
* Share **individual files and folders** with other people.
* No Shadow Layers — it's built for convenience.

**Vault** — an advanced, security-first container.

* You can create **many** vaults (personal, work, per-project).
* Each vault is opened with its own **password**.
* Every vault can hold **Shadow Layers** for plausible deniability.
* Sharing is at the **whole-vault** level.
* Each vault has its own independent key hierarchy — compromising one vault does **not** expose another.

|               | Drive                | Vault              |
| ------------- | -------------------- | ------------------ |
| How many      | One per user         | Multiple per user  |
| Unlock with   | Device PIN           | Per-vault password |
| Sharing       | File & folder level  | Whole vault        |
| Shadow Layers | No                   | Yes                |
| Feel          | Familiar cloud drive | Security-first     |

**Why it matters:** Drive is the default landing experience — good for the files you use all day. Vaults are opt-in, for data that needs stronger separation or the deniability of [Shadow Layers](/drive-support/shadow-layers/how-shadow-layers-work.md).

> Both live behind the same encryption. The difference is how you unlock them and how much control-versus-convenience you want.