docs / guides

botdb cloud

The hosted relay botdb syncs through by default, what it stores, accounts, plan limits and how to leave.

botdb cloud is a hosted relay at https://botdb.dev, the same origin as this site. It’s where your databases sync unless you choose a folder or your own relay. It’s free during the beta.

Getting an account

There’s nothing to sign up for. botdb login picks botdb cloud by default and creates an account for your vault:

botdb login                  # vault, recovery phrase, botdb cloud account
botdb create movies          # syncs through botdb cloud

The account token is stored in your vault catalog (encrypted like everything else) and in ~/.botdb/config.json, so every device restored with botdb login --restore uses the same account. If you logged in with another remote, add botdb cloud later:

botdb remote add cloud --default     # new databases sync there
botdb remote add cloud -d movies     # an existing database too

cloud is shorthand for botdb cloud’s URL anywhere botdb takes a remote. Set BOTDB_CLOUD_URL to point it somewhere else.

Your account

botdb cloud

account    acc_6qg6xlnnzlhdpker
plan       free
databases  2 of 20
storage    3.4 KB (50.0 MB per database)
relay      https://botdb.dev
           (vault)          2.8 KB
           movies           672 B

Your vault catalog counts as one database. Storage is the encrypted size on the relay: the change log plus the latest snapshot, which replaces old changes after a week. Daily backups don’t count.

Backups

botdb cloud keeps a daily encrypted backup of every database for up to a month: the last 7 days plus one a week for 4 weeks. List them with botdb backup ls --remote and restore one with botdb backup restore --remote -d <db> --at <time>. See Cloud backups.

Limits

When a database would go over its storage limit, pushes fail with a quota error; your local copy keeps working. Creating more databases than the plan allows fails with plan_limit. Paid plans with more room will come later.

The account is only needed to create databases on botdb cloud. Anyone you invite syncs a shared database without an account of their own, and it counts against yours.

What it can see

Only ciphertext and metadata: database ids, padded sizes, timing and IP addresses. Every change is encrypted and signed on your device. See the threat model.

Leaving

Every device holds a full copy, so moving away loses nothing:

botdb remote add https://relay.example.com --default   # or a folder path
botdb remote add https://relay.example.com -d movies
botdb remote rm cloud -d movies
botdb rm movies && botdb trash empty --remote --yes    # deletes the remote copy too

botdb export --type sqlite gives you a plain SQLite file at any time.

How it runs

botdb cloud runs on Cloudflare Workers. Each database is a Durable Object holding its encrypted change log; its latest snapshot and daily backups are encrypted files in Cloudflare R2, and accounts live in Cloudflare D1. It speaks the same protocol as botdb relay, so the CLI treats it like any self-hosted relay.