Introducing Livops 2.0! Promo codeCEOgives you 8,000 so‘m on your balance.What’s new

Managed PostgreSQL hosting in 2026: the options compared

A production PostgreSQL needs backups you can restore, a connection limit your app stays under, the app in the same region, and a supported version. On Livops a PostgreSQL 15, 16 or 17 database runs inside your project, its DATABASE_URL is written into your services, and it is backed up every night; 500 MB is free, one per team, and 1 GB is 9 credits a month. Here is how Neon, Supabase, Render, Railway and a VPS compare.

By Livops team, the people who build and run LivopsUpdated

Every managed PostgreSQL runs the same database; what you are choosing is who takes the backups, how many connections you get, how far the database sits from your app, and what a month costs. This page lists what a production Postgres needs, compares Neon, Supabase, Render, Railway and a VPS on each provider’s own pages, read on 20 November 2026, and ends with how a database works on Livops — including where the others are better.

What does a production PostgreSQL need?

Backups you have restored at least once

A backup that has never been restored is a hope. Check three things: how often it is taken, how long it is kept, and what a restore does — overwrite the running database, or open a copy next to it. Point-in-time recovery, which rolls back to any second inside a window, is the step past nightly backups; some providers include it and some charge for it.

A connection limit your app stays under

Each PostgreSQL connection is a server process. The server’s own default is 100 connections, of which three are kept for superusers[2], and small managed plans often allow fewer. An app with several processes, each holding a pool of ten, reaches the limit quickly, and the next connection is refused. A pooler such as PgBouncer lets many clients share few server connections; without one, keep each pool small.

The app and the database in the same place

Every query is a round trip. An app in Tashkent talking to a database in Frankfurt pays that distance on every query, and a page that runs twenty queries pays it twenty times. Put the database in the same region, ideally the same private network, as the app that uses it.

A supported major version

PostgreSQL supports each major version for five years after its first release[1]. Today 15, 16, 17, 18 and 19 are supported; 14 reached its final release on 12 November 2026[1]. Know how your provider moves you to a new major version, because the old one will run out.

The options at a glance

Option What it is Smallest paid database What you still maintain
Livops PostgreSQL inside your project; servers in Uzbekistan 1 GB: 9 credits a month; 500 MB free, one per team Your schema; a major upgrade by copying the data
Neon Serverless Postgres billed by usage Launch: $0.106 per CU-hour and $0.35 per GB-month[3] Your schema
Supabase Postgres with auth, storage and APIs around it Pro: $25 a month, including one Micro instance with 1 GB of RAM[5] Your schema
Render A platform with managed Postgres $6 a month: 256 MB RAM, 100 connections, plus $0.30 per GB of storage[7] Your schema
Railway A Postgres template billed by usage About $10 per GB of memory and $0.15 per GB of volume a month; Hobby is $5 including $5 of usage[12] Your schema; more if you change the template[13]
A VPS in Uzbekistan A virtual machine with root 82,000 so’m a month: 1 vCPU, 2 GB, 30 GB HDD (SmartCloud)[16] Installing, tuning, securing, backing up and upgrading PostgreSQL

Other providers’ prices are from each provider’s own page, read on 20 November 2026; the dates are in Sources below. Livops prices are the ones the cabinet bills today.

Each option

Livops

A database runs in its own container inside your project, next to the app, on servers in Uzbekistan. It has no public port: services in the project reach it at the internal host postgres, and your computer reaches it through an SSH tunnel. PostgreSQL 15, 16 or 17 is offered, in Standard, pgvector or PostGIS types, with a fixed list of extensions the team owner switches on. It is backed up every night and keeps 7 daily, 4 weekly and 3 monthly backups; a restore opens as a new database beside the original.

Where it is worse: there is no point-in-time recovery, only nightly and hand-taken backups. The largest size is 5 GB with 256 MiB of memory, where the others here grow far past that. PostgreSQL accepts 20 connections at once and there is no built-in pooler yet. 18 and 19 are not offered, and the version cannot be changed in place. And because there is no public port, an app hosted elsewhere cannot use it.

Neon

