Should you use Cloud Clusters MariaDB hosting (maclusters)?
Managed MariaDB hosting got harder to shop for after MariaDB shut down its own SkySQL cloud, so it makes sense that you are looking at Cloud Clusters (their MariaDB product is maclusters.com). This is the honest comparison. We run Layerbase Cloud, a competing managed database platform, so factor in the bias. We are still going to lay out where Cloud Clusters is a fair pick and where it is not.
Short version: Cloud Clusters runs a real managed MariaDB with flat, no-overage pricing, and for one small always-on database that is fine. For most other cases we think Layerbase is the stronger choice, and the differences are specific, not hand-wavy.
Contents
- At a glance
- What Cloud Clusters gets right
- Where it falls short
- The free tier gap
- Branching
- The web console and local tooling
- A note on the website itself
- Try MariaDB locally first with SpinDB
- Which one to pick
At a glance
| Cloud Clusters (maclusters) | Layerbase Cloud | |
|---|---|---|
| MariaDB version | MariaDB 11.1 and 10.6 Community | Current MariaDB release |
| Free tier | 7-day free trial only | Free dev tier, no credit card, no expiry |
| Pro trial | No | Yes, free trial on the Pro plan |
| Pricing model | Flat per instance, no overages | Flat per instance, no overages |
| Entry price | About $4.99/mo (2 CPU, 2GB, 60GB) | Free dev tier, paid add-ons are opt-in |
| Other engines on one account | No, separate sites per engine | More than 20 engines in one dashboard |
| Web query console / IDE | No, control panel plus phpMyAdmin | Yes, in-browser query console |
| Branching | No | Yes, MariaDB branches |
| Local dev tooling | None | SpinDB CLI plus a desktop app |
| Scale to zero | No, always-on container | Yes, hibernation with wake on connect |
| Bare metal option | Dedicated servers | Dedicated bare-metal on the Custom plan |
| Regions | US only (Kansas City, Dallas) | Vendor neutral, reachable from any cloud |
What Cloud Clusters gets right
Cloud Clusters runs MariaDB in an isolated Docker container on Kubernetes, and the offer is straightforward:
- Flat pricing with no overages. Fixed CPU, RAM, and SSD tiers, billed monthly, cheaper if you prepay. Their copy promises no overage charges for high traffic. Layerbase is also flat per instance with no usage meter, so on the no-surprise-bill front we agree.
- Low entry price. Express is around $4.99/mo, and they advertise steeper "membership" discounts on top. For a small always-on MariaDB the cost is reasonable.
- Standard tooling. phpMyAdmin, free auto-backup, easy restore, free migration, SSH, and 24/7 support are all included.
If you want one small MariaDB that stays up, this does it.
Where it falls short
- The version is dated and Community only. maclusters lists MariaDB 11.1 and 10.6 Community. Those are not the newest releases, and there is no sign of a fast upgrade cadence. Layerbase tracks the current MariaDB release.
- No real free tier. A 7-day trial, then every instance is paid.
- No branching, no scale to zero, no web query console. All standard on modern platforms, all missing.
- US-only footprint. Kansas City and Dallas. No European or Asian regions.
The free tier gap
Cloud Clusters gives you a 7-day free trial. After it ends, every MariaDB is a paid instance, including a scratch database for testing a migration.
Layerbase gives you a free dev tier with no credit card and no expiry. It hibernates when idle and wakes on the next connection, which is what keeps it free. Keep a staging or hobby MariaDB running as long as you want, and run more than one. The Pro plan adds its own free trial of the always-warm experience.
If you are coming off SkySQL and just want a free place to land a MariaDB while you regroup, that constraint is the whole story. For the broader survey, see MariaDB SkySQL alternatives.
Branching
Branching takes an instant copy of a database so a preview deploy or a test run can hit real-shaped data and be thrown away after. Cloud Clusters does not offer it. The architecture is one fixed container per instance with scheduled backups, with no storage and compute split and no copy-on-write snapshot layer, which is the foundation instant branching needs. It is unlikely to arrive on that infrastructure without a rebuild.
Layerbase branches MariaDB today, from the dashboard, with a fresh connection string in seconds. For preview environments or rehearsing a schema change against a real copy, this is the single clearest reason to choose Layerbase.
The web console and local tooling
Cloud Clusters gives you a control panel, phpMyAdmin, and SSH. Functional, but phpMyAdmin has not changed much in years.
Layerbase ships a web query console in the dashboard: write SQL in the browser, run it, read the results in a real data table. The same console works across every engine, so MariaDB, MySQL, and Postgres tabs all behave the same way.
For local development, Layerbase ships SpinDB, an open-source CLI that runs MariaDB and 20-plus other engines on your machine with no Docker, plus a desktop app. SpinDB runs on macOS, Windows, and Linux. Cloud Clusters has no local tooling.
Layerbase also bundles free auth integrations (drop-in email and password or OAuth, no extra charge) and is expanding into hosting applications next to your data. Cloud Clusters is database hosting only.
A note on the website itself
A short, fair note. The Cloud Clusters sites feel dated, more mid-2010s hosting panel than modern developer platform, and details vary across their engine sites (the MariaDB site still shows a 2025 copyright while others show 2026, and the company is named as both an LLC and an Inc).
The testimonials are the part to read carefully. On the MariaDB site, as on the others, the customer quotes are attributed only to masked email addresses with placeholder avatars, no names, titles, or companies, so there is no way to confirm a real person or business behind them. This does not prove anything, but we would not weigh the social proof heavily. The free trial tells you more than the quotes do.
Try MariaDB locally first with SpinDB
Before committing to a host, run MariaDB locally. SpinDB does it with one CLI, no Docker. (What is SpinDB?)
npm i -g spindb # npm
pnpm add -g spindb # pnpmspindb create my-mariadb -e mariadb --start --connectThat creates a MariaDB, starts it, and opens a client. Try a table:
CREATE TABLE notes (
id INT AUTO_INCREMENT PRIMARY KEY,
body TEXT NOT NULL,
created_at TIMESTAMP DEFAULT CURRENT_TIMESTAMP
);
INSERT INTO notes (body) VALUES ('first note');
SELECT * FROM notes;When you want it managed, the same engine moves to Layerbase Cloud unchanged. Useful SpinDB commands:
spindb url my-mariadb # print the connection string
spindb stop my-mariadb # stop the server
spindb start my-mariadb # start it again
spindb list # see all your instancesWhich one to pick
- You need a single small always-on MariaDB and prefer a fixed monthly price: Cloud Clusters is a reasonable, cheap option.
- You want a free tier, branching, a web console, local tooling, scale to zero, or a current release: Layerbase.
Honestly, for MariaDB specifically we cannot find a scenario where Cloud Clusters is the better pick over Layerbase. Where Cloud Clusters does earn a fair recommendation is SQL Server and Oracle, which Layerbase does not host. If you need one of those, keep them in mind. For MariaDB, MySQL, Postgres, or Redis, we think Layerbase is the clear choice.
Create a free MariaDB on Layerbase Cloud. No credit card, no 7-day clock, branchable, queryable in the browser, and runnable locally with SpinDB.