Plans and limits
Every organization is on one plan. The plan sets what is included each month, what overage costs, and the limits below. Prices and how billing works are on Billing and pricing; the live price list is app.namidb.com/pricing.
Plans at a glance
| Free | Pro | Scale | |
|---|---|---|---|
| Price | $0 | $19 / month, or $190 / year | $149 / month, or $1,490 / year |
| Storage included | 2 GB (hard cap) | 100 GB | 1 TB |
| Write requests / month | 100,000 | 1,000,000 | 10,000,000 |
| Read requests / month | 1,000,000 | 10,000,000 | 100,000,000 |
| Overage | none: usage stops at the cap | $0.025 / GB-month, $6 / M writes, $0.50 / M reads | $0.02 / GB-month, $5.50 / M writes, $0.45 / M reads |
| Spend cap | always on | on by default | on by default |
| Databases | 2 | 20 | 100 |
| Scales to zero after | 10 idle minutes | 30 idle minutes | 60 idle minutes, or keep warm |
| Idle pause | after 7 days without activity | never | never |
| Scheduled backups | none (on demand only) | every 6 hours | every hour |
| Backup retention | 3 days | 48 hours, one a day kept 7 days | 48 hours, one a day kept 30 days |
| Point-in-time restore | from backups | to the second, last 48 hours (then from backups) | to the second, last 7 days (then from backups) |
| SSO (SAML) and SCIM | ✓ | ||
| IP allowlist entries per list | 1 | 20 | 100 |
| Support | Community, best effort | Email, first response within 1 business day | Priority, 4 business hours for urgent issues |
| SLA | none | 99.9% monthly uptime | 99.9% monthly uptime |
Enterprise is an agreement on top of Pro or Scale: custom allowances,
databases, rate limits and query timeouts, invoice billing with net terms,
response targets in the agreement, and help with security and legal reviews.
While an agreement is in force, its limits are the ones NamiDB applies and
shows everywhere: member seats, the storage meter, usage pages, banners,
plan-change emails and the management API’s limits (and so the CLI and the
Terraform provider). Contact sales.
What counts
- Storage: the bytes in your organization’s storage (databases, their restore-point history and their backups), sampled every hour and averaged over the month.
- Write request: one Cypher statement that changed data.
- Read request: any other statement served.
Requests count the same over HTTP, Bolt, MCP and the console’s query editor.
Requests refused by a limit (rate limit, spend cap, paused organization) are
never counted. The Usage page shows each meter against the allowance, and
GET /usage returns the same numbers.
Limits on every plan
| Limit | Free | Pro | Scale |
|---|---|---|---|
| Requests per second (per organization) | 25, bursts of 50 | 250, bursts of 500 | 1,000, bursts of 2,000 |
| Concurrent queries (per organization) | 8 | 64 | 256 |
| Query timeout | 10 s | 30 s | 60 s |
| Open Bolt sessions (per organization) | 64 | 512 | 2,048 |
| Console import file | 10 MB / 100k records | 100 MB / 1M records | 250 MB / 2.5M records |
The same on every plan:
| Limit | Value |
|---|---|
| HTTP request body | 2 MiB |
| Query result | 64 MiB |
| Active API keys | 50 per organization |
| Active management tokens | 25 per organization |
| Management API | 300 requests per minute per token |
| Webhooks | 10 per organization |
| Saved queries | 200 per organization |
| Members | no limit |
Details, headers and per-hour budgets for backups, restores and exports: Rate limits.
Changing plans
- Free → paid: an owner, admin or billing member picks the plan on Billing and completes checkout. It applies at once.
- Upgrade between paid plans applies at once, prorated, and is invoiced right away.
- Downgrade takes effect at the end of the billing period. Nothing is deleted: databases past the new limit become read-only (see Databases).
- Cancel returns the organization to Free at the end of the period.