Skip to content

Storage, limits and lifecycle

Each database has a storage limit, shown on the Overview tab as Storage Used. DockHive checks usage every few minutes and warns you as you approach the limit. Plan for headroom: a database that fills its storage may become read-only until you free space or raise the limit.

In the console you choose the storage when creating the database. To change it later, use the API (100 MB to 1 TB):

Terminal window
curl -X POST "https://api.dockhive.io/api/v1/databases/$DB/resize?region=$REGION" \
-H "Authorization: Bearer $DOCKHIVE_API_KEY" \
-H "Content-Type: application/json" \
-d '{"storage_limit_mb": 2048}'

Billing is based on the storage you actually use, not the limit you set. See Usage and overage.

Free Tier Developer Pro Scale
Databases 10 20 60 Custom
Total database storage 500 MB 50 GB, then $0.10 per GB-month 150 GB, then $0.10 per GB-month Custom

Counts and storage add up across all regions. On the Free Tier, the storage cap applies to the storage limits you allocate, and every database needs at least 100 MB. So the 500 MB lets you run up to 5 databases at the minimum size, even though the count limit is 10. Larger storage limits mean fewer databases.

When you reach a limit, the console and API tell you, for example “Your Free plan includes 10 databases. Delete a database or upgrade your plan to create another.”

Each database runs with a fixed amount of memory and CPU suited to its engine.

Use Stop, Start and Restart in the database’s header (or the matching API calls). A stopped database keeps its data; its storage still counts.

Click Delete, type the database name and confirm. Deletion is immediate and permanent: the data, all backups, firewall rules and the hostname are removed. Take a copy first if you need one.

Running SQL in the console, database users and roles, imports and exports, query metrics and password rotation are coming soon.