What's new in NamiDB Cloud

• 7 days on Pro, 14 days on Scale: point-in-time restore now reaches any second of the last 7 days on Pro (was 48 hours) and the last 14 days on Scale (was 7 days). Nothing is deleted: the longer window fills up over the next days, and older times keep using backups as before.
• Enterprise windows by agreement: an Enterprise agreement can set point-in-time restore from 7 up to 30 days, never shorter than its base plan's.
• Scale backs up every 6 hours: scheduled backups on Scale now run every 6 hours, like Pro, with one a day kept 30 days and the others 48 hours. Point-in-time restore covers every second in between, so restores inside the window are as exact as before.
• Clearer storage billing: storage includes your data, your backups and your point-in-time restore history, all inside your plan's included storage. The temporary copies we make to run an export or for maintenance, and the export files themselves, no longer count toward your storage. This applies from today; earlier hours are unchanged.

• Restore to any second: on Pro (last 48 hours) and Scale (last 7 days), a point-in-time restore copies the database into a new one exactly as it was at the time you pick, with every change committed by then and none after. The recovery point objective inside that window is seconds instead of the backup interval.
• Older times still work: before the window, and on Free, a point-in-time restore uses the newest backup at or before the chosen time, as before, and says how far before that time its recovery point is.
• Exact recovery points for backups: every backup now records when its newest change was committed, so a restore from a backup states exactly what it holds, and a backup taken after the chosen time can still serve it when nothing changed in between.
• API: POST /api/v1/restores takes database and at for a point-in-time restore (the same as a point_in_time clone). Clones report recovery_source (restore_point or backup), and backups report source_created_at and, for point-in-time copies, as_of.

• Consistent exports: an export is a point-in-time snapshot of the database as of when it starts. Writes made while it runs are not included, so totals and relationships always match. manifest.json records the snapshot time (snapshot.taken_at).
• Indexes in `import.cypher`: full-text indexes and vector indexes (dimension and similarity function included) are recreated by the script instead of being listed as comments. Vector indexes with NamiDB-specific build options are marked as NamiDB only.
• Nodes with many relationships: a node with more relationships than one query may return is now exported in full instead of failing the export.

• Export ready alerts: when a database export finishes, the export.ready event now reaches your webhooks and the owners and admins chosen on the Alerts page. Whoever asked for the export keeps getting their own "export ready" email, once.
• Enterprise agreements everywhere: member seats, the sidebar's storage meter, the read-only databases banner, usage pages, plan-change emails and the management API's limits (and so the CLI and the Terraform provider) now show the limits of your agreement, not those of its base plan.
• Annual subscriptions: cancelling an annual subscription, from the console or the billing portal, now ends it when the year you paid for ends, like a downgrade.
• Sign-up with GitHub or Google follows the same rules as signing up with an email address.
• Terms and Privacy Policy: the Terms now describe annual billing and the credits and referral program, and the Privacy Policy describes support requests and their attachments and how long they are kept (3 years after the conversation ends).

• Slow-query log: statements sent over Bolt by Neo4j drivers now appear in a database's activity next to HTTP, MCP and console ones, with the same threshold and without their parameters.
• Running queries: listing or cancelling running queries (GET /v1/<database>/queries) no longer starts a database that is asleep; it simply has none running.
• Open transactions: revoking an API key, or removing an address from an IP allowlist, now also ends a Bolt transaction that is already open; the transaction is rolled back and the driver gets an error that says why.
• Error code access_banned (403): returned when NamiDB has blocked an address, an organization or a key for abuse. Contact info@namidb.com if you think it is a mistake.

• Management tokens through the API: an admin token can list, create and revoke management tokens (/api/v1/management-tokens). A new token acts for the same member, is never broader in scope and never outlives the token that created it, and every change is in the audit log.
• Running queries in the SDKs: the JavaScript and Python SDKs list the statements running on a database and cancel one (runningQueries / cancelQuery, running_queries / cancel_query). Cancelling a statement that already finished returns the new error code query_not_found.
• Point-in-time restores in the SDKs: restores.pointInTime (JavaScript) and restores.point_in_time (Python) restore a database as it was at a given time into a new database.
• CLI: namidb databases clone, namidb restores create <database> <new-database> --at <time> (an ISO 8601 time or how long ago, such as 2h), namidb tokens and namidb queries list | cancel.
• Terraform provider: new namidb_management_token and namidb_ip_allowlist_entry resources, a namidb_database data source, and clone_from on namidb_database to create a database as a copy of another one, from a backup or as it was at a point in time.

