Apps / MariaDB
Managed MariaDB hosting.
One server, no app limits.
The MySQL fork with a community heart. Same managed treatment: tuning, backups, monitoring.
What it is
MariaDB is the community-governed MySQL lineage: drop-in compatible for the workloads that matter, the default database of most Linux distributions, and what the majority of CMS installs actually run on.
Minimum RAM
1 GB
Fits on SC-1GB; SC-2GB is the comfortable pick with room to stack.
What we install
The playbook deploys current MariaDB tuned to the server's RAM, secured to local access by default with remote access as an explicit firewall grant, and scheduled logical dumps layered on top of the block-level backups.
What managed covers
Updates on the maintained series, daily snapshots plus dual offsite backups with per-database dumps, monitoring on connections and slow queries, and the managed firewall in front of the port.
The app is $0. The managed server is the only bill, and everything above is part of it.
What does managed MariaDB hosting include?
Tuning matched to the plan, three layers of backup, watched monitoring, and deliberate network exposure, in the flat server price. The boring, correct way to run the database everything else depends on.
Why MariaDB for CMS workloads?
Because it is what they are tested against: WordPress, Joomla, Nextcloud, and most of this catalog treat MariaDB as home ground. If an app on this page needs a database and you have no strong opinion, this is the unopinionated right answer.
Can one MariaDB serve several stacked apps?
Yes, and it is the efficient pattern: one tuned instance with a database per app, one buffer pool sized once, one backup schedule covering all of it. The playbooks wire each catalog app to it cleanly.
What about very busy databases?
Busy transactional loads are what the Dedicated CPU family exists for: cores that are physically yours so query latency stops depending on neighbors. Same management, same playbook, sturdier floor.
Stack it
MariaDB runs well with.
Same server, no extra bill. These are the companions our team installs next to MariaDB most often.
Redis
+1 GBIn-memory cache and queue. The cheapest speed upgrade most stacks never install. Pairs with everything.
Uptime Kuma
+1 GBThe self-hosted uptime monitor everyone loves. Watch your sites from your own server.
Frequently asked questions
How much RAM does MariaDB need?
1 GB floors it for small schemas. Shared across several stacked apps, count roughly the sum of their working sets; the sizing calculator helps.
Is it compatible with MySQL apps?
For the overwhelming majority of applications, yes, drop-in. The exceptions are apps pinned to MySQL-8-only features, and those simply pick MySQL from this same catalog.
How are restores handled?
Snapshot rollback for the whole server, offsite restore for disasters, and per-database logical dumps when you need one table back from Tuesday. You ask; we restore.
Sizing an app stack? The VPS sizing calculator recommends a plan from your apps and traffic, with the math shown.
Shared CPU servers
The right home for MariaDB and most stacks: 3.0+ GHz vCPU, from $10/mo.
See Shared CPU →Dedicated CPU servers
For CPU-hungry stacks and busy databases: cores that are physically yours.
See Dedicated CPU →All plans and pricing
Every plan, both families, one honest price with everything included.
See pricing →Your server runs. You sleep.
Fully managed hosting from people who have been doing this since 2001.