Supabase Posthog

Supabase Posthog: Product analytics stack pairing PostHog with Supabase backend services. Analyze usage with event capture and session replay.

Deploy from this page: TryDirect provisions the server, starts the services, generates the deployment credentials and wires the 10 containers together. Nothing is shared between deployments and no secrets ship with the stack.

What's included

Service	Port	Description
app	8000 (public), 8443 (public)	API gateway
db	5432 (local only)	Database
studio	3000 (local only)	Dashboard UI
auth	internal	supabase/gotrue:v2.189.0
rest	internal	Database
realtime	internal	supabase/realtime:v2.102.3
storage	internal	API server
imgproxy	internal	Image processing
meta	internal	Database
posthog	8000 (public on 8001)	python:3.11-alpine

What you configure

• Domain (commonDomain): the hostname the stack is served on

All 28 credentials (passwords and keys) are generated per deployment and stored in your project's secret store.

Requirements

• A cloud account connected to TryDirect (the deploy form provisions

the server) or one of your own servers

• A server that fits 10 containers (4 GB RAM or more recommended)
• A DNS record for the domain you set in the deploy form

Alternative: deploy with the Stacker CLI

Everything above also works from the command line:

git clone https://github.com/trydirect/awesome-selfhosted-stacker.git
cd awesome-selfhosted-stacker/stacker-projects/supabase-posthog

# Generate secrets
cp .env.example .env
./scripts/generate-secrets.sh

# Deploy
stacker deploy