Neon bills compute by the hour and storage by the GB: on Launch, $0.106 per CU-hour and $0.35 per GB-month[3]. Compute scales to zero after 5 minutes without activity, which Launch lets you disable[3]. It is better than Livops on several counts: a history window for restores of up to 7 days on Launch and 30 on Scale[3], a built-in PgBouncer with up to 10,000 pooled connections per compute[3], branches for previews and tests[3], and sizes up to 16 CU (64 GB of RAM) on Launch[3]. Its regions are on AWS in the US, Frankfurt, London, Singapore, Sydney and São Paulo[4] — none of them in Central Asia.

Supabase

Supabase is Postgres with authentication, file storage and generated APIs around it. Pro is $25 a month and includes $10 of compute credits, enough for one Micro instance with 1 GB of RAM, and 8 GB of disk per project, then $0.125 per GB[5]. A Micro instance accepts 60 direct connections and 200 through the pooler[5]. Pro keeps daily backups for 7 days; point-in-time recovery costs $100 a month per 7 days of retention[5]. It has the most regions here, from Mumbai and Tokyo to São Paulo[6]. If you want auth and storage from the same vendor as the database, it does more than any other option on this page.

Render

Render’s smallest paid Postgres is $6 a month for 256 MB of RAM and 100 connections, and storage is $0.30 per GB[7]. Point-in-time recovery covers the past 3 days on a Hobby workspace and 7 days on Pro or higher[9], and logical backups are kept for seven days[9]. PgBouncer pooling is built in, at no extra cost on paid databases[10]. Regions are Oregon, Ohio, Virginia, Frankfurt and Singapore, and services talk privately only within one region[11]. Better than Livops for an app hosted on Render in one of those regions, and for anyone who needs point-in-time recovery.

Railway

Railway’s Postgres is a template that deploys a single node Railway maintains; once you change its image, start command or variables, the database is yours to manage[13]. It is private by default and gives other services DATABASE_URL and the PG* variables; public access goes through a TCP proxy whose egress you pay for[13]. You pay for the memory and volume it uses, about $10 per GB of memory and $0.15 per GB of volume a month[12]. Backups can be scheduled daily (kept 6 days), weekly (27 days) or monthly (89 days), and a restore goes to a new volume[14]. Regions are California, Virginia, Amsterdam and Singapore[15]. Payment is by card[12].

A VPS

The cheapest SmartCloud machine with 2 GB is 82,000 so’m a month[16]: more memory than any small managed plan here, and root to tune PostgreSQL as you like. Everything else is yours: installing it, keeping it off the public internet, pg_dump on a schedule to somewhere that is not the same disk, testing restores, and a major upgrade at least once every five years[1].

Managed or on a VPS: what do you maintain?

On a VPS, the database is as safe as the last backup you checked. A managed database takes the backups, the minor updates and the disk for you, and you give up superuser access and some tuning in exchange. Of the managed options, the trade-offs are distance and limits: Neon, Supabase, Render and Railway have more memory, more connections and point-in-time recovery, in regions far from Uzbekistan; Livops has less of each, next to an app running in Uzbekistan.

Where can you run PostgreSQL for free?

  • Livops: one 500 MB database per team is free, with 128 MiB of memory, and backed up like the paid ones. It is reachable only from your project’s services and over the SSH tunnel; the apps that use it are paid.
  • Neon: 100 projects with 1 GB of storage and 100 CU-hours each a month, compute up to 2 CU, suspended after 5 minutes without activity, with a restore window of up to 6 hours or 1 GB of changes; no card required[3].
  • Supabase: two active projects with a 500 MB database each, paused after a week without activity, and no automatic backups[5].
  • Render: one free Postgres per workspace, 1 GB, which expires 30 days after creation with 14 days’ grace to upgrade, and has no backups[8].
  • Railway: a Free plan with $1 of usage a month and volumes up to 0.5 GB; services sleep after 5 to 10 minutes without outbound traffic[12].
  • A VPS is never free; the cheapest machine above is 82,000 so’m a month[16].

PostgreSQL on Livops

  1. Open the project and add PostgreSQL under Databases. Pick the version (15, 16 or 17) and the type (Standard, with pgvector, or with PostGIS); neither can be changed later. Pick the size: 500 MB is free, one per team.
  2. DATABASE_URL and the PG* and POSTGRES_* variables are written to every service in the environment, including ones you add later. Read the variable; do not copy the value.
  3. Run migrations as the pre-deploy command: it runs before each new version starts, and if it fails, the old version keeps serving.
  4. To browse tables, use the database page in the cabinet. To use DBeaver, TablePlus or psql, add an SSH key under Account → SSH keys and open Connect from your computer.