• More roles: Developer (databases, backups, read-write queries and API keys), Billing (plan, spend cap and invoices) and Viewer (read-only console), next to Owner, Admin and Member.
• SAML single sign-on on Scale and Enterprise: connect your identity provider, verify your email domains, map identity provider groups to roles, and optionally require single sign-on.
• SCIM 2.0 provisioning: create, update and deactivate members from your identity provider; deactivating someone ends their sessions. Owners are never removed through SCIM: an owner removes another owner in the console.
• IP allowlists: limit an organization, or a single API key, to the addresses you list, over HTTP, Bolt and MCP and in the console's query editor (ip_not_allowed otherwise). An organization's list also covers requesting and downloading exports, from the console and the management API.
• Sign-up protection: disposable email addresses and repeated sign-ups are refused.

• Pricing page at app.namidb.com/pricing: every plan's allowances, overage rates, spend cap and SLA side by side, with no sign-in needed. Picking Pro or Scale there carries the choice through sign-up to your billing page; nothing is charged until you check out.
• Annual billing: Pro ($190 a year) and Scale ($1,490 a year) can be billed once a year for 10 months of the base price. Usage past the allowance is still billed monthly.
• Support center in the console: open a ticket with a category, a severity and attachments, follow the conversation and reply by email. Response targets are shown in the console: Pro gets a first response within 1 business day; Scale gets priority support with 4 business hours for urgent issues.
• Enterprise: contact sales from the pricing page for custom limits, invoice billing with net terms, and security and legal reviews.
• SLA: Pro and Scale keep their 99.9% monthly uptime commitment.

• Service notices: planned maintenance and incidents now show as a banner in the console and are emailed to organization owners and admins, with the time window in UTC.
• Email preferences: product update emails are optional; turn them off in your account settings or with the one-click unsubscribe link in each one. Security, billing, service and legal notices always reach owners and admins.
• Subprocessor updates: anyone can subscribe on the Subprocessors page (with a confirmation email) to hear about new subprocessors and policy changes 30 days before they take effect.
• Welcome email with the shortest path to a first query, and emails when your role in an organization changes or you're removed from one.
• Changelog: this page, with RSS and Atom feeds.
• Credits: redeem credit codes from the billing page. Credits are taken off your next invoices, and Free organizations keep them until they choose a paid plan.
• Referrals: every organization has a referral link. When an organization you referred pays its first invoice, you both get a credit.

The new versions are dated November 2, 2026; you're asked to accept the Privacy Policy and Terms once when you next sign in.

• Privacy Policy: how sanctions checks work (country of the IP address at sign-up, sign-in and purchase; billing address and name at checkout, some reviewed by a person), that owners and admins get product-update emails they can turn off at any time, what we keep from the contact-sales form and from policy-update subscriptions and for how long, and that security-relevant logs are kept 90 days.
• Terms of Service: backups are kept in your organization's storage and may also be copied, encrypted, to separate backup storage; they help you recover and don't replace copies you keep yourself.
• Data Processing Addendum and Subprocessors: encrypted off-site copies of database backups are covered, and a backup storage provider is named on the Subprocessors page, with notice, before it receives any.
• Security: the same log retention, and a reminder to keep your own exports.

• Import: map the columns of a CSV, TSV, JSON or JSON Lines file to nodes and relationships, preview them and load them from the database page. Large files load in batches you can pause and resume, and rows that fail are listed at the end.
• Sample dataset: an empty database offers a small movies graph and a few guided queries to try.
• Export: download a database as JSON Lines plus an import.cypher script that loads it into NamiDB or Neo4j. Files stay available for 7 days, and you are emailed when they are ready. A suspended organization can still export its data.
• Clones: copy a database from its latest backup or a fresh snapshot into a new database.
• Point-in-time restore: restore a database as of a chosen time, from the newest backup taken at or before it; the console shows exactly which point you get.
• More frequent backups: Scale backs up every hour and Pro every 6 hours, with one backup a day kept 30 and 7 days.
• Bulk import in the SDKs: importNodes, importRelationships and bulkWrite (and their Python equivalents).

• Graph view: query results as a graph you can pan, zoom and expand, next to the table and JSON views. Export results as CSV or JSON.
• Schema browser: labels, relationship types, property keys, indexes and constraints, one click from the editor.
• Saved queries and history: save queries for your organization, reuse your own recent ones, fill parameters from a form, and use keyboard shortcuts.
• Activity: see the queries running on a database and cancel one, through the console or the API (GET /v1/<database>/queries). Slow statements are logged for 7 days without their parameters.
• Alerts: choose who is emailed when a backup fails, a restore finishes, an engine keeps failing, usage nears an allowance or a key is about to expire, and send the same events to your own signed webhooks.

