Run 3+ Isolated Supabase Stacks on One Coolify VPS — SupaScale Docker Guide
SupaScale shows how indie builders replace multiple per-project Supabase Cloud compute bills by consolidating 3 isolated Docker stacks onto one 16 GB KVM 4 server.
SupaScale minimum floor: 16 GB RAM • Sweet-spot tier: 32 GB RAM (Public vendor rates retrieved 2026-11-12).
Deploying 3 unmodified Coolify Supabase templates spawns 39 containers including 3 duplicate Logflare + Vector stacks (~4.5 GB wasted on idle log sinks!). Always disable analytics and vector on secondary and staging Coolify stacks.
SupaScale Deterministic Memory Model Table: Run 3+ Isolated Supabase Stacks on One Coolify VPS
| Supabase Docker Subsystem | Baseline Idle Reserve | 50K MAU Projected Reserve | Memory Role |
|---|---|---|---|
| 1 Full Supabase Stack + Coolify Control Plane | 5.10 GB | 6.80 GB | 8GB KVM 2 Tight |
| 3 Unmodified Full Stacks (Logflare × 3) | 13.40 GB | 17.90 GB | Exceeds 16GB! |
| 3 Slimmed Coolify Stacks (Logflare Off) | 7.60 GB | 11.20 GB | Fits 16GB KVM 4 |
| 8+ Agency Client Stacks (Dedicated VDS) | 19.50 GB | 28.40 GB | 32GB–64GB VDS |
SupaScale Coolify Per-Stack Environment Isolation & Traefik Routing
# Stack A: api-saas1.yourdomain.io (Coolify Service Stack)
SERVICE_FQDN_SUPABASEKONG=https://api-saas1.yourdomain.io
POSTGRES_PASSWORD=${SERVICE_PASSWORD_POSTGRES}
JWT_SECRET=${SERVICE_PASSWORD_JWT}
PGRST_DB_SCHEMAS=public,storage,graphql_public
# Keep Postgres :5432 unexposed; route HTTPS cleanly via Coolify Traefik!
EXPOSE_POSTGRES_PORT=false
ENABLE_ANALYTICS=false1. SupaScale TCO Math: Why Per-Project Cloud Compute Multiplies Indie Costs
Managed Supabase Pro ($25/mo) bundles a single $10 compute credit covering one Micro shared-CPU instance. Spinning up a second SaaS product, an internal admin backend, and a staging environment adds separate compute charges every month before counting disk or MAU. In our SupaScale multi-stack model, running 3 Slim-mode stacks on Coolify v4 fits comfortably inside a 16 GB Hostinger KVM 4.
2. Preventing Kong & Supavisor Port Collisions in SupaScale Coolify Topologies
Raw upstream docker-compose binds host ports 8000 (Kong), 5432 (Postgres), and 6543 (Supavisor). Inside Coolify, remove host port mappings on Kong and route HTTPS via Traefik FQDN labels over port 443. For external Prisma or Drizzle schema migrations, map distinct firewall-restricted ports per stack (15431, 15432, 15433).
3. When SupaScale Recommends Graduating from Shared KVM to Dedicated Agency VDS
Once a fleet exceeds 4 to 5 active Supabase stacks on one virtual machine, concurrent PostgreSQL WAL fsync writes and Coolify Nixpacks builds compete for disk I/O. For 8+ client environments, we recommend moving to an UltaHost 32 GB or 64 GB Dedicated VDS for 0% noisy-neighbor CPU steal.
SupaScale Matched KVM & VDS Tiers for Run 3+ Isolated Supabase Stacks on One Coolify VPS
Hostinger KVM NVMe VPS (1-Click Docker / Coolify + Supabase) — SupaScale
From $4.99/mo (~127k)
12–24 mo KVM 2 (8GB) or KVM 4 (16GB) locks lowest rate + stacks Extra 20% partner discount.
Check Hostinger KVM VPS Specs for Run 3+ Isolated Supabase Stacks on One Coolify VPS on SupaScale →UltaHost Dedicated VDS (32GB–128GB Multi-Instance Agency) — SupaScale
From $37.5/mo (~956k)
Consolidate 8–15 client Supabase Pro orgs ($200–$600/mo) onto one 32GB–64GB VDS.
Compare UltaHost Agency VDS Options for Run 3+ Isolated Supabase Stacks on One Coolify VPS on SupaScale →SupaScale rate citation: Public vendor tariffs retrieved 2026-11-12; promotional and renewal prices change — verify exact checkout pricing before ordering.