Skip to main content
kombify.me gives a homelab service a stable HTTPS name on *.kombify.me. It is the optional connected-ingress path: useful when you want a public address, and unused when the stack stays on the local network.
kombify.me is Alpha software. Names, headers, and error shapes can still change. Do not treat this as a general-availability release.

​
What you can do

  • Open a kit service on a *.kombify.me host when the origin is already reachable on the public internet.
  • Keep first-party kit names such as auth on {your-lab}-auth.kombify.me, never on a reserved apex like auth.kombify.me.
  • Relay a private HTTP(S) target through the Techstack node agent when the origin is not public.
kombify.me does not replace StackKits. A local kit still installs, verifies, and runs without a kombify.me address.

​
How it fits

Publish a public service

Register an HTTPS name for a service that is already reachable.

Reach a private service

Use the optional relay when the origin stays on your network.