Documentation
ShrouDB docs
Install the server, connect your app, and find the reference for each engine.
ShrouDB is a security server you run alongside your application. Your app calls it to encrypt data, store secrets, manage users, and check permissions. The server is called Moat, and each feature is an engine inside it that you turn on in the config file. Clients connect over HTTP or the RESP3 wire protocol, directly or through the TypeScript, Python, Go, and Ruby SDKs.
Start here
Install
Homebrew, Docker, binary, or source.
Quickstart
Encrypt a value and store a secret in about five minutes.
Architecture
How the server, engines, and storage fit together.
Moat reference
Config file, access tokens, HTTP and RESP3.
Engines
| Engine | Use it to | Docs |
|---|---|---|
| Cipher | Encrypt customer data before it reaches your database | Read → |
| Sigil | Add sign-up, login, and sessions | Read → |
| Keep | Get database passwords and API keys out of .env files | Read → |
| Veil | Search data you've encrypted | Read → |
| Stash | Store user files you can permanently delete | Read → |
| Chronicle | Answer “who accessed this, and when?” | Read → |
| Sentry | Decide who is allowed to do what | Read → |
| Forge | Issue TLS certificates for your internal services | Read → |
| Courier | Notify people whose contact details you store encrypted | Read → |
Deployment paths
ShrouDB Cloud
Managed platform · free tier
We run the server. Same API and SDKs as self-hosting.
ShrouDB Moat
Self-hosted · binary or Docker
You run the server on your own infrastructure, so keys and data stay on your network.