Self-hosting is appealing until you are the one babysitting it. deployable.sh is a catalogue of 138 production-ready Docker Compose stacks that deploy straight to Miget, so you get the tools you would self-host without running the servers yourself. Combined with Docker Compose Stacks on Miget, going from "I want Supabase" to a running, TLS-terminated instance takes a few clicks.
What deployable.sh is
Every entry in the catalogue is a real Docker Compose stack, organized across more than 30 categories:
- Databases: PostgreSQL, MongoDB, ClickHouse, and more
- Messaging and streaming: Kafka, Redpanda, RabbitMQ
- Backends: Supabase, PocketBase, Hasura
- Auth: Keycloak, Authentik, Zitadel
- AI and LLM tooling: Langfuse, LiteLLM, Open WebUI
- Business apps, media servers, game servers, and developer tools
Each stack is a plain compose.yaml that runs the same on your laptop, a VPS, or Miget. A small compose.miget.yaml overlay adds the platform-specific bits, so there is no lock-in - the base compose file stays portable.
Why deploy them on Miget
Running a stack like Supabase or Kafka yourself means provisioning a server, wiring up TLS, managing the database, and keeping it patched. On Miget, the Compose Stack does that for you:
- Managed Postgres and Valkey are detected in the compose file and provisioned as real Miget services, with backups and HA available.
- Clusters form themselves and services are auto-wired through injected connection variables.
- Every service gets a TLS domain out of the box.
- The whole stack runs in one Resource, so you pay for compute, not per service. A full backend starts at $5 per month.
Deploy a stack in three steps
- Pick a stack from the catalogue at deployable.sh.
- Point Miget at the repository and the stack's directory. Miget reads the compose file, detects each service, and shows you which environment variables it needs.
- Deploy. Miget provisions the managed services, builds the apps, assigns domains, and brings the stack up.
From there the stack behaves like any other Miget deployment. Push a change to the tracked branch and the stack reconciles: new services are added, changed services are updated, removed services are cleaned up.
An example: a full backend
Say you want a Supabase backend. Instead of standing up Postgres, the auth service, the REST layer, and storage by hand, you select the Supabase stack, point Miget at it, fill in the handful of required secrets that the analyzer surfaces, and deploy. Postgres comes up as a managed Miget database. The application services come up as apps. They are wired together and reachable over HTTPS, and you never touched a server.
Portability by design
Because each stack keeps a clean compose.yaml and isolates Miget-specific settings in compose.miget.yaml, your exit cost is zero. The same file you deploy to Miget runs locally with docker compose up or on any VPS. You are adopting a workflow, not a proprietary format.
Get started
- Browse the catalogue at deployable.sh.
- Read the Docker Compose Stacks documentation.
- Create your first stack on app.miget.com.
What to read next
- Docker Compose Stacks: Deploy Multi-Service Apps From One File - How Compose Stacks work on Miget
- How to Deploy a Python Celery Worker on Miget - Multiple services in one Resource
- Why Choose Miget - How Miget compares on price and features