Databases

PostgreSQL VPS HostingA Postgres Server You Fully Control

Run PostgreSQL with the version, settings and extensions you choose. We install it, size the memory settings for your plan, limit connections to the servers you name and hand you root, on NVMe storage with daily backups.

View VPS Plans Talk to an Engineer

Full root & SSH NVMe storage Daily backups Anti-DDoS 99.9% uptime SLA 11 locations

  • Reserved RAM

    shared_buffers and OS cache that are yours alone.

  • NVMe storage

    Low-latency reads, writes and WAL.

  • Root access

    postgresql.conf, pg_hba.conf and extensions.

  • Daily backups

    Automatic backup of the previous 24 hours.

Why a VPS

Why Run PostgreSQL on a VPS

Managed Postgres is convenient but limits extensions and settings and prices by tier. A VPS gives you the whole server.

  1. Any extension

    PostGIS, pgvector, pg_trgm, TimescaleDB and others, installed from packages without waiting for a provider to support them.

  2. Settings for your workload

    Tune shared_buffers, work_mem, autovacuum and WAL for the queries you actually run.

  3. A fixed monthly cost

    Storage, connections and I/O are not metered separately.

  4. Your upgrade timing

    Run the major version your app supports and upgrade when you are ready.

The stack

A Secure PostgreSQL Server

Applications connect over a restricted port with their own roles; the engine and fast storage sit underneath.

Connection from your application server

  1. Network

    UFW allow-list

    Port 5432 open only to your app servers, or closed if the app runs on this VPS.

  2. Access

    pg_hba.conf + roles

    scram-sha-256 authentication and one role per application, limited by database and source IP.

  3. Pooling

    PgBouncer (optional)

    A small pool of server connections shared by many app connections.

  4. Engine

    PostgreSQL

    MVCC, WAL and autovacuum, with memory sized to the plan.

  5. Storage

    NVMe disk

    Data and WAL on fast local storage, with the server backed up daily.

Worth knowing

  • listen_addresses and pg_hba.conf both need changing before remote apps can connect.
  • Every connection is a separate process: use PgBouncer if apps open hundreds.
  • Newer major versions come from the PostgreSQL project's own apt repository.
  • pg_dump makes logical backups; for point-in-time recovery, archive WAL with a tool such as pgBackRest.
What you can run

What a PostgreSQL VPS Is Used For

  • Back end for web apps

    Django, Rails, Laravel and Node apps on one database server.

  • Geospatial data with PostGIS

    Maps, routing and location search.

  • Vector search with pgvector

    Embeddings for semantic search beside your relational data.

  • Analytics and reporting

    Window functions and JSONB for reporting workloads.

  • Self-hosted apps

    n8n, Odoo, Mattermost and others that run on PostgreSQL.

  • Read replicas

    Streaming replication to a second VPS for reporting.

VPS Plans

VPS Plans for PostgreSQL

Size by RAM: shared_buffers plus the OS page cache should hold your hot data. VPS-2 or VPS-3 suit most production databases.

VPS-1

Small websites, APIs, bots and development servers.

₹1,008 /mo
Get Started
  • 2 vCores
  • 4 GB RAM
  • 40 GB NVMe
  • 500 Mbps
  • Full root and SSH access
  • Free initial stack installation
  • Server hardening and firewall setup
  • Daily backup of the previous 24 hours
  • Unlimited traffic *
  • Anti-DDoS protection
  • Dedicated IPv4 and IPv6
  • KVM virtualisation
Most Popular

VPS-2

Production apps, WordPress and online stores.

₹1,906 /mo
Get Started
  • 4 vCores
  • 8 GB RAM
  • 75 GB NVMe
  • 1 Gbps
  • Full root and SSH access
  • Free initial stack installation
  • Server hardening and firewall setup
  • Daily backup of the previous 24 hours
  • Unlimited traffic *
  • Anti-DDoS protection
  • Dedicated IPv4 and IPv6
  • KVM virtualisation

