Licensing & Third-Party Services
RushDB Cloud combines RushDB software with storage infrastructure and optional integrations. The exact service boundary depends on whether you use managed cloud, BYOC, or self-hosted deployment.
This page is an engineering reference, not legal advice. Review each applicable license and provider agreement before production use.
RushDB Software Licenses
| Component | License | Notes |
|---|---|---|
| Documentation | Apache License 2.0 | Source for this documentation site |
| TypeScript / JavaScript SDK | Apache License 2.0 | Client library published as @rushdb/javascript-sdk |
| MCP server and agent skills | Apache License 2.0 | Packages published as @rushdb/mcp-server and @rushdb/skills |
| RushDB platform core and dashboard | Elastic License 2.0 | Review the ELv2 limitations before redistributing or offering the platform as a managed service |
| RushDB Cloud | Commercial managed service | Your subscribed plan and applicable service terms govern hosted usage |
Runtime Services
| Service | When it participates | Configuration or reference |
|---|---|---|
| Neo4j and APOC Core | Required graph backend. Use the bundled deployment, an existing Neo4j instance, or Aura through BYOC. | Neo4j & Aura |
| SQLite or PostgreSQL | Required SQL metadata store for users, workspaces, projects, tokens, OAuth sessions, and access grants. SQLite is the zero-config self-hosted default; PostgreSQL is appropriate for cloud deployments. | PostgreSQL / SQLite |
| OpenAI-compatible embedding endpoint | Optional managed embeddings for semantic search. The configured provider receives text selected for embedding. | RUSHDB_EMBEDDING_BASE_URL, RUSHDB_EMBEDDING_MODEL |
| OpenAI-compatible chat completions endpoint | Optional relationship suggestions. The configured provider receives a compact ontology containing labels, properties, sampled values, and existing relationship patterns. | RUSHDB_LLM_BASE_URL, RUSHDB_LLM_MODEL |
| SMTP provider | Optional confirmation, password reset, and workspace invitation email. | MAIL_HOST, MAIL_USER, MAIL_FROM |
| Google and GitHub OAuth | Optional dashboard login providers. | GOOGLE_CLIENT_ID, GH_CLIENT_ID |
| reCAPTCHA | Optional login and form abuse protection. | SERVICE_CAPTCHA_KEY |
| External billing service | Optional cloud billing enforcement. | BILLING_SERVICE_URL, RUSHDB_BILLING_SECRET |
| Stripe Checkout | Optional dashboard checkout integration. | VITE_STRIPE_PUBLIC_KEY |
Models and OpenRouter
RushDB does not hardcode one model vendor into the graph engine. Embeddings and relationship suggestions call OpenAI-compatible endpoints configured by the deployment:
RUSHDB_EMBEDDING_BASE_URL=https://openrouter.ai/api/v1
RUSHDB_EMBEDDING_MODEL=qwen/qwen3-embedding-8b
RUSHDB_LLM_BASE_URL=https://api.openai.com/v1
RUSHDB_LLM_MODEL=gpt-4.1-mini
OpenRouter is one supported endpoint option. OpenAI, Azure OpenAI, Ollama, and other compatible providers can be used as well. Provider-specific model availability, data handling, billing, and terms apply.
Omit the embedding variables to disable managed embedding indexes. Omit the LLM variables to disable automatic relationship suggestions. External embedding indexes remain available when your application supplies vectors directly.
Responsibility by Operating Model
| Concern | RushDB Cloud | Cloud with BYOC | Self-hosted |
|---|---|---|---|
| RushDB API and dashboard operations | RushDB | RushDB | Your team |
| Neo4j account and graph infrastructure | RushDB | Your team | Your team |
| SQL metadata infrastructure | RushDB | RushDB | Your team |
| Optional model endpoint selection | Cloud configuration | Cloud configuration | Your environment variables |
| Third-party provider terms | Apply where enabled | Apply where enabled | Apply where enabled |
See Environment Variables for the complete self-hosted configuration surface.