SLA
This page summarises the Service Level Agreement. The binding text is the SLA on app.namidb.com/legal/sla, part of the Terms of Service; where they differ, it wins.
The commitment
99.9% monthly uptime for organizations on Pro and Scale (and Enterprise agreements on top of them), measured per organization in each calendar month (UTC). Free has no SLA.
99.9% allows about 43 minutes of downtime in a 30-day month.
What is covered
The data plane at db.namidb.com: the HTTPS query API
(/v1/<database>/cypher), the MCP endpoint and Bolt on port 7687, for
databases in the ready state.
The console, sign-in, backups and restores, usage reporting and billing are run to the same standard but are not covered by credits.
How downtime is counted
A downtime minute is one in which, for your organization, either no valid
request could connect, or more than 5% of valid requests failed with a
server-side error caused by NamiDB (an HTTP 5xx, including
engine_unavailable, control_plane_unavailable and engine_starting once
the cold-start budget is used up, or the Bolt equivalent).
- A request that succeeds after the database wakes from idle is not a failure, even when the first response is slower.
- A minute with no valid requests is not a downtime minute.
- Requests refused by your own limits, keys or settings (
4xx, rate limits, the spend cap) don’t count. - Planned maintenance announced at least 48 hours ahead on the status page or by email doesn’t count, up to 4 hours per month.
- The full list of exclusions (for example, failures outside NamiDB’s control, force majeure, or fees past due) is in the SLA.
Service credits
A percentage of that month’s fees for the organization (subscription plus usage, excluding taxes):
| Monthly uptime | Pro | Scale |
|---|---|---|
| Below 99.9%, at least 99.0% | 10% | 10% |
| Below 99.0%, at least 95.0% | 25% | 25% |
| Below 95.0% | 25% | 50% |
| Most credit in one month | 25% | 50% |
Credits apply to future invoices of the same organization and have no cash value.
How to claim
Email info@namidb.com with the subject “SLA claim” within 30 days after the end of the affected month, with:
- the organization’s slug and the affected databases;
- the dates and times (UTC) of each period of downtime;
- evidence: request ids (
x-request-id), error codes, and logs.
Status and incidents
Live status, incidents and planned maintenance: status.namidb.com.