Skip to content

Support

Where to ask

ChannelFor
Support center in the console (Support)Everything about your organization: databases, queries, connections, billing, access
Email info@namidb.comWhen you can’t sign in, security reports, legal and privacy questions
GitHubQuestions and bug reports about the open-source engine and Cypher, with the community
status.namidb.comIs 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.

PlanSupport levelUrgentHigh, normal, question
FreeCommunity supportBest effortBest effort
ProEmail support1 business day1 business day
ScalePriority support, handled first4 business hours1 business day
EnterpriseEnterprise support, with a named contactAs set in your agreementAs 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:

    SeverityUse it when
    UrgentProduction is down or data is at risk
    HighProduction is impaired: errors or slowness for some requests
    NormalSomething is wrong, but you can work around it
    QuestionHow-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-id header, or requestId / request_id on 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.

Other help