14 docs tagged with "Deployment"

Deploy RushDB on AWS EC2, Google Cloud Compute Engine, or Azure Virtual Machines with cloud-init or manual Docker Compose.

Back up and restore a self-hosted RushDB instance (Neo4j + SQL metadata).

Compare RushDB's three deployment models — Managed, BYOC (Bring Your Own Cloud), and Self-Hosted — with a feature matrix, decision guide, and step-by-step migration path.

Use your own Neo4j or Aura database as the RushDB data store — keep data in your cloud account while using the full RushDB API.

Run RushDB locally with Docker Compose (full stack) or a single docker run command against an existing Neo4j instance.

Clone the RushDB repository and run the platform locally with pnpm dev — Neo4j and PostgreSQL start in Docker while the NestJS API and dashboard run as local Node.js processes.

Deploy RushDB on Kubernetes using the official Helm chart — values reference, Neo4j wiring, ingress, and persistence.

Run RushDB on your machine. Choose between Docker, running from source, or a Kubernetes Helm chart.

System requirements and software dependencies before deploying RushDB to a remote server.

Create projects, configure per-project embedding models, invite team members, and verify SDK connectivity on a self-hosted RushDB instance.

Deploy RushDB to a remote server. Choose your cloud provider or run Docker on any Linux machine.

Deploy RushDB on your own infrastructure with Docker Compose, connect your own Neo4j instance, and configure embedding support.

Deploy RushDB with provider templates for self-hosted environments.

Common RushDB self-hosting failures and how to fix them.