Skip to main content
Many good tools exist for running a homelab. This section helps you find the one that fits what you want. It is information, not a ranking. Each detail page says what the other tool does well and when it is the right choice today, and it states the limits kombify has today.

​
Pick by what you want

These tools overlap in places, and many people run two or three of them together.

​
Where kombify sits

kombify defines the whole homelab in one declarative file. StackKits turns that definition into a plan, applies it and verifies the result. Sign-in, an access policy per service, routing, backup and updates are part of the definition and are set up by default. Techstack operates the homelab, and kombify Cloud and kombify AI are optional. The same definition describes a server at home and a server in the cloud. kombify is a layer beside and on top of the tools above. It does not replace a hypervisor, a NAS operating system or an app platform.

​
What kombify does today

  • Sign-in with passkeys through Pocket ID, with no default passwords.
  • An explicit access policy for each service.
  • Restore into an isolated staging copy before you switch over.
  • Updates that take a snapshot first.
  • Plan, apply and verify from one definition.
  • A local MCP server on every install, so your own AI agent can read and operate the homelab. See Connect your own AI agent.

​
Limits today

  • kombify is before 1.0 and releases often.
  • Compatibility is still being verified. See OS compatibility.
  • Installation needs a prepared Linux host and one command. There is no boot image yet.
  • kombify does not manage disks or RAID.
  • 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.
  • Connected and Managed by kombify are in preview.

​
Detail pages

Last reviewed: 2026-11-10