Overview

LeafLock runs anywhere Docker does. Pick the option that matches how you ship software and follow the linked page. Everything here stays lean so you are not reading the same advice twice.

Platform Snapshot

Platform	Best For	Why Choose It
Railway	Fastest path to a hosted instance	Git-based deploys, zero infrastructure maintenance
Coolify	Self-hosted control with a UI	Bring-your-own server, Docker Compose stays first-class
Docker Compose	Local or custom servers	Full control, easy to integrate with existing stacks
Kubernetes	Enterprises and complex scaling	Works with any cluster, fits GitOps/Argo workflows

Quick Starts

• Need a production environment today? Follow the Railway steps.
• Running your own hardware? Jump to the Coolify page.
• Building bespoke infrastructure? Start with the Docker Compose notes, then adapt.
• Already have a cluster? Go straight to Kubernetes.

Before You Deploy

All platforms share the same requirements:

• Generate POSTGRES_PASSWORD, REDIS_PASSWORD, JWT_SECRET, and SERVER_ENCRYPTION_KEY with openssl rand
• Point CORS_ORIGINS and VITE_API_URL at the URL your users will hit
• Keep ENABLE_REGISTRATION=false unless you want public sign-ups on day one
• Expose 8080 for the backend and 80 (or your chosen ingress) for the frontend

Keep the Reference page open for variable names, ports, and health endpoints.

After Deploying

• Walk through the short Readiness checklist
• Hit /api/v1/health and verify the UI can create an encrypted note
• Rotate secrets and reboot once to prove everything survives restarts

Need Help?

Head to Troubleshooting for platform-specific fixes (starting with Railway), or open a GitHub issue if something new breaks. The goal is to keep each document focused so you spend time shipping, not reading.