VPS-3

Busy stores, SaaS products and several projects.

₹2,748 /mo
Get Started
  • 6 vCores
  • 12 GB RAM
  • 100 GB NVMe
  • 2 Gbps
  • Full root and SSH access
  • Free initial stack installation
  • Server hardening and firewall setup
  • Daily backup of the previous 24 hours
  • Unlimited traffic *
  • Anti-DDoS protection
  • Dedicated IPv4 and IPv6
  • KVM virtualisation

VPS-4

High-traffic apps, large databases and agencies.

₹5,274 /mo
Get Started
  • 8 vCores
  • 24 GB RAM
  • 200 GB NVMe
  • 3 Gbps
  • Full root and SSH access
  • Free initial stack installation
  • Server hardening and firewall setup
  • Daily backup of the previous 24 hours
  • Unlimited traffic *
  • Anti-DDoS protection
  • Dedicated IPv4 and IPv6
  • KVM virtualisation

* Unlimited traffic in Europe and North America. In Mumbai, Singapore and Sydney a monthly allowance applies (VPS-1 500 GB, VPS-2/VPS-3 1 TB, VPS-4 3 TB), then speed is limited to 10 Mbps until the next month.

Sizing guide

Which Plan for Your PostgreSQL Server

A common starting point is shared_buffers at about 25% of RAM, with the rest left to the OS cache and connections.

Recommended VPS plan for each PostgreSQL workload
Workload Start with Why
Small app or staging VPS-1 2 vCores · 4 GB RAM About 1 GB of shared_buffers.
Production app database VPS-2 4 vCores · 8 GB RAM About 2 GB of shared_buffers and 75 GB NVMe.
Busy database or PostGIS VPS-3 6 vCores · 12 GB RAM About 3 GB of shared_buffers and 6 vCores.
Large database or analytics VPS-4 8 vCores · 24 GB RAM About 6 GB of shared_buffers, 24 GB RAM in total and 200 GB NVMe.

A starting point, not a limit: every plan upgrades in place, keeping your data, IP address and configuration.

Managed Postgres or Your Own Server?

A managed service runs Postgres for you. A VPS gives you every setting and extension for a fixed price.

Feature Managed Postgres service PostgreSQL VPS
Pricing By tier, storage and sometimes I/O Flat monthly plan
Extensions The provider's approved list Any packaged extension
postgresql.conf Selected parameters Full
Backups and failover Managed Daily VPS backup plus your own tooling
Major upgrades Handled for you You run them
Server administration Handled by the provider Yours, after our free setup
See Plans
After handover

First Steps on Your PostgreSQL Server

Typical first tasks after handover: a role and database for an app, access and backups.

  1. Create a role and database

    The role owns only its own database.

  2. Allow your app server

    Add a host line for its IP to pg_hba.conf, set listen_addresses, and open the port to that IP.

  3. Enable an extension

    For example trigram search.

  4. Back up

    A compressed custom-format dump.

# 1. Create a role and database

sudo -u postgres createuser --pwprompt app

sudo -u postgres createdb -O app app_db

# 2. Allow your app server

sudo nano /etc/postgresql/16/main/pg_hba.conf

sudo ufw allow from 203.0.113.10 to any port 5432 proto tcp

sudo systemctl restart postgresql

# 3. Enable an extension

sudo -u postgres psql -d app_db -c "CREATE EXTENSION IF NOT EXISTS pg_trgm;"

# 4. Back up

sudo -u postgres pg_dump -Fc app_db > ~/backups/app_db-$(date +%F).dump

Example shell commands; adjust paths, names and versions to your project.

Example commands; adjust names, paths and versions to your project. Deploying and maintaining your application is yours to do (or ask us for a quote).

Free one-time setup

Installed and Secured Before You Log In

