How to run self-hosted Supabase without the Analytics/Logflare container? #46306

ghost · 2026-05-24T07:17:57Z

ghost
May 24, 2026

I'm trying to self-host Supabase using Docker Compose but I don't need the analytics/logging stack (Logflare + ClickHouse). It uses a lot of memory on my small VPS. Is it safe to remove those services from the docker-compose.yml? Will anything break?

Answered by kabincs9

May 24, 2026

Yes,
it's possible to run Supabase self-hosted without the analytics stack. You can remove or comment out the analytics and vector services from docker-compose.yml. A few things to note:

Set LOGFLARE_LOGGER_BACKEND_API_KEY to any dummy value — some services check for it on startup.
In kong.yml, remove or comment out the routes that proxy to the analytics service, otherwise Kong will error trying to reach a container that doesn't exist.
The Studio dashboard's "Logs" section will stop working since it queries Logflare. Everything else (Auth, Storage, DB, Realtime) continues normally.

This is a common setup for resource-constrained environments. Hope that helps!

View full answer

kabincs9 · 2026-05-24T07:19:40Z

kabincs9
May 24, 2026

Yes,
it's possible to run Supabase self-hosted without the analytics stack. You can remove or comment out the analytics and vector services from docker-compose.yml. A few things to note:

Set LOGFLARE_LOGGER_BACKEND_API_KEY to any dummy value — some services check for it on startup.
In kong.yml, remove or comment out the routes that proxy to the analytics service, otherwise Kong will error trying to reach a container that doesn't exist.
The Studio dashboard's "Logs" section will stop working since it queries Logflare. Everything else (Auth, Storage, DB, Realtime) continues normally.

This is a common setup for resource-constrained environments. Hope that helps!

2 replies

aantti May 24, 2026
Maintainer

Set LOGFLARE_LOGGER_BACKEND_API_KEY to any dummy value

This isn't needed.

Overall, yes, correct, analytics & vector can just be removed from docker-compose.yml.

anonymity12 Jun 30, 2026

yes, Kong works well even u dont change any thing in volumes/api/kong.yml. since analytics section is comment-out already( in my 2026.02 version). so we just remove analytics & vector parts in docker-compose.yml(AND any depends_on sections that contain analytics); then do docker compose up -d --remove-orphans, wait a while, see the memory is free!

if anyone need to re-check, here is my yml file, after carefully compare to 2026.06.30 repo version and rewrite:(note that i added some deploy resources limits section to solve the memory problem before 2026.05, but it seems useless now)

