Local AI Packaged

Local AI Packaged: Self-hosted AI starter kit: n8n, Supabase, Ollama, Open WebUI, Flowise, Qdrant, Neo4j, SearXNG and Langfuse behind Caddy

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

What's included

Service	Port	Description
flowise	internal	flowiseai/flowise:3.1.3
open-webui	internal	Web UI
qdrant	internal	Vector database
neo4j	internal	neo4j:2026.09.0-community
searxng	internal	searxng/searxng:2026.10.13-22c64b8d3
ollama-cpu	internal	LLM runtime
ollama-gpu	internal	LLM runtime
ollama-gpu-amd	internal	LLM runtime
ollama-pull	internal	LLM runtime
langfuse-worker	internal	Background worker
langfuse-web	internal	Web UI
clickhouse	internal	Database
minio	internal	Object storage
redis	internal	Cache
postgres	internal	Database
studio	internal	Dashboard UI
api-gw	internal	API gateway
auth	internal	supabase/gotrue:v2.196.0
rest	internal	Database
realtime	internal	supabase/realtime:v2.134.10
storage	internal	API server
imgproxy	internal	Image processing
meta	internal	Database
functions	internal	supabase/edge-runtime:v1.76.2
db	internal	Database
supavisor	internal	supabase/supavisor:2.9.12
lap-caddy	80 (public), 443 (public), 8001 (public), 8002 (public), 8003 (public), 8005 (public), 8007 (public), 8008 (public)	Web server
lap-n8n	internal	n8nio/n8n:2.43.6

What you configure

• Domain (commonDomain): the hostname the stack is served on
• SUPABASE_PUBLISHABLE_KEY: you provide this in the deploy form
• SUPABASE_SECRET_KEY: you provide this in the deploy form
• OPENAI_API_KEY: you provide this in the deploy form
• SUPABASE_PUBLISHABLE_KEY: you provide this in the deploy form
• SUPABASE_SECRET_KEY: you provide this in the deploy form

All 71 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 28 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/local-ai-packaged

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

# Deploy
stacker deploy