The variable looks like this:

DATABASE_URL=postgresql://app:<password>@postgres:5432/app

and the code only reads it:

import pg from 'pg'
const pool = new pg.Pool({ connectionString: process.env.DATABASE_URL, max: 5 })
  • 20 connections at once. Keep pools small: with Prisma 6, ?connection_limit=5 in DATABASE_URL. A built-in PgBouncer is not offered yet.
  • Backups every night, kept as 7 daily, 4 weekly and 3 monthly. Download any of them as a pg_dump custom-format file, or take one of the current state before risky work. A restore opens a new database next to the original and your apps’ variables do not change; only the team owner can restore.
  • Extensions from a fixed list — pg_trgm, pgcrypto, uuid-ossp, citext, hstore and more — are switched on under Settings → Extensions. TimescaleDB, pg_stat_statements and pg_cron are not available.
  • Read-only login for Metabase, Grafana or an analyst: Overview → Read-only login.
  • Staging gets its own, empty database, so tests never write to production’s. See Environments.

A database is free at 500 MB (one per team), 9 credits a month at 1 GB, 19 at 3 GB and 29 at 5 GB, and you can grow it later. Staging and other environments cost half. Credits are bought in so’m through Payme or Click, with no card. See Databases and Pricing.

Questions

Which PostgreSQL versions does Livops run?

15, 16 and 17, with 16 as the default. You pick the version when you add the database and it cannot be changed later. To move to a newer one, add a database of that version and copy the data over with pg_dump through the SSH tunnel.

How does my app get the connection string?

By itself. Once you add PostgreSQL to a project, DATABASE_URL and the PGHOST, PGPORT, PGUSER, PGPASSWORD and PGDATABASE variables are written to every service in that environment, including services added later. Your code reads DATABASE_URL.

Can I connect to a Livops database from my computer or from another host?

From your computer, yes, through an SSH tunnel signed by your key; the database page shows the settings for DBeaver, DataGrip, TablePlus, pgAdmin or a terminal. There is no public port, so an app hosted somewhere else cannot reach it. Run the app on Livops too, or choose a database with a public address.

How are Livops databases backed up?

Every night, to a separate location. The last 7 daily, 4 weekly and 3 monthly backups are kept, and you can take one of the current state before risky work. Any backup can be downloaded as a pg_dump file. A restore opens as a new database next to the original, so nothing is overwritten. There is no point-in-time recovery.

How many connections can my app open?

PostgreSQL on Livops accepts 20 connections at once, and a built-in pooler is not offered yet. Keep each process's pool small, for example connection_limit=5 in the URL for Prisma 6, or max on the pg Pool.

Is the 500 MB database really free?

Yes, one per team, with 128 MiB of memory. Larger sizes are paid monthly in credits bought in so'm through Payme or Click, with no card. Databases do not run during the 15-minute demonstration of an unpaid account; they start once there are credits.

Who wrote this comparison?

The Livops team. Every price and limit of another provider links to that provider's own page, with the day we read it, and each section says where that provider is better than us.

Sources

  1. PostgreSQL — Versioning policy (postgresql.org). Checked .
  2. PostgreSQL docs — Connections and authentication (postgresql.org). Checked .
  3. Neon — Pricing (neon.com). Checked .
  4. Neon — Regions (neon.com). Checked .
  5. Supabase — Pricing (supabase.com). Checked .
  6. Supabase — Available regions (supabase.com). Checked .
  7. Render — Pricing (render.com). Checked .
  8. Render — Deploy for free (render.com). Checked .
  9. Render — Postgres recovery and backups (render.com). Checked .
  10. Render — Postgres connection pooling (render.com). Checked .
  11. Render — Regions (render.com). Checked .
  12. Railway — Pricing (railway.com). Checked .
  13. Railway — PostgreSQL (docs.railway.com). Checked .
  14. Railway — Backups (docs.railway.com). Checked .
  15. Railway — Deployment regions (docs.railway.com). Checked .
  16. SmartCloud — VDS plans (smartcloud.uz). Checked .

Put your project online today

Connect GitHub or drop a folder. No card is asked for.

Add a database

Got a question? — @livops_uz