How they fit together
kombify and Coolify do different jobs. Coolify is an app platform. kombify is a layer beside and on top of it. kombify defines the homelab: identity, access policy, routing, backup and updates. Coolify is one way to build and deploy your own apps on that homelab.The current state of the integration
The integration is in development.- StackKits can install Coolify as an optional platform, selected explicitly. It is never part of the default workspace. See Coolify.
- The Marketplace use case, an app store on your homelab with Coolify as its engine, is a draft. The runtime proof, backup and restore, and full acceptance at the current release are pending.
- Workload backup and restore are not supplied by the Coolify adapter for every workload. See Application delivery compatibility.
- Apps that you install from Coolify’s own store belong to Coolify and to you. kombify does not own them.
What Coolify does well
- Deploy from a Git repository with build steps.
- Run databases and services next to your apps.
- Manage several servers from one interface.
- Reach a large library of ready services.
Limits of kombify today
- kombify is before 1.0 and releases often.
- Compatibility is still being verified. See OS compatibility for the current rows.
- Installation needs a prepared Linux host and one command. There is no boot image.
- Bringing your own Compose project under the homelab’s sign-in, routing and backup is not implemented.
- The catalog is curated and listed in the use-case catalog.
What kombify does today
- Passkey sign-in through Pocket ID, no default passwords.
- An explicit access policy per service.
- Restore into an isolated staging copy.
- Updates that take a snapshot first.
- Plan, apply and verify from one definition.
- A local MCP server on every install for your own AI agent.
