12 docs tagged with "Self-Hosted"

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

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.

Configure environment variables, authorization, and security for your RushDB instance.

Complete reference for all RushDB environment variables.

Configure RushDB's graph backend — bundled Neo4j via Docker Compose, an existing Neo4j instance, or Neo4j Aura (BYOC).

Configure the relational database used by RushDB for project metadata, users, and API keys.

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.

How the RushDB NestJS application process works — ports, startup dependencies, static serving, health check, CLI, and resource requirements.

How RushDB stores data, enforces project isolation, and what to harden in production.

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.