Database pricing & limits
Managed Databases are pay as you go and billed hourly. You pay for the compute and storage the instance uses, at the same rates as dedicated Cell resources, plus a management fee while it runs. There is no minimum term.
How the price is calculated
| Part | Rate | Charged |
|---|---|---|
| Compute | $0.004 per vCPU-hour and $0.002 per GiB of memory per hour, plus the instance's 1 GiB system disk at the storage rate | While the instance runs |
| Storage | $0.00001536 per GiB-hour, about $0.011 per GiB per month | Always, including while the instance is stopped |
| Management fee | 30% of the CPU and memory cost | While the instance runs |
A stopped instance pays for its storage only. Monthly figures on this page use 730 hours. For example, a Nano instance (0.25 vCPU, 512 MiB) with 10 GiB of storage costs:
- Compute: 0.25 × $0.004 + 0.5 × $0.002 = $0.002 per hour, plus $0.00001536 for the system disk.
- Management fee: 30% × $0.002 = $0.0006 per hour.
- Storage: 10 × $0.00001536 = $0.0001536 per hour.
- Total: $0.00276896 per hour, about $2.02 per month.
The quote you see is the price you get
hubfly db create show a quote before you create or resize an instance, and that quote is authoritative. If prices changed between the quote and your confirmation, Hubfly space refuses the request (MANAGED_PRICE_CHANGED) and you get a fresh quote.Example monthly prices
| Size | vCPU | Memory | With 10 GiB storage (default) | Stopped, 10 GiB |
|---|---|---|---|---|
| Nano | 0.25 | 512 MiB | ≈ $2.02 | ≈ $0.11 |
| Small | 0.5 | 1 GiB | ≈ $3.92 | ≈ $0.11 |
| Medium | 1 | 2 GiB | ≈ $7.72 | ≈ $0.11 |
| Large | 2 | 4 GiB | ≈ $15.31 | ≈ $0.11 |
| X-Large | 4 | 8 GiB | ≈ $30.49 | ≈ $0.11 |
Each extra GiB of storage adds about $0.011 per month. A Nano instance with 1 GiB of storage is about $1.92 per month; a Medium instance with 100 GiB is about $8.72.
Sizes
| Preset | vCPU / memory | Suggested for |
|---|---|---|
nano | 0.25 / 512 MiB | Prototypes and small side projects |
small | 0.5 / 1 GiB | Hobby apps and staging |
medium | 1 / 2 GiB | Production apps with steady traffic |
large | 2 / 4 GiB | Busy production workloads |
xlarge | 4 / 8 GiB | Heavy queries and many connections |
- Custom sizes. 0.25 to 8 vCPU in steps of 0.25, and 256 MiB to 32 GiB of memory in steps of 256 MiB.
- Engine minimums. PostgreSQL needs at least 512 MiB of memory and MySQL at least 1 GiB, so MySQL starts at the Small preset. SQLite (libSQL) can run with 256 MiB.
- Storage. 1 to 500 GiB in whole GiB, 10 GiB by default. Storage can grow but never shrink.
You can change CPU, memory and storage later; see resizing.
Billing and your balance
Instances are billed from your account balance like other dedicated resources. If the balance runs out, Hubfly space stops database instances the same way it stops paid containers, and the instance shows why it stopped. After you top up, Hubfly space starts them again. Read Billing & Free Tier for how balances and usage work.
Limits
| Item | Limit |
|---|---|
| Instance name | 3–48 lowercase letters, numbers and hyphens, starting with a letter. It becomes part of the hostname. |
| Database name | Up to 63 lowercase letters, numbers and underscores, starting with a letter or underscore. Names such as postgres, mysql, sys, public, template0 and anything starting with pg_ or hubfly_ are reserved. |
| User name | Same characters as database names; up to 63 characters (32 on MySQL). |
| Access token name (libSQL) | 1–64 printable characters. |
| IP allowlist | Up to 64 IPv4 or IPv6 addresses or CIDR ranges per instance. |
| Export and import files | Up to 5 GB per file. Exports expire after 7 days. |
| Instances per account | A per-account limit applies to live instances. hubfly db engines shows yours. |
| Topology | One server per instance in one location chosen by Hubfly space. No replicas, high availability or point-in-time recovery. |
| Automatic backups | Coming soon. Use manual exports today. |