• Management tokens: owners and admins create organization-scoped tokens (read, write or admin) under Settings → Management API, with two-factor authentication on. Every change a token makes is in the audit log with the token's name.
• REST API at app.namidb.com/api/v1, described by an OpenAPI document: databases, backups, restores, clones and point-in-time restores, exports, API keys, IP allowlists, usage, members, invitations and support tickets. Creates accept an Idempotency-Key.
• SDKs: ManagementClient in the JavaScript and Python SDKs.
• Coming next: the namidb command line tool (management, queries, an interactive shell and file imports) and a Terraform provider for databases and API keys, published to npm and the Terraform Registry.

• Audit log: owners and admins see every change in their organization (keys, databases, members, billing, backups, sign-ins) with time, actor, IP and user agent, filter it and export it as CSV. Events are kept for a year.
• API key rotation: replace a key with a grace period for the old one, and set a maximum key lifetime for the organization. Owners and admins are emailed 7 days and 1 day before a key expires.
• Abuse protection: a privacy-friendly proof-of-work check on sign-up, and on sign-in after repeated attempts. No third-party captcha.
• Browser hardening: a strict Content-Security-Policy with per-request nonces, and HTTPS-only, HttpOnly session cookies.

All of NamiDB Cloud's legal documents are published at app.namidb.com/legal:

• Terms of Service and Privacy Policy. When either changes, you're told at least 30 days ahead and asked to accept the new version once.
• Data Processing Addendum with the EU Standard Contractual Clauses, the UK Addendum, and Swiss and CCPA terms.
• Service Level Agreement: 99.9% monthly uptime for Pro and Scale, with service credits when we miss it.
• Acceptable Use Policy, Cookie Policy (strictly necessary cookies only, no analytics or advertising) and the Subprocessors list.
• Security page with our vulnerability disclosure policy and safe harbor, and a security.txt.

Organizations can now move from Free to Pro or Scale from the billing page. Each plan includes storage, write requests and read requests; usage past an allowance is billed at the plan's rates.

• Spend cap: on by default. With it on, usage past an allowance is never billed: writes (or reads) pause until the period resets. Turn it off to keep serving and pay overage.
• Plan changes: upgrades apply right away and are prorated; downgrades take effect at the end of the period, and nothing is deleted when you move to a smaller plan.
• Emails at 80% and 100% of an allowance, when a payment fails or needs confirmation, and before an annual renewal.
• Free plan: organizations idle for 7 days are paused after a warning the day before, and resume with one click. Pausing deletes nothing; an organization that stays paused for more than 90 days may be deleted, and only after 30 days' notice by email, as the Terms describe.
• Invoices, payment methods and tax IDs are managed in the Stripe customer portal.

• Teams: owners and admins invite people by email as owner, admin or member. Invitation links work once, for 7 days, for the invited address only. Change roles, remove members, leave, or transfer ownership; an organization always keeps an owner.
• Two-factor authentication with an authenticator app (a primary and a backup). Sensitive actions such as deleting an organization, changing keys, members or billing ask for it again.
• Require two-factor for everyone in an organization.
• Sessions: see where you're signed in and sign out one or all other sessions; a revoked session ends on its next request.
• Account settings: change your name, email (confirmed on both addresses) and password, and delete your account.
• Deleting an organization takes it offline at once and keeps it recoverable for 30 days.

Every database now answers queries at db.namidb.com, authenticated with your API keys.

• HTTP: send Cypher to https://db.namidb.com/v1/<database>/cypher.
• Bolt: connect any Neo4j driver to neo4j+s://db.namidb.com and pick the database by name.
• MCP: give AI agents a graph to read and write through the Model Context Protocol, with the same keys and limits.
• Query editor: run Cypher from the console and see the results as a table.
• Backups and restores: back up a database on demand on every plan, daily on paid plans, and restore any backup into a new database.
• Read-only keys are enforced on every protocol, and requests are metered the same way whichever one you use.

The first version of the NamiDB Cloud console is live at app.namidb.com.

• Accounts: sign up with email and password (with a confirmation code or link), sign in with a password or a magic link, and recover a forgotten password. GitHub and Google sign-in are available where enabled.
• Organizations: each one gets its own dedicated, isolated storage, set up the moment you create the organization.
• Databases: create and delete databases inside your organization; each is an isolated namespace in your organization's storage, so there is nothing to size or provision.
• API keys: read-write or read-only, optionally scoped to one database and with an expiry date. A key is shown exactly once; only a keyed hash of it is stored.
• Usage: storage and requests per hour, per day and per billing period.