Security overview
This page summarises how NamiDB Cloud protects your data and which controls are yours to use. The authoritative description is the Security page, which is also Annex II of the Data Processing Addendum.
What NamiDB does
- Isolation per organization. Each organization’s databases and backups live in their own storage bucket, and its queries run in an isolated engine dedicated to it, with memory and CPU limits per plan. An engine receives short-lived credentials that open only its own organization’s storage.
- Enforcement in the engine. Read-only keys, and organizations over a write allowance, are given a read-only credential, so the engine itself refuses writes on HTTP and Bolt alike.
- Encryption. TLS on every public endpoint (
app.namidb.com,auth.namidb.com,db.namidb.com, including Bolt on 7687, andstatus.namidb.com). Data is encrypted at rest by the storage provider. - Credentials stored as hashes. API keys and management tokens are stored only as keyed hashes, shown once, and revocable at any time; revocation reaches the data API within about two seconds.
- Account protection. Passwords of at least 10 characters, checked against known breached passwords; single-use email codes; sign-in that never reveals whether an address has an account; rate limits that fail closed.
- Access by staff. NamiDB staff do not access customer content in the ordinary course. Production access is limited to authorized personnel, with individual accounts and two-factor authentication, and is logged.
- Monitoring and response. Automated monitoring of every public endpoint, a documented incident process with updates on the status page, and notice to affected customers within 48 hours of a security incident affecting their personal data.
NamiDB does not hold SOC 2 or ISO 27001 certifications yet. Our storage, payment and email providers hold their own; see the Subprocessors page.
What you control
| Control | Where | Plans |
|---|---|---|
| Two-factor authentication for your account, and required for the whole organization | Account, Settings → Members | All |
| Roles for every member | Settings → Members | All |
| API key roles, database scopes, expiry, rotation and a lifetime policy | API keys | All |
| IP allowlists for the organization and per key | API keys | All (1 / 20 / 100 entries) |
| Audit log with CSV export | Audit log | All |
| SAML single sign-on, required SSO and SCIM provisioning | Settings → Single sign-on | Scale, Enterprise |
| Alerts and signed webhooks | Alerts | All |
| Session review and sign-out of other devices | Account → Sessions | All |
Sensitive actions (deleting an organization or account, changing email or password, API keys, members, billing, exports, webhooks) ask for your second factor again when you have one enrolled.
Your part
- Keep API keys in a secret manager or server-side environment; never ship read-write keys in browser or mobile code.
- Use read-only keys, database scopes and expiry wherever they fit; revoke keys you no longer use.
- Turn on two-factor authentication, and require it for the organization.
- Review members, roles and the audit log regularly.
Reporting a vulnerability
Email info@namidb.com with the subject “Security report”. The disclosure policy explains what is in scope and how quickly we respond. Test only against organizations and accounts you created yourself.