Databases
Run Postgres, MySQL, or Redis on an isolated Cube with reserved RAM and disk. Full root, its own kernel, and resources that are never oversold.
Cubes from $2.92/moNo credit card to sign up
Why run this on a Cube
Every line here is enforced by the platform rather than left to you: its own kernel per Cube, RAM and disk reserved 1:1, and full outbound access while nothing reaches in until you open a port — each one IP-allowlistable.
Reserved RAM and disk
Databases love predictable memory and I/O. On a Cube every GB is reserved 1:1 and never thin-provisioned, so your working set stays warm and performance stays steady.
Tune it exactly how you like
Full root lets you set your own config, extensions, and kernel parameters — run Postgres with the extensions you need or Redis tuned for your workload.
Isolated and unexposed
Your database runs in its own microVM with its own kernel and no inbound route. Open the database port only to the specific IPs that need it.
Snapshots and backups built in
Take live snapshots for point-in-time copies and keep a pre-deletion backup for an exact replica — restore instantly whenever you need to.
How it works on a Cube
Run your database on a Cube sized and secured for it.
- 01
Create a Cube with the RAM and disk your dataset needs and SSH in as root.
- 02
Install Postgres, MySQL, or Redis and apply your configuration.
- 03
Open the database port only to the specific IPs that should connect, keeping everything else closed.
- 04
Schedule snapshots and keep a backup so you can restore to a known-good state anytime.
Frequently asked questions
Is the memory and disk really reserved for my Cube?
Yes. Every GB of RAM and disk on a Cube is reserved 1:1 on the host and never oversold or thin-provisioned — so your database gets consistent, predictable resources.
Can I install extensions and tune the config?
Yes. With full root you control the full configuration, extensions, and kernel parameters — set the database up exactly the way your workload needs.
How do I keep the database private?
A Cube has no inbound route until you create one. Open the database port only to the specific IPs that need access and leave everything else closed.
Launch your first Cube
Signing up is free — you'll be SSH'd into your own Cube in under a minute. Claim $5 in free credit — one-time, per account, and nothing is charged for it.