From reddb-cloud
Use the reddb.io managed cloud — sign up, provision a RedDB instance, get connection strings, and connect from any driver. Invoke when the user mentions reddb.io, app.reddb.io, the managed/cloud/hosted offering, "create a database in the cloud", billing/plans, or wants to move from self-hosted RedDB to managed.
How this skill is triggered — by the user, by Claude, or both
Slash command
/reddb-cloud:reddb-cloudThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
`reddb.io` is the **managed** offering for RedDB. You sign up, provision an instance from the dashboard, and get a connection string — same `.rdb` format, same query languages, same drivers as self-hosted, but operated for you (provisioning, backups, scaling, upgrades).
reddb.io is the managed offering for RedDB. You sign up, provision an instance from the dashboard, and get a connection string — same .rdb format, same query languages, same drivers as self-hosted, but operated for you (provisioning, backups, scaling, upgrades).
This skill is intentionally a skeleton. It covers what you do on the cloud side. For everything that happens after you have a connection (writing queries, picking models, embeddings, ASK), invoke the
reddbskill — the engine is identical.
| Want… | Use |
|---|---|
| Production database without running ops | reddb.io |
| Edge / CLI / embedded in a single process | Self-hosted embedded (@reddb-io/sdk, Rust RedDB::open) |
| Quick dev / CI / local Docker | Self-hosted Docker (docker-compose.min.yml) |
| Multi-team production with budget for ops | Either — managed is faster to start, self-hosted is cheaper long-term |
| Hard data-residency or air-gapped | Self-hosted (or ask cloud team about dedicated/BYOC) |
When in doubt, recommend starting on reddb.io for prod workloads and embedded/Docker for dev — the file format matches, so you can move either way without dump/restore.
That's it. Everything else (query languages, models, ASK, vectors) is engine-side — see the reddb skill.
The cloud exposes the same transports as self-hosted RedDB. The dashboard shows you the URIs to use:
# HTTP / gRPC over the cloud gateway
red://<your-db>.reddb.io
https://<your-db>.reddb.io
# Postgres-wire (RedWire) — works with psql, pgx, node-postgres, psycopg2
postgresql://<user>:<password>@<your-db>.reddb.io:5050/reddb
For remote connections, use @reddb-io/client (not @reddb-io/sdk — that one spawns a local binary).
import { connect } from '@reddb-io/client'
const db = await connect('red://<your-db>.reddb.io', {
token: process.env.REDDB_TOKEN, // from the dashboard
})
await db.insert('users', { name: 'Alice' })
const { rows } = await db.query('SELECT * FROM users')
psql "postgresql://<user>:<password>@<your-db>.reddb.io:5050/reddb"
Works with pgx, node-postgres, psycopg2, Prisma, Drizzle — anything that speaks Postgres v3 wire. SQL only through this path; for Cypher/Gremlin/SPARQL/NL/ASK, use the HTTP or gRPC endpoints.
curl -X POST https://<your-db>.reddb.io/query \
-H "authorization: Bearer $REDDB_TOKEN" \
-H "content-type: application/json" \
-d '{"query": "SELECT * FROM users LIMIT 10"}'
The HTTP API surface matches self-hosted (/query, /collections/*, /ai/*, /changes, /backup/*) — see the reddb skill's CHEATSHEET.md.
You authenticate with a token (from the dashboard), not by configuring a vault yourself. Treat the token like any other secret:
REDDB_TOKEN) or a secrets manager.prod, staging, ci).What you still own:
reddb skill)./ai/credentials on your instance just like self-hosted (see reddb skill's AI.md).These change over time and are owned by the marketing/billing site — don't memorize, point users to the dashboard:
If the user asks "how much does it cost" or "what region is available" — refer them to the live pricing page rather than guessing.
Same .rdb file format across embedded, server, Docker, and cloud. Two practical patterns:
Self-hosted → cloud: export from your local server (POST /backup/trigger), then import via the cloud dashboard (or ask the cloud team about direct migration tooling).
Cloud → self-hosted: request a backup export from the dashboard, then red restore --from <archive> --path ./data.rdb against a fresh self-hosted server.
There's no schema migration step in either direction — the format is identical.
reddb skill. The engine is the same; don't duplicate that knowledge here.@reddb-io/client for remote, @reddb-io/sdk for local); then check token / region; then escalate to the cloud team.EMBEDDED_ONLY from @reddb-io/sdk → you used the embedded SDK against a red:// cloud URI. Switch to @reddb-io/client.psql connects but Cypher/Gremlin/SPARQL/ASK fail → RedWire is SQL only. Use HTTP /query or gRPC for the other languages.Searches MemPalace before answering questions about past work, people, projects, or prior decisions. Returns verbatim stored content instead of guessing from model memory.
Guides Payload CMS config (payload.config.ts), collections, fields, hooks, access control, APIs. Debugs validation errors, security, relationships, queries, transactions, hook behavior.
Implements vector databases with Pinecone, Weaviate, Qdrant, Milvus, pgvector for semantic search, RAG, recommendations, and similarity systems. Optimizes embeddings, indexing, and hybrid search.
npx claudepluginhub reddb-io/skills --plugin reddb-cloud