| An ordinary cloud | NMTS | |
|---|---|---|
| Who can read your files | The provider holds the keys and can open them. | Only you. Files are encrypted in your browser before they leave your device, and the key never leaves it. |
| What the account needs | An email address, a name and a password. | One NMTS key. No email address, no name. |
| Where the files are | On the provider's own servers. | On the Walrus public storage network, in encrypted pieces. NMTS keeps only the encrypted list of names and where the pieces are, with sizes and times. |
| What you pay, and to whom | A subscription to the provider. | Nothing to NMTS. You buy storage for a period from the network from your own wallet; free credits pay the first amount. |
| If the service disappears | The files go with it. | An open-source recovery program rebuilds them from the network with your NMTS key and the recovery list you saved. |
| An AI agent using it | Through the provider's API under your own account, where offered. | A command-line tool and an MCP server. An agent gets its own AI account under yours, with the same encryption. |
| Source code | Closed. | The encryption engine, the tool and the recovery program are open source. The server and the web app are not. |
| If you forget the secret | A password reset by email. | There is none. Lose the NMTS key and the recovery kit, and the files cannot be opened by anyone. |
NMTS is not decentralised as a service: one developer runs one server in front of a public storage network. The storage is spread over many operators; the service is not.