dbdock init and backups upload straight to your quota — you never create a bucket or paste an access key.
DBDock Storage needs a signed-in account. Run
dbdock login first. It’s available on Pro and Business plans, with a small free-tier allowance for trying it out.How it works
The CLI never holds the storage bucket’s credentials. Every upload and download goes through a short-lived presigned URL that the DBDock backend issues for your account only:dbdock backupwrites the finished backup to a temp file.- The CLI asks the backend for a presigned upload URL. The backend checks your quota and scopes the object to your account’s private prefix.
- The CLI uploads directly to storage using that URL, then removes the temp file.
dbdock restorereverses it with a presigned download URL.
Setup
init activates managed storage for your account and shows your current quota. The written dbdock.config.json is just:
.env.
Everyday use
Quotas
Usage is measured from what’s actually stored, so CLI and dashboard backups both count. Quota by plan:
When a backup would push you over quota, the upload is refused before anything is stored. Free up space with
dbdock delete or dbdock cleanup, or upgrade your plan.
When to use it
- You want backups offsite without running your own bucket.
- You don’t want storage keys living in config files or CI secrets.
- You already pay for DBDock and would rather not add a separate storage bill.
When to use your own bucket instead
- You need backups in a specific region, account, or compliance boundary you control.
- You want to keep more data than your plan’s quota allows.
- You have existing lifecycle or replication rules on your bucket.
init.
See also
dbdock storage
Check your usage and quota.
dbdock account
See your plan and limits.

