Best VPS for Supabase Hosting in 2026

Self-hosting Supabase gives you complete control over your backend-as-a-service platform. Running your own Supabase instance requires careful VPS selection to handle PostgreSQL, real-time subscriptions, and API services efficiently. If you’re new to VPS hosting, check our VPS buying guide first. Here are the top VPS providers for Supabase hosting.

Why VPS Specs Matter for Supabase

Supabase is a comprehensive platform with multiple components that need proper resources:

• PostgreSQL Database: Requires substantial RAM (4GB+ recommended) for query performance and connections
• Real-time Engine: WebSocket connections need good CPU performance for low latency
• Storage Engine: Fast NVMe SSD essential for database operations and file uploads
• API Gateway: Multiple services (PostgREST, GoTrue, Storage) need adequate CPU resources
• Memory: Database caching, connection pooling, and real-time subscriptions are RAM-intensive

Top VPS for Supabase

Hostinger’s VPS offers excellent value for Supabase hosting. Their NVMe storage ensures fast database operations, while 8GB RAM handles PostgreSQL and real-time connections smoothly.

Pros:

• High-performance NVMe SSD storage
• Competitive pricing for specs offered
• Good CPU performance for API services
• 24/7 support for technical issues
• Easy scaling options

Cons:

• Limited to specific data center locations
• Basic control panel compared to alternatives

DigitalOcean’s droplets are popular among developers for Supabase deployments. Their marketplace includes one-click Supabase installation options.

Pros:

• Excellent documentation and tutorials
• Managed PostgreSQL option available
• Strong developer community
• Multiple data center regions
• Predictable pricing

Cons:

• More expensive than competitors
• Basic specs for the price point
• No NVMe on entry-level plans

Hetzner provides exceptional hardware specs for the price, making it ideal for resource-intensive Supabase deployments.

Pros:

• Outstanding price-to-performance ratio
• High RAM allocation perfect for PostgreSQL
• NVMe storage included
• European data centers
• No traffic limits

Cons:

• Limited to European locations
• English support during EU hours only
• More complex setup for beginners

Supabase Docker Setup

Here’s how to deploy Supabase on your VPS using Docker:

# Install Docker and Docker Compose
curl -fsSL https://get.docker.com -o get-docker.sh
sudo sh get-docker.sh
sudo curl -L "https://github.com/docker/compose/releases/download/v2.24.0/docker-compose-$(uname -s)-$(uname -m)" -o /usr/local/bin/docker-compose
sudo chmod +x /usr/local/bin/docker-compose

# Clone Supabase Docker setup
git clone --depth 1 https://github.com/supabase/supabase.git
cd supabase/docker

# Configure environment
cp .env.example .env
# Edit .env with your settings:
# - Set strong passwords for POSTGRES_PASSWORD, JWT_SECRET
# - Configure SITE_URL for your domain
# - Set SMTP settings for auth emails

# Start Supabase services
docker-compose up -d

# Verify services are running
docker-compose ps

Recommended Specs by Project Size

Small Projects (< 1,000 users)

• CPU: 2-4 vCPUs
• RAM: 4-8GB
• Storage: 80-160GB NVMe SSD
• Bandwidth: 2-4TB/month
• Recommended: Hostinger VPS 2 ($7.99/mo)

Medium Projects (1,000-10,000 users)

• CPU: 4-6 vCPUs
• RAM: 8-16GB
• Storage: 160-320GB NVMe SSD
• Bandwidth: 4-8TB/month
• Recommended: Hostinger VPS 4 ($14.99/mo)

Large Projects (10,000+ users)

• CPU: 6-8+ vCPUs
• RAM: 16-32GB
• Storage: 320GB+ NVMe SSD
• Bandwidth: 8TB+/month
• Recommended: Hetzner CPX31 or higher

Performance Optimization

PostgreSQL Configuration

-- Optimize PostgreSQL for your VPS RAM
ALTER SYSTEM SET shared_buffers = '2GB';  -- 25% of RAM
ALTER SYSTEM SET effective_cache_size = '6GB';  -- 75% of RAM
ALTER SYSTEM SET work_mem = '32MB';
ALTER SYSTEM SET maintenance_work_mem = '512MB';
ALTER SYSTEM SET max_connections = '100';
SELECT pg_reload_conf();

Docker Resource Limits

# In your docker-compose.yml
services:
  db:
    image: supabase/postgres:15.1.0.117
    deploy:
      resources:
        limits:
          memory: 4G
        reservations:
          memory: 2G

Real-time Optimization

• Configure connection pooling for WebSocket connections
• Set appropriate max_connections in PostgreSQL
• Monitor real-time subscription limits
• Use CDN for static assets and file storage

FAQ

Can I run Supabase on a 2GB RAM VPS?

While technically possible, 2GB RAM is too limited for production Supabase deployments. PostgreSQL alone needs 1-2GB, leaving little room for other services. Start with 4GB minimum for small projects.

Do I need managed PostgreSQL or can I use Docker?

Docker-based PostgreSQL works well for most Supabase deployments and keeps costs lower. Consider managed PostgreSQL only for high-availability requirements or if you lack database administration experience.

How much storage does Supabase need?

Base Supabase installation requires ~10GB. Plan additional storage for:

• Database growth (varies by project)
• File uploads (if using Supabase Storage)
• Logs and backups Start with 80-160GB and scale as needed.

Can I use Supabase Edge Functions on self-hosted instances?

Yes, self-hosted Supabase supports Edge Functions through Deno runtime. Ensure your VPS has adequate CPU resources as Edge Functions can be compute-intensive.

What about SSL certificates for custom domains?

Use Let’s Encrypt with nginx or Caddy as a reverse proxy. Supabase Docker setup includes Caddy configuration examples for automatic SSL certificate management.

Summary

For self-hosting Supabase, Hostinger offers the best balance of performance, price, and ease of use. Their NVMe storage and generous RAM allocations work perfectly for PostgreSQL workloads.

Hetzner provides exceptional value for larger projects needing more resources, while DigitalOcean remains a solid choice for developers who value documentation and managed service options.

Remember to:

• Size your VPS based on expected user load
• Configure PostgreSQL parameters for your available RAM
• Set up proper backups for your database
• Monitor resource usage and scale as your project grows
• Use a reverse proxy with SSL for production deployments