The VPS is unmanaged: after handover the server is yours to run. Before that, our engineers do the first setup once, free, so you start from a hardened server with PostgreSQL in place.

  1. Choose a plan and location

    Pick the resources you need and the datacentre closest to your users.

  2. Tell us your PostgreSQL setup

    Versions, database and domain: at order or right after.

  3. We install and secure it

    Server hardened, PostgreSQL installed and tested, HTTPS on your domain.

  4. You take over with root

    SSH access to a working server, ready for your code and data.

Your PostgreSQL server

  • PostgreSQL from the OS or the PostgreSQL apt repository
  • scram-sha-256 authentication, with a role and database for each app
  • Memory settings sized for your plan
  • pg_hba.conf and the firewall limited to your app servers
  • PgBouncer or extensions such as PostGIS on request

Yours to run after handover

  • Ongoing server administration
  • Application maintenance and updates
  • Debugging your code
  • Migrating existing sites or data

Not included in the free setup, but we can quote for it. No control panel by default: CloudPanel, HestiaCP or Virtualmin on request at no cost; cPanel and Plesk need their own licence.

Under the hood

Platform Specs and Locations

The same KVM platform on every plan; only the CPU, RAM, storage and port speed change.

VPS platform specifications
Virtualisation KVM with reserved vCores and RAM
Storage NVMe SSD on every plan
Network Dedicated IPv4 and IPv6, 500 Mbps to 3 Gbps per plan
Operating systems Ubuntu 26.04, 24.04 and 22.04 LTS · Debian 13, 12 and 11 · AlmaLinux · Rocky Linux · Fedora · FreeBSD
Access Full root over SSH, key-based login
Backups Automatic daily backup of the previous 24 hours; snapshots and longer retention on request
Protection Always-on anti-DDoS mitigation
Availability 99.9% uptime SLA

Secured before we hand it over

  • Non-root sudo user created for daily work
  • SSH key login, password login for root disabled
  • Firewall (UFW) open only for the ports you use
  • Fail2ban blocking repeated login attempts
  • Automatic security updates enabled
  • Free Let's Encrypt SSL on your domain
  • Timezone, swap and hostname configured

Asia-Pacific

  • Mumbai
  • Singapore
  • Sydney

Europe

  • London
  • Limburg
  • Roubaix
  • Gravelines
  • Strasbourg
  • Milan
  • Warsaw

North America

  • Beauharnois

Availability per location changes with demand; we confirm your location before setup. In Mumbai, Singapore and Sydney each plan includes a monthly traffic allowance (VPS-1 500 GB, VPS-2 and VPS-3 1 TB, VPS-4 3 TB); beyond it, speed is limited to 10 Mbps until the next month.

Who it's for

Who a PostgreSQL VPS Suits

  • Developers on Postgres-first frameworks

    Django, Rails and many Node apps default to PostgreSQL.

  • Teams that need extensions

    PostGIS, pgvector or TimescaleDB that managed plans restrict or charge extra for.

  • Teams splitting app and database

    The database on its own server, sized separately.

Running it well

Security and Performance for PostgreSQL

Security

  • Use scram-sha-256 and never trust authentication for remote hosts.
  • One role per application, owning only its database.
  • Keep 5432 closed except for known IPs, and use TLS between servers.
  • Apply minor releases promptly: they contain security fixes.

Performance

  • Start with shared_buffers at 25% of RAM and set effective_cache_size to reflect the rest.
  • Raise work_mem carefully: it applies per sort, per connection.
  • Use PgBouncer when apps open many connections.
  • Find slow queries with pg_stat_statements and EXPLAIN ANALYZE.
PostgreSQL VPS FAQs

Questions Before You Deploy

Not covered here? Ask an engineer before you order.

Run PostgreSQL on Your Own Server

Pick a plan sized for your data and tell us which servers should connect. We hand over PostgreSQL installed, tuned and secured.

Deploy Your VPS Talk to an Engineer