name: supabase
services:
  studio:
    container_name: supabase-studio
    image: 'supabase/studio:2026.02.16-sha-26c615c'
    restart: unless-stopped
    healthcheck:
      test:
        - CMD
        - node
        - '-e'
        - >-
          fetch('http://studio:3000/api/platform/profile').then((r) => {if
          (r.status !== 200) throw new Error(r.status)})
      timeout: 10s
      interval: 5s
      retries: 3
      start_period: 20s
    environment:
      HOSTNAME: '::'
      STUDIO_PG_META_URL: 'http://meta:8080'
      POSTGRES_PORT: '${POSTGRES_PORT}'
      POSTGRES_HOST: '${POSTGRES_HOST}'
      POSTGRES_DB: '${POSTGRES_DB}'
      POSTGRES_PASSWORD: '${POSTGRES_PASSWORD}'
      PG_META_CRYPTO_KEY: '${PG_META_CRYPTO_KEY}'
      DEFAULT_ORGANIZATION_NAME: '${STUDIO_DEFAULT_ORGANIZATION}'
      DEFAULT_PROJECT_NAME: '${STUDIO_DEFAULT_PROJECT}'
      OPENAI_API_KEY: '${OPENAI_API_KEY:-}'
      SUPABASE_URL: 'http://kong:8000'
      SUPABASE_PUBLIC_URL: '${SUPABASE_PUBLIC_URL}'
      SUPABASE_ANON_KEY: '${ANON_KEY}'
      SUPABASE_SERVICE_KEY: '${SERVICE_ROLE_KEY}'
      AUTH_JWT_SECRET: '${JWT_SECRET}'
      SNIPPETS_MANAGEMENT_FOLDER: /app/snippets
      EDGE_FUNCTIONS_MANAGEMENT_FOLDER: /app/edge-functions
    volumes:
      - './volumes/snippets:/app/snippets:Z'
      - './volumes/functions:/app/edge-functions:Z'
  kong:
    container_name: supabase-kong
    image: 'kong:2.8.1'
    restart: unless-stopped
    ports:
      - '${KONG_HTTP_PORT}:8000/tcp'
      - '${KONG_HTTPS_PORT}:8443/tcp'
    volumes:
      - './volumes/api/kong.yml:/home/kong/temp.yml:ro,z'
    depends_on:
      studio:
        condition: service_healthy
    environment:
      KONG_DATABASE: 'off'
      KONG_DECLARATIVE_CONFIG: /home/kong/kong.yml
      KONG_DNS_ORDER: 'LAST,A,CNAME'
      KONG_PLUGINS: >-
        request-transformer,cors,key-auth,acl,basic-auth,request-termination,ip-restriction
      KONG_NGINX_PROXY_PROXY_BUFFER_SIZE: 160k
      KONG_NGINX_PROXY_PROXY_BUFFERS: 64 160k
      SUPABASE_ANON_KEY: '${ANON_KEY}'
      SUPABASE_SERVICE_KEY: '${SERVICE_ROLE_KEY}'
      DASHBOARD_USERNAME: '${DASHBOARD_USERNAME}'
      DASHBOARD_PASSWORD: '${DASHBOARD_PASSWORD}'
    entrypoint: >-
      bash -c 'eval "echo \"$$(cat ~/temp.yml)\"" > ~/kong.yml &&
      /docker-entrypoint.sh kong docker-start'
  auth:
    container_name: supabase-auth
    image: 'supabase/gotrue:v2.186.0'
    restart: unless-stopped
    healthcheck:
      test:
        - CMD
        - wget
        - '--no-verbose'
        - '--tries=1'
        - '--spider'
        - 'http://localhost:9999/health'
      timeout: 5s
      interval: 5s
      retries: 3
    depends_on:
      db:
        condition: service_healthy
    environment:
      GOTRUE_API_HOST: 0.0.0.0
      GOTRUE_API_PORT: 9999
      API_EXTERNAL_URL: '${API_EXTERNAL_URL}'
      GOTRUE_DB_DRIVER: postgres
      GOTRUE_DB_DATABASE_URL: >-
        postgres://supabase_auth_admin:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_DB}
      GOTRUE_SITE_URL: '${SITE_URL}'
      GOTRUE_URI_ALLOW_LIST: '${ADDITIONAL_REDIRECT_URLS}'
      GOTRUE_DISABLE_SIGNUP: '${DISABLE_SIGNUP}'
      GOTRUE_JWT_ADMIN_ROLES: service_role
      GOTRUE_JWT_AUD: authenticated
      GOTRUE_JWT_DEFAULT_GROUP_NAME: authenticated
      GOTRUE_JWT_EXP: '${JWT_EXPIRY}'
      GOTRUE_JWT_SECRET: '${JWT_SECRET}'
      GOTRUE_EXTERNAL_EMAIL_ENABLED: '${ENABLE_EMAIL_SIGNUP}'
      GOTRUE_EXTERNAL_ANONYMOUS_USERS_ENABLED: '${ENABLE_ANONYMOUS_USERS}'
      GOTRUE_MAILER_AUTOCONFIRM: '${ENABLE_EMAIL_AUTOCONFIRM}'
      GOTRUE_SMTP_ADMIN_EMAIL: '${SMTP_ADMIN_EMAIL}'
      GOTRUE_SMTP_HOST: '${SMTP_HOST}'
      GOTRUE_SMTP_PORT: '${SMTP_PORT}'
      GOTRUE_SMTP_USER: '${SMTP_USER}'
      GOTRUE_SMTP_PASS: '${SMTP_PASS}'
      GOTRUE_SMTP_SENDER_NAME: '${SMTP_SENDER_NAME}'
      GOTRUE_MAILER_URLPATHS_INVITE: '${MAILER_URLPATHS_INVITE}'
      GOTRUE_MAILER_URLPATHS_CONFIRMATION: '${MAILER_URLPATHS_CONFIRMATION}'
      GOTRUE_MAILER_URLPATHS_RECOVERY: '${MAILER_URLPATHS_RECOVERY}'
      GOTRUE_MAILER_URLPATHS_EMAIL_CHANGE: '${MAILER_URLPATHS_EMAIL_CHANGE}'
      GOTRUE_EXTERNAL_PHONE_ENABLED: '${ENABLE_PHONE_SIGNUP}'
      GOTRUE_SMS_AUTOCONFIRM: '${ENABLE_PHONE_AUTOCONFIRM}'
  rest:
    container_name: supabase-rest
    image: 'postgrest/postgrest:v14.5'
    restart: unless-stopped
    depends_on:
      db:
        condition: service_healthy
    environment:
      PGRST_DB_URI: >-
        postgres://authenticator:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_DB}
      PGRST_DB_SCHEMAS: '${PGRST_DB_SCHEMAS}'
      PGRST_DB_ANON_ROLE: anon
      PGRST_JWT_SECRET: '${JWT_SECRET}'
      PGRST_DB_USE_LEGACY_GUCS: 'false'
      PGRST_APP_SETTINGS_JWT_SECRET: '${JWT_SECRET}'
      PGRST_APP_SETTINGS_JWT_EXP: '${JWT_EXPIRY}'
    command:
      - postgrest
  realtime:
    container_name: realtime-dev.supabase-realtime
    image: 'supabase/realtime:v2.76.5'
    restart: unless-stopped
    depends_on:
      db:
        condition: service_healthy
    healthcheck:
      test:
        - CMD-SHELL
        - >-
          curl -sSfL --head -o /dev/null -H "Authorization: Bearer ${ANON_KEY}"
          http://localhost:4000/api/tenants/realtime-dev/health
      timeout: 5s
      interval: 30s
      retries: 3
      start_period: 10s
    environment:
      PORT: 4000
      DB_HOST: '${POSTGRES_HOST}'
      DB_PORT: '${POSTGRES_PORT}'
      DB_USER: supabase_admin
      DB_PASSWORD: '${POSTGRES_PASSWORD}'
      DB_NAME: '${POSTGRES_DB}'
      DB_AFTER_CONNECT_QUERY: SET search_path TO _realtime
      DB_ENC_KEY: supabaserealtime
      API_JWT_SECRET: '${JWT_SECRET}'
      SECRET_KEY_BASE: '${SECRET_KEY_BASE}'
      ERL_AFLAGS: '-proto_dist inet_tcp'
      DNS_NODES: ''''''
      RLIMIT_NOFILE: '10000'
      APP_NAME: realtime
      SEED_SELF_HOST: 'true'
      RUN_JANITOR: 'true'
      DISABLE_HEALTHCHECK_LOGGING: 'true'
  storage:
    container_name: supabase-storage
    image: 'supabase/storage-api:v1.37.8'
    restart: unless-stopped
    depends_on:
      db:
        condition: service_healthy
      rest:
        condition: service_started
      imgproxy:
        condition: service_started
    healthcheck:
      test:
        - CMD
        - wget
        - '--no-verbose'
        - '--tries=1'
        - '--spider'
        - 'http://storage:5000/status'
      timeout: 5s
      interval: 5s
      retries: 3
    environment:
      ANON_KEY: '${ANON_KEY}'
      SERVICE_KEY: '${SERVICE_ROLE_KEY}'
      POSTGREST_URL: 'http://rest:3000'
      PGRST_JWT_SECRET: '${JWT_SECRET}'
      DATABASE_URL: >-
        postgres://supabase_storage_admin:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_DB}
      REQUEST_ALLOW_X_FORWARDED_PATH: 'true'
      FILE_SIZE_LIMIT: 52428800
      STORAGE_BACKEND: file
      GLOBAL_S3_BUCKET: '${GLOBAL_S3_BUCKET}'
      FILE_STORAGE_BACKEND_PATH: /var/lib/storage
      TENANT_ID: '${STORAGE_TENANT_ID}'
      REGION: '${REGION}'
      ENABLE_IMAGE_TRANSFORMATION: 'true'
      IMGPROXY_URL: 'http://imgproxy:5001'
      S3_PROTOCOL_ACCESS_KEY_ID: '${S3_PROTOCOL_ACCESS_KEY_ID}'
      S3_PROTOCOL_ACCESS_KEY_SECRET: '${S3_PROTOCOL_ACCESS_KEY_SECRET}'
    volumes:
      - './volumes/storage:/var/lib/storage:z'
  imgproxy:
    container_name: supabase-imgproxy
    image: 'darthsim/imgproxy:v3.30.1'
    restart: unless-stopped
    volumes:
      - './volumes/storage:/var/lib/storage:z'
    healthcheck:
      test:
        - CMD
        - imgproxy
        - health
      timeout: 5s
      interval: 5s
      retries: 3
    environment:
      IMGPROXY_BIND: ':5001'
      IMGPROXY_LOCAL_FILESYSTEM_ROOT: /
      IMGPROXY_USE_ETAG: 'true'
      IMGPROXY_ENABLE_WEBP_DETECTION: '${IMGPROXY_ENABLE_WEBP_DETECTION}'
      IMGPROXY_MAX_SRC_RESOLUTION: 16.8
  meta:
    container_name: supabase-meta
    image: 'supabase/postgres-meta:v0.95.2'
    restart: unless-stopped
    depends_on:
      db:
        condition: service_healthy
    environment:
      PG_META_PORT: 8080
      PG_META_DB_HOST: '${POSTGRES_HOST}'
      PG_META_DB_PORT: '${POSTGRES_PORT}'
      PG_META_DB_NAME: '${POSTGRES_DB}'
      PG_META_DB_USER: supabase_admin
      PG_META_DB_PASSWORD: '${POSTGRES_PASSWORD}'
      CRYPTO_KEY: '${PG_META_CRYPTO_KEY}'
  functions:
    container_name: supabase-edge-functions
    image: 'supabase/edge-runtime:v1.70.3'
    restart: unless-stopped
    volumes:
      - './volumes/functions:/home/deno/functions:Z'
      - 'deno-cache:/root/.cache/deno'
    healthcheck:
      test:
        - CMD-SHELL
        - timeout 1 bash -c '</dev/tcp/127.0.0.1/9000'
      interval: 5s
      timeout: 5s
      retries: 3
    environment:
      JWT_SECRET: '${JWT_SECRET}'
      SUPABASE_URL: 'http://kong:8000'
      SUPABASE_PUBLIC_URL: '${SUPABASE_PUBLIC_URL}'
      SUPABASE_ANON_KEY: '${ANON_KEY}'
      SUPABASE_SERVICE_ROLE_KEY: '${SERVICE_ROLE_KEY}'
      SUPABASE_DB_URL: >-
        postgresql://postgres:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/${POSTGRES_DB}
      VERIFY_JWT: '${FUNCTIONS_VERIFY_JWT}'
    command:
      - start
      - '--main-service'
      - /home/deno/functions/main
  db:
    container_name: supabase-db
    image: 'supabase/postgres:15.8.1.085'
    restart: unless-stopped
    deploy:
      resources:
        limits:
          memory: 768M
        reservations:
          memory: 384M
    volumes:
      - >-
        ./volumes/db/realtime.sql:/docker-entrypoint-initdb.d/migrations/99-realtime.sql:Z
      - >-
        ./volumes/db/webhooks.sql:/docker-entrypoint-initdb.d/init-scripts/98-webhooks.sql:Z
      - >-
        ./volumes/db/roles.sql:/docker-entrypoint-initdb.d/init-scripts/99-roles.sql:Z
      - >-
        ./volumes/db/jwt.sql:/docker-entrypoint-initdb.d/init-scripts/99-jwt.sql:Z
      - './volumes/db/data:/var/lib/postgresql/data:Z'
      - >-
        ./volumes/db/_supabase.sql:/docker-entrypoint-initdb.d/migrations/97-_supabase.sql:Z
      - >-
        ./volumes/db/logs.sql:/docker-entrypoint-initdb.d/migrations/99-logs.sql:Z
      - >-
        ./volumes/db/pooler.sql:/docker-entrypoint-initdb.d/migrations/99-pooler.sql:Z
      - 'db-config:/etc/postgresql-custom'
    healthcheck:
      test:
        - CMD
        - pg_isready
        - '-U'
        - postgres
        - '-h'
        - localhost
      interval: 5s
      timeout: 5s
      retries: 10
    environment:
      POSTGRES_HOST: /var/run/postgresql
      PGPORT: '${POSTGRES_PORT}'
      POSTGRES_PORT: '${POSTGRES_PORT}'
      PGPASSWORD: '${POSTGRES_PASSWORD}'
      POSTGRES_PASSWORD: '${POSTGRES_PASSWORD}'
      PGDATABASE: '${POSTGRES_DB}'
      POSTGRES_DB: '${POSTGRES_DB}'
      JWT_SECRET: '${JWT_SECRET}'
      JWT_EXP: '${JWT_EXPIRY}'
    command:
      - postgres
      - '-c'
      - config_file=/etc/postgresql/postgresql.conf
      - '-c'
      - log_min_messages=fatal
  supavisor:
    container_name: supabase-pooler
    image: 'supabase/supavisor:2.7.4'
    restart: unless-stopped
    deploy:
      resources:
        limits:
          memory: 768M
        reservations:
          memory: 384M
    ports:
      - '${POSTGRES_PORT}:5432'
      - '${POOLER_PROXY_PORT_TRANSACTION}:6543'
    volumes:
      - './volumes/pooler/pooler.exs:/etc/pooler/pooler.exs:ro,z'
    healthcheck:
      test:
        - CMD
        - curl
        - '-sSfL'
        - '--head'
        - '-o'
        - /dev/null
        - 'http://127.0.0.1:4000/api/health'
      interval: 10s
      timeout: 5s
      retries: 5
    depends_on:
      db:
        condition: service_healthy
    environment:
      PORT: 4000
      POSTGRES_PORT: '${POSTGRES_PORT}'
      POSTGRES_DB: '${POSTGRES_DB}'
      POSTGRES_PASSWORD: '${POSTGRES_PASSWORD}'
      DATABASE_URL: >-
        ecto://supabase_admin:${POSTGRES_PASSWORD}@${POSTGRES_HOST}:${POSTGRES_PORT}/_supabase
      CLUSTER_POSTGRES: true
      SECRET_KEY_BASE: '${SECRET_KEY_BASE}'
      VAULT_ENC_KEY: '${VAULT_ENC_KEY}'
      API_JWT_SECRET: '${JWT_SECRET}'
      METRICS_JWT_SECRET: '${JWT_SECRET}'
      REGION: local
      ERL_AFLAGS: '-proto_dist inet_tcp'
      POOLER_TENANT_ID: '${POOLER_TENANT_ID}'
      POOLER_DEFAULT_POOL_SIZE: '${POOLER_DEFAULT_POOL_SIZE}'
      POOLER_MAX_CLIENT_CONN: '${POOLER_MAX_CLIENT_CONN}'
      POOLER_POOL_MODE: transaction
      DB_POOL_SIZE: '${POOLER_DB_POOL_SIZE}'
    command:
      - /bin/sh
      - '-c'
      - >-
        /app/bin/migrate && /app/bin/supavisor eval "$$(cat
        /etc/pooler/pooler.exs)" && /app/bin/server
volumes:
  db-config: null
  deno-cache: null

aantti · 2026-05-24T10:17:08Z

aantti
May 24, 2026
Maintainer

See also https://github.com/orgs/supabase/discussions/46084

1 reply

kabincs9 Jun 5, 2026

👍

Navigation Menu

Supabase

How to run self-hosted Supabase without the Analytics/Logflare container? #46306

Uh oh!

{{title}}

Uh oh!

Replies: 2 comments 3 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Supabase

How to run self-hosted Supabase without the Analytics/Logflare container? #46306

Uh oh!

ghost May 24, 2026

Replies: 2 comments · 3 replies

Uh oh!

kabincs9 May 24, 2026

Uh oh!

aantti May 24, 2026 Maintainer

Uh oh!

Uh oh!

anonymity12 Jun 30, 2026

Uh oh!

aantti May 24, 2026 Maintainer

Uh oh!

kabincs9 Jun 5, 2026

ghost
May 24, 2026

Replies: 2 comments 3 replies

kabincs9
May 24, 2026

aantti May 24, 2026
Maintainer

aantti
May 24, 2026
Maintainer