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.
In everyday terms: an app on your own server normally has an address that only works at home. kombify.me can give it a normal web address that works from anywhere, with a padlock (HTTPS) already in place. You decide which apps get an address and which stay private.

​
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

​
Where to start

  1. Read Public, private or redirect: which one do I need? to pick the kind of address that matches where your app lives.
  2. Follow Get your first kombify.me address to choose a name, point it at your app and switch it on.
  3. If you use a StackKits server, see Use an address with a StackKits server.
  4. Later, change, pause or remove an address when you need to.

​
If something goes wrong

Start with kombify.me troubleshooting. It lists what a visitor sees for each situation and what to check.

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.