What Is Neon Postgres? Why Slim Minima Uses It

Q: Why pooled connection string and not the direct one?

A pooled connection, the one whose host contains `-pooler`, is designed for environments that open many short-lived connections, which is how serverless hosting like Vercel behaves. Using it avoids running out of connections under load. Slim Minima expects the pooled string.

Every Slim Minima site needs a database. It is where your content actually lives: every page, every blog post, every menu, every contact form submission, every setting you change in the admin panel. By default, that database is Neon.

Neon is a hosted version of Postgres, one of the most trusted databases in the world. The "serverless" part is what makes it a good fit for a small site: it scales itself up when there is work to do and goes quiet when there is not, so you are not paying for a server that sits idle most of the day.

This article explains what Neon is, how a Slim Minima site uses it, why it is the default, and the one behaviour that surprises people the first time they see it. Figures came from Neon's official pricing and documentation, checked in June 2026.

What Postgres is, in plain terms

Postgres, short for PostgreSQL, is a database. A database is a structured filing system that software uses to store and retrieve information reliably.

When you write a blog post in Slim Minima and hit save, the title, the body text, the meta description, the tags, and the URL all get written into Postgres. When a visitor opens that post, the site reads it back out of Postgres and shows it. The same goes for pages, the navigation menu, your site settings, and the messages people send through a contact form.

Postgres has been around for decades and runs some of the largest applications on the internet. It is dependable, well understood, and not going anywhere. Building on it means your content sits in a format any developer can work with, on a system that will outlast any single hosting company.

What makes Neon different

Neon is real Postgres, not a lookalike or a fork. Anything that works with standard Postgres works with Neon. What Neon adds is the way it runs that Postgres.

It separates storage from compute. Your data sits in storage permanently, while the part that does the work spins up only when a query comes in. This is what lets it scale to zero.
It scales to zero. After about five minutes with no activity, the compute goes to sleep. While asleep, it uses nothing and costs nothing. The next request wakes it.
It has database branching. You can make an instant copy of your whole database to test a change against, the same way you branch code. Most people never need this on a small site, but it is there.

The practical upshot is a database that behaves like a big managed one when busy and disappears when idle, which is exactly the shape a marketing site's traffic takes.

How Neon works with Slim Minima

Setting Neon up for a Slim Minima site is a copy-and-paste job, not a database administration project.

Create a free Neon project. Any name, any region near your visitors.
Copy the connection string. Use the pooled one, the host that contains -pooler, which is built to handle many short-lived connections.
Paste it into the site's DATABASE_URL setting.
Run the migration command once, which creates all the tables Slim Minima needs.

From then on, the database just works. When you deploy the site, the build applies any new database changes automatically before going live, so the structure and the code never fall out of step. Slim Minima talks to Neon over a connection built for serverless hosting, which is part of why the pairing with Vercel is so clean.

You are not locked in. Because Neon is standard Postgres, you can point a Slim Minima site at any Postgres host, whether that is Supabase, Railway, a managed instance from a cloud provider, or a server you run yourself. Neon is the default, not a requirement.

Why we recommend Neon

A few honest reasons it is the default choice.

It is real Postgres, so there is no lock-in. Your data is portable to any Postgres host on day one.
The free tier is generous for content sites. Half a gigabyte of storage holds thousands of pages and posts. A normal marketing site uses a tiny fraction of it.
Scale to zero keeps it free when idle. A small site spends most of the day with no visitors. Neon charges nothing for that quiet time.
It is light to set up. No server to size, patch, or babysit. You paste one connection string and move on.
It is well regarded. Neon is one of the better-known serverless Postgres providers, with solid documentation and a free plan that does not expire.

Storage is rarely the thing you run out of. To put it in numbers: the free plan gives 0.5 GB per project, and a content-heavy page with all its metadata is roughly 200 KB, so the limit lands somewhere around a couple of thousand pages or posts. The depth on those numbers, alongside Vercel and Cloudinary, lives in how far the free stack stretches.

The one quirk to understand: cold starts

Here is the behaviour that catches people out, and the honest caveat that most write-ups leave off.

Because Neon's free tier scales to zero after about five minutes of inactivity, the first request after a quiet spell has to wake the database up. Neon resumes in a few hundred milliseconds, but it is not instant.

For a Slim Minima site, this is almost always invisible. Public pages are served from a cache, so a visitor landing on your homepage usually does not touch the database at all. The only place you might notice the wake-up is the admin panel after it has been sitting idle, where the first action can take an extra half second.

If a busier site ever makes those cold starts annoying, the fix is to move up a tier so the database stays warm, or to switch to a Postgres host that does not sleep. For the vast majority of marketing sites, scale to zero is a feature, not a problem: it is the reason the database is free for the long stretches when nobody is visiting.

When you would upgrade

Neon's free plan is permanent, so most small sites stay on it indefinitely. You would move to the paid Launch tier, which is usage-based with no monthly base fee, when:

Your content genuinely outgrows the free storage, which is unusual for a marketing site.
You want automatic backups and the ability to restore the database to an earlier point in time.
You want the database to stay always on, with no cold starts at all.

For a typical Slim Minima site, none of those arrive quickly, and when they do you pay for the one thing you outgrew rather than a whole new plan.

Frequently asked questions

Is Neon free to use? Yes. Neon has a permanent free plan with no credit card required. It gives 0.5 GB of storage per project and enough compute to run a small site comfortably. You only pay if you outgrow the limits or need features like point-in-time backups.

Will my site break when the database goes to sleep? No. Most public pages on a Slim Minima site are served from a cache and never touch the database on a normal visit. When the database does need to wake from sleep, it resumes in a few hundred milliseconds. The only place you might feel it is the admin panel after a long idle period.

Can I use a different database instead of Neon? Yes. Neon is standard Postgres, so a Slim Minima site can run on any Postgres host, including Supabase, Railway, a managed cloud instance, or your own server. Neon is the recommended default, not a lock-in.

How much content fits in the free tier? Half a gigabyte holds roughly a couple of thousand pages or posts once you account for all the text and metadata. A marketing site with dozens of pages and a blog with a hundred or so posts uses only a small slice of it.

Why pooled connection string and not the direct one? A pooled connection, the one whose host contains -pooler, is designed for environments that open many short-lived connections, which is how serverless hosting like Vercel behaves. Using it avoids running out of connections under load. Slim Minima expects the pooled string.

My verdict

Neon is the right default because it gives a small site a real, trusted database for free, then gets out of the way. The scale-to-zero quirk sounds like a downside until you realise it is the reason the free tier exists, and on a cached Slim Minima site you almost never feel it.

If you ever need an always-on database, moving up or moving out is easy, because it was standard Postgres the whole time.

What Is Neon Postgres? And Why Slim Minima Uses It