Product overview

Cyphra provisions dedicated Neo4j Community instances on AWS. Each database you create maps to its own Kubernetes namespace and Helm release.

Creating a database

From the dashboard, choose a name, region, and size. The control plane enqueues a provisioning job; status moves from requested → provisioning → ready (or failed with events).

Connecting with Bolt

When the instance is ready, copy the Bolt URI and credentials from the detail page. Use any Neo4j driver or the Cyphra TypeScript ORM from your application.

Lifecycle

You can restart, rotate the admin password, or delete an instance. Delete is asynchronous and removes Kubernetes resources before marking the record deleted.

MVP limits

• Single AWS region in early access (expandable later).
• No automatic scheduled backups yet (manual / roadmap).
• Billing integration is optional; quotas may be enforced by plan.