Should you use Cloud Clusters PostgreSQL hosting (pgsclusters)?

If you are shopping for managed PostgreSQL and have landed on Cloud Clusters (the Postgres product lives at pgsclusters.com), this post is the side by side you are looking for. We run Layerbase Cloud, a competing managed database platform, so we have a horse in this race. We are going to be straight with you anyway, because the goal here is for you to make the right call, not to be sold.

Short version: Cloud Clusters is a real, working managed Postgres host with flat pricing and no usage meter. For a small always-on instance it does the job. But if you are choosing where to put a Postgres in 2026, we think Layerbase wins on free tier, tooling, branching, and current engine versions, and we will show you exactly where.

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 Postgres locally first with SpinDB
• Which one to pick

At a glance

What Cloud Clusters gets right

Credit where it is due. Cloud Clusters runs your Postgres in an isolated Docker container on Kubernetes, and the model is honest:

• Flat pricing with no overages. Their copy says it plainly: you will not get an overage charge for high traffic. The plans are fixed CPU, RAM, and SSD tiers, billed monthly, cheaper if you prepay six, twelve, or twenty four months. This is genuinely nice if you hate surprise bills. For what it is worth, Layerbase is also flat per instance with no usage meter, so neither of us is going to spring a metered bill on you.
• Cheap entry point. Express starts around $4.19/mo for 2 CPU, 2GB RAM, and 60GB SSD. That is a fair price for a small always-on instance.
• The basics are covered. Free auto-backup (twice a month on the lower tiers, weekly higher up), SSL, firewall rules, and 24/7 support are all there.

If all you want is a single small Postgres that stays on and costs a few dollars a month, Cloud Clusters can do that. We are not going to pretend otherwise.

Where it falls short

The gaps show up the moment you want more than one always-on box.

• The Postgres is a major version behind. pgsclusters lists PostgreSQL 16 Community as the top version. Postgres 18 is current. If you want the newer planner improvements, uuidv7(), or the latest logical replication work, you are not getting them here.
• No real free tier. There is a 7-day free trial and then you pay. There is no perpetual free instance to keep a side project or a staging database on.
• No branching, no scale to zero, no web query console. These are not edge cases anymore, they are table stakes for modern Postgres platforms, and they are all absent. More on each below.
• US-only footprint. Their datacenters are Kansas City and Dallas. If your users or your app servers are in Europe or Asia, every query crosses the Atlantic or the Pacific.

The free tier gap

This is the single biggest difference, so it gets its own section.

Cloud Clusters gives you a 7-day free trial. After that, every Postgres is a paid instance, even a throwaway one you spin up to test a migration.

Layerbase gives you a free dev tier with no credit card and no expiry. The instance hibernates when idle and wakes on the next connection in a couple of seconds, which is how it can be free. You can keep a staging database, a hobby project, or a demo running indefinitely without paying, and you can have more than one. On top of that, the Pro plan has its own free trial, so you can try the always-warm paid experience before committing.

If your use case is "I want to try Postgres without a clock running" or "I want a free database for a side project," that is the whole ballgame.

Branching

Branching is the feature that has reshaped how teams use Postgres. You take an instant copy of a database, point a pull-request preview or a test run at it, and throw it away when you are done. No pg_dump and restore, no waiting.

Cloud Clusters does not offer branching, and this is not just a missing checkbox. Their architecture is one fixed-size container per instance with conventional scheduled backups (twice a month or weekly). There is no storage and compute separation and no copy-on-write snapshot layer, which is what instant branching is built on. It is fair to say branching is unlikely to arrive on that infrastructure without a rebuild.

Layerbase branches Postgres today, along with eight other engines. You branch from the dashboard, get a fresh connection string, and it is ready in seconds. If your team does preview environments or per-PR databases, this alone is the reason to choose Layerbase.

The web console and local tooling

Cloud Clusters gives you a control panel for backups and deployments, plus SSH and FTPS access. To actually run a query you bring your own tool (psql, pgAdmin, DBeaver). There is no in-browser query editor.

Layerbase ships a web query console in the dashboard. You write SQL in the browser, run it, and read the results in a real data table, no local client required. The same console works across every engine on the platform, so a Postgres tab and a Redis tab look and feel consistent.

Local development is the other half. Layerbase ships SpinDB, an open-source CLI that runs Postgres (and 20-plus other engines) on your machine with no Docker, plus a desktop app for managing it visually. SpinDB runs on macOS, Windows, and Linux, so your local setup matches your cloud setup. Cloud Clusters has no local story at all.

Layerbase also gives you free auth integrations (drop-in email and password or OAuth for your app, at no extra charge) and is expanding into hosting full applications next to your data. Cloud Clusters is database hosting and nothing more.

A note on the website itself

This is a small thing, but worth a calm mention because it shapes trust. The Cloud Clusters sites have a dated feel, closer to a mid-2010s shared-hosting control panel than a modern developer platform, and small details are inconsistent across their engine sites (copyright years that read 2025 on some pages and 2026 on others, the company named as both an LLC and an Inc).

The customer testimonials are the part we would weigh carefully. On the Postgres site they are attributed only to masked email addresses like isk***@***mail.com with placeholder avatar images, no names, job titles, or companies. We could not find a way to verify that any of them map to a real, named person or business. None of this proves anything is wrong, but we would not put much weight on the social proof. Judge the product on the free trial, not the quotes.

Try Postgres locally first with SpinDB

Before you commit to any host, run Postgres locally and get a feel for it. SpinDB does it with one CLI, no Docker. (What is SpinDB?)

npm i -g spindb    # npm
pnpm add -g spindb # pnpm

spindb create my-postgres -e postgresql --start --connect

That creates a Postgres, starts it, and drops you into a psql shell. Build a table to try it out:

CREATE TABLE notes (
  id SERIAL PRIMARY KEY,
  body TEXT NOT NULL,
  created_at TIMESTAMPTZ DEFAULT now()
);

INSERT INTO notes (body) VALUES ('first note');
SELECT * FROM notes;

When you want it managed, the same engine moves to Layerbase Cloud unchanged. Common SpinDB commands:

spindb url my-postgres      # print the connection string
spindb stop my-postgres     # stop the server
spindb start my-postgres    # start it again
spindb list                 # see all your instances

Which one to pick

Here is the honest split:

• You need a single, small, always-on Postgres and nothing else, and you like a fixed monthly price: Cloud Clusters is a reasonable, cheap option. It works.
• You want a free tier, the current Postgres version, branching, a web console, local tooling, scale to zero, or anything beyond one box: Layerbase.

We have thought about this honestly, and for Postgres specifically we cannot come up with a scenario where Cloud Clusters is the better choice over Layerbase. The one area where Cloud Clusters earns a genuine recommendation is SQL Server and Oracle, which Layerbase does not host. If you need one of those, keep Cloud Clusters in mind. For Postgres, MySQL, MariaDB, or Redis, we think the call is clear.

Create a free Postgres on Layerbase Cloud. No credit card, no 7-day clock, and you can branch it, query it in the browser, and run the same engine locally with SpinDB.