We handle
- Engine installation, configuration, patching, and version upgrades
- Backups, retention, and performing restores on request
- Storage capacity, monitoring, and connection limits
- Credential rotation on request
Managed MariaDB
A dedicated schema on our data tier, backed up and patched by us.
What this tier is
A database on its own is a legitimate product. Plenty of workloads already have somewhere to run and only need somewhere reliable to keep state. This is that: a schema with its own user, its own grants, and its own backup schedule on a tier we operate.
The data tier is separate from the compute tier by design. It has its own storage, its own maintenance windows, and its own monitoring. Application incidents do not become data incidents.
Specification
| Engine | MariaDB, current stable release |
|---|---|
| Storage | 5 GB, expandable |
| Connections | 25 concurrent |
| Character set | utf8mb4 by default |
| Access | Private in-cluster hostname; restricted external on request |
| Backups | Daily logical dump, 14-day retention |
| Restores | Operator-performed, restore point confirmed with you first |
| Upgrades | Scheduled with you, never applied silently |
What is included
- Dedicated schema with a scoped user and least-privilege grants
- utf8mb4 by default, with collation configurable on request
- Daily logical dump, fourteen-day retention, operator-assisted restore
- Private in-cluster hostname for workloads hosted with us
- Optional restricted external access by source address
- Slow query log available on request for tuning conversations
- Engine version upgrades scheduled with you, never silently
Typical use cases
- Persistence for an application running on our compute tier
- A database for a workload you host elsewhere but do not want to operate
- Replacing a database that currently lives on the same box as the web server
- A reporting or archive schema that needs to survive its application
Responsibility split
Written down so there is no argument about it later.
You handle
- Schema design, indexes, and query performance
- Application-side connection pooling and retry behaviour
- Telling us before you load ten times the data you estimated
How provisioning works
Operator-provisioned, usually same business day. You receive a hostname, database name, username, and password by a channel you nominate. Credentials are never sent in the same message as the hostname.
Order
Other tiers in Applications and databases
Entry
Application Starter
One application container and one managed database, wired together.
$19 /mo
- Application container plus a managed database schema
- Private in-cluster networking to the data tier
- Daily database backup with a fourteen-day restore window
View details
Redundant application instances, a larger database, and a change process.
$59 /mo
- Multiple replicas behind health checks with rolling deploys
- Larger managed database with point-in-time restore requests
- Staging environment matching production configuration
View details
A PostgreSQL database with extensions, backups, and an operator.
$10 /mo
- Dedicated database and role with least-privilege grants
- Common extensions available on request
- Daily backup with a fourteen-day restore window
View details
A Redis-compatible cache with an eviction policy you chose on purpose.
$6 /mo
- Dedicated instance, not a shared keyspace
- Eviction policy and memory ceiling agreed at provisioning
- Private in-cluster access, never exposed publicly
View details