Support
Where to ask
| Channel | For |
|---|---|
| Support center in the console (Support) | Everything about your organization: databases, queries, connections, billing, access |
| Email info@namidb.com | When you can’t sign in, security reports, legal and privacy questions |
| GitHub | Questions and bug reports about the open-source engine and Cypher, with the community |
| status.namidb.com | Is something down right now? |
Response targets
Targets are for the first response, in business hours: Monday to Friday, 9:00 to 18:00 (UTC−5), excluding weekends.
| Plan | Support level | Urgent | High, normal, question |
|---|---|---|---|
| Free | Community support | Best effort | Best effort |
| Pro | Email support | 1 business day | 1 business day |
| Scale | Priority support, handled first | 4 business hours | 1 business day |
| Enterprise | Enterprise support, with a named contact | As set in your agreement | As set in your agreement |
A ticket opened outside business hours starts counting at the next opening. Targets are goals for how quickly a person answers, not resolution times; uptime is covered separately by the SLA.
Opening a ticket
In the console: open Support and fill in the ticket form. With the API:
POST /support/tickets (see the
management API).
-
Category: Databases & queries, Connections, drivers & SDKs, Billing & plans, Account & access, Security, Feature request, Something else.
-
Severity:
Severity Use it when Urgent Production is down or data is at risk High Production is impaired: errors or slowness for some requests Normal Something is wrong, but you can work around it Question How-to, guidance, nothing is broken -
Database, when one is concerned.
-
Attachments: up to 3 files of 4 MB each (8 MB in total): images, PDF, text, logs, CSV, JSON or Cypher files.
Every member of the organization sees its tickets. You are emailed when support replies, and you can answer from the console or by replying to the email. A resolved ticket reopens when you reply; one nobody answers for 14 days after it was resolved is closed.
What to include
The fastest tickets to solve include:
- the request id (
x-request-idheader, orrequestId/request_idon SDK errors) of a failing request; - the error code and the time (with time zone);
- the database name and how you connect (HTTP, SDK and version, Neo4j driver and version, MCP client);
- the Cypher statement, with parameters redacted if they are sensitive.
Never send API keys, management tokens or passwords: support never needs them, and never asks for them.