SupaScale 12-Container Supabase Docker Workbench Emblem SupaScale 12-Container Docker
  • 12-Container Workbench
  • Blueprints (8)
  • Comparisons (4)
  • Methodology
  • About
  • Contact
  • VI // TIẾNG VIỆT
    SUPASCALE // 12-CONTAINER SUPABASE DOCKER & MAU COST WORKBENCH

    Size All 12 Self-Hosted Supabase Docker Containers & Audit MAU Costs on SupaScale

    In our deterministic SupaScale container model, we sum per-service memory across all 12 official supabase/docker components (PostgreSQL 15 + pgvector, Supavisor, Kong, GoTrue, PostgREST, Realtime BEAM, Storage, ImgProxy, pg-meta, Studio, Deno Edge, and Logflare + Vector) plus a 20% kernel/autovacuum reserve so you avoid 2GB–4GB VPS OOM crashes.

    Toggle individual containers below to recalculate RAM live and export your custom docker-compose.override.yml.

  • 01 // 12-CONTAINER SELF-HOSTED SUPABASE DOCKER COMPOSE TOGGLE GRID (SUPASCALE)
    02 // GOTRUE MONTHLY ACTIVE USERS
    03 // POSTGRESQL + PGVECTOR DISK GB
    04 // COOLIFY / VDS STACK DENSITY
    2GB–4GB VPS OOM ALERT • LOGFLARE + IMGPROXY RESERVE 2.33 GB

    Enabling Logflare + Vector reserves 2.33 GB in Erlang BEAM + media heaps alone, pushing total stack demand to 8.88 GB. Provision a 16 GB tier or uncheck #12 Logflare + Vector to reclaim ~1.6 GB immediately.

    ACTIVE CONTAINERS RAM 6.86 GB 12/12 services (1 stack) POSTGRES BUFFER RESERVE 2.87 GB shared_buffers=3264MB RECOMMENDED SERVER TIER 16 GB RAM 4 vCPU • 200 GB NVMe CLOUD PRO BILL VS KVM SPEND $115.13/mo +$0 MAU • +$2 Disk · $104.64 (Self-host from $10.49/mo)

    SupaScale Per-Container Supabase Docker RAM & Limit Breakdown

    Docker Compose Service Official Image State Projected RAM Compose mem_limit
    #1. PostgreSQL 15 + pgvector (db) supabase/postgres:15.8.1 Active 1587 MB (1.55 GB) 1984m
    #2. Supavisor Pooler (supavisor) supabase/supavisor:1.1 Active 420 MB (0.41 GB) 525m
    #3. Kong API Gateway (kong) kong:2.8.1 Active 522 MB (0.51 GB) 653m
    #4. GoTrue Auth (auth) supabase/gotrue:v2.164 Active 133 MB (0.13 GB) 192m
    #5. PostgREST (rest) postgrest/postgrest:v12.2 Active 184 MB (0.18 GB) 230m
    #6. Realtime Elixir (realtime) supabase/realtime:v2.33 Active 686 MB (0.67 GB) 858m
    #7. Storage API (storage) supabase/storage-api:v1.11 Active 256 MB (0.25 GB) 320m
    #8. ImgProxy (imgproxy) darthsim/imgproxy:v3.8 Active 666 MB (0.65 GB) 833m
    #9. pg-meta (meta) supabase/postgres-meta:v0.84 Active 164 MB (0.16 GB) 205m
    #10. Supabase Studio (studio) supabase/studio:2026 Active 287 MB (0.28 GB) 359m
    #11. Deno Edge Runtime (functions) supabase/edge-runtime:v1.62 Active 399 MB (0.39 GB) 499m
    #12. Logflare + Vector Analytics (analytics) supabase/logflare:1.4 + vector:0.28 Active 1720 MB (1.68 GB) 2150m
    docker-compose.override.yml // SUPASCALE MEMORY GUARD GENERATOR
    # Generated by SupaScale Deterministic 12-Container Workbench
    # Target Profile: 50K MAU | 25 GB Postgres | 1 Stack(s) | 16 GB Host Tier
    services:
      db:
        mem_limit: 1984m
        command:
          - postgres
          - -c
          - shared_buffers=3264MB
          - -c
          - effective_cache_size=7424MB
          - -c
          - work_mem=16MB
      supavisor:
        mem_limit: 525m
      kong:
        mem_limit: 653m
        environment:
          KONG_NGINX_WORKER_PROCESSES: "2"
      auth:
        mem_limit: 192m
      rest:
        mem_limit: 230m
      realtime:
        mem_limit: 858m
      storage:
        mem_limit: 320m
      imgproxy:
        mem_limit: 832m
        environment:
          IMGPROXY_CONCURRENCY: "4"
          MALLOC_ARENA_MAX: "2"
      meta:
        mem_limit: 205m
      studio:
        mem_limit: 358m
      functions:
        mem_limit: 499m
      analytics:
        mem_limit: 2150m
        environment:
          ERL_FLAGS: "+MBas aobf +MBlmbcs 512"
      vector:
        mem_limit: 320m

    SupaScale Matched Self-Hosted KVM VPS & Dedicated VDS Loadouts

    Rehearsing a zero-downtime PostgreSQL Logical Replication cutover from Supabase Cloud first? Check Vultr $300 30-Day Staging Credit for Supabase Migration on SupaScale →

    SupaScale Public Supabase Cloud & KVM/VDS Vendor Pricing Audit (Retrieved 2026-11-12)

    In our deterministic SupaScale pricing ledger, we cite published vendor tariffs retrieved 2026-11-12. Promotional introductory discounts and renewal rates may change — always verify final terms on the vendor's official checkout page before purchasing.

    Vendor & Snapshot Date Published Tiers & Overage Rates (2026-11-12) Official Public Source URL Partner Checkout / Reference
    Supabase Cloud Pro
    2026-11-12
    Pro Base $25/mo ($10 compute credit, 100K MAU, 8 GB DB disk, 250 GB egress) + Small–2XL Compute ($15–$410/mo), +$0.00325/MAU >100K, +$0.125/GB DB disk >8 GB, +$100/mo 7-day PITR https://supabase.com/pricing Managed Cloud Baseline (Non-Affiliate)
    Hostinger KVM NVMe VPS
    2026-11-12
    KVM 1 (4 GB, $4.99/mo promo / $13.99/mo regular), KVM 2 (8 GB, $5.99/mo promo / $16.99/mo regular), KVM 4 (16 GB, $10.49/mo promo / $27.99/mo regular), KVM 8 (32 GB, $19.99/mo promo / $49.99/mo regular) https://www.hostinger.com/vps-hosting Check Hostinger KVM Coolify Rates for Supabase on SupaScale →
    Vultr High Frequency NVMe
    2026-11-12
    High Frequency 3.5GHz+ local Gen4 NVMe: 8 GB / 3 vCPU ($48.00/mo), 16 GB / 4 vCPU ($96.00/mo), 32 GB / 8 vCPU ($192.00/mo) — hourly metered billing in Singapore, Tokyo, EU & US https://www.vultr.com/pricing/ Explore Vultr 3.5GHz+ HF Rates for Supabase on SupaScale →
    UltaHost Dedicated VDS / VPS
    2026-11-12
    Dedicated physical DDR5 & 0% CPU-steal VDS: 32 GB / 6 Dedicated Cores ($37.50/mo promo / $62.50/mo regular), 64 GB / 8 Cores ($68.00/mo), 128 GB / 16 Cores ($129.00/mo) with unmetered fair-use port https://ultahost.com/vps-hosting Inspect UltaHost Dedicated VDS Rates for Supabase on SupaScale →
    InterServer Price-Lock VPS & Storage
    2026-11-12
    Month-to-month Price-Lock KVM & Storage slices: 16 GB / 320 GB SSD ($24.00/mo), 32 GB / 640 GB SSD ($48.00/mo), Dedicated Ryzen 64 GB / 2 TB NVMe ($89.00/mo) — zero renewal hike https://www.interserver.net/vps/ Review InterServer Price-Lock Rates for Supabase on SupaScale →
    ChemiCloud LiteSpeed NVMe Web
    2026-11-12
    Managed LiteSpeed NVMe edge web hosting (for decoupling docs, marketing sites & SMTP off your Supabase DB IP): Starter ($2.95/mo promo / $9.95/mo regular), Turbo ($5.45/mo promo / $14.95/mo regular) https://chemicloud.com/web-hosting/ Check ChemiCloud Edge Web Rates for Supabase Docs on SupaScale →

    SupaScale pricing notice: Public rates retrieved 2026-11-12; promotional & renewal prices may change — always verify on the vendor’s official checkout page.

    SupaScale Honest Trade-Off Matrix: Managed Supabase Cloud Pro vs Self-Hosted Docker

    When Managed Supabase Cloud Pro Beats Self-Hosting — SupaScale Guidance

    We recommend staying on Managed Supabase Cloud Pro ($25/mo) when validating a single pre-revenue MVP below 50,000 MAU and 8 GB disk, when your team wants zero Linux SSH or WAL-G backup maintenance, or when enterprise buyers mandate turnkey SOC2 Type II / HIPAA BAA compliance.

    When Self-Hosted Docker on KVM/VDS Wins — SupaScale Guidance

    Self-hosting via Coolify v4 or Docker Compose on 16 GB KVM 4 and Dedicated VDS cuts monthly spend by 75%–92% once GoTrue passes 100,000 MAU ($0.00325/MAU), PostgreSQL + pgvector HNSW indexes exceed 25 GB, media egress climbs past 250 GB, or you consolidate 3 to 8 isolated client stacks.

    SupaScale Technical Architecture & Cost Topology Diagrams (4 Original SVGs)

    SupaScale 12-Container Supabase Docker Compose Memory Allocation Bar Map
    Diagram 1 (SupaScale): 12-service Supabase Docker RAM allocation at 50K MAU vs 2GB and 4GB VPS OOM thresholds.
    SupaScale Supabase Cloud Pro 100K MAU Overage Curve vs Flat KVM Spend
    Diagram 2 (SupaScale): Supabase Cloud Pro $0.00325/MAU >100K overage curve compared against flat KVM/VDS billing.
    SupaScale Kong Port 8000 API Gateway and Supavisor Port 6543 Pooler Topology
    Diagram 3 (SupaScale): Kong :8000 JWT gateway and Supavisor :6543 pooler shielding internal PostgreSQL :5432.
    SupaScale Coolify Multi-Project Isolation and 3-2-1 Off-Host WAL-G Backup Vault
    Diagram 4 (SupaScale): Coolify v4 multi-project isolation paired with encrypted 60-second WAL-G off-host S3 backups.
    SUPASCALE 15-SECOND VERTICAL BRIEFING (9:16 HD MP4)

    SupaScale Video Briefing: Why 12-Container Supabase Docker OOMs on 4GB Cloud VPS

    In our deterministic SupaScale sizing model, we map memory reservations across PostgreSQL 15, Kong, GoTrue, Realtime BEAM, PostgREST, ImgProxy, and Logflare so you avoid 4 GB VPS crashes and $0.00325/MAU Cloud overages.

    8 Self-Hosted Supabase Docker Production Blueprints on SupaScale

    4 Supabase Docker vs Cloud Pro & BaaS Cost Audits on SupaScale

    SupaScale Frequently Asked Self-Hosted Supabase Docker Questions

    Why does SupaScale flag 2GB and 4GB cloud VPS tiers as OOM traps for 12-container Supabase Docker?

    In our deterministic SupaScale container model, three Erlang/BEAM runtimes (Logflare + Vector ~1.52 GB, Realtime ~390 MB, Supavisor ~340 MB) plus Kong Nginx/LuaJIT (~440 MB) and ImgProxy libvips reserve over 3.2 GB before PostgreSQL 15 even allocates shared_buffers. Deploying an 8 GB–16 GB KVM node or unchecking #12 Logflare + Vector prevents Linux oom-killer crashes.

    Does unchecking #12 Logflare + Vector in the SupaScale grid break Supabase Studio or GoTrue Auth?

    No. Core PostgreSQL 15, GoTrue Auth, PostgREST, Realtime, and Storage operate independently of Logflare. The SupaScale override generator sets profiles: ["disabled"] on analytics/vector and NEXT_PUBLIC_ENABLE_LOGS="false" on Studio, reclaiming ~1.52 GB of idle RAM cleanly.

    How does SupaScale calculate Supabase Cloud Pro $0.00325/MAU and $0.125/GB disk overages?

    We apply published rates retrieved 2026-11-12 from supabase.com/pricing: $25/mo Pro base (includes 100K MAU and 8 GB DB disk) + Dedicated Compute add-on ($15–$410/mo) + $0.00325 per GoTrue MAU above 100,000 + $0.125/GB disk above 8 GB + $100/mo when 7-day PITR applies.

    When does SupaScale recommend staying on Managed Supabase Cloud Pro instead of self-hosting?

    We recommend Managed Supabase Pro ($25/mo) for single-environment MVPs under 50,000 MAU and 8 GB database storage, teams without Linux SSH/backup familiarity, or regulatedhealthcare/fintech workloads requiring turnkey SOC2 Type II and HIPAA BAA coverage.

    How should engineers firewall PostgreSQL port 5432 when deploying the SupaScale Compose override?

    Never bind PostgreSQL 5432 to 0.0.0.0 on a public interface. Keep db inside the private Docker bridge network, route client SDK traffic over TLS 443 to Kong via Coolify/Traefik, and gate Supabase Studio behind Basic Auth or a WireGuard/Tailscale mesh.