About
Self-hosting shouldn't require a second job.
We think services and data belong on hardware their owners control. What stops most people isn't running the software — it's the internet side of the problem.
Getting a service you run at home or in your office safely onto the public internet has traditionally meant a static IP or dynamic-DNS hackery, router port forwarding, a reverse proxy, certificate renewal, and a permanent, low-grade worry about what you've exposed. Every one of those steps is undifferentiated plumbing — and each one is a reason people give up and hand their data to someone else's cloud.
Edgible does the plumbing. A gateway we operate is the public face; an encrypted WireGuard tunnel — established outbound by your device — carries traffic to your machine, where TLS terminates and your service answers. Deployments are declarative YAML, certificates are managed, and your hardware never accepts an inbound connection.
The result is a deal we think is fair: you keep the hardware, the data, and the workload. We handle the part of the internet nobody self-hosts for fun.
01 — Your hardware is the product's home
Workloads run on machines you own. The gateway relays encrypted traffic; it doesn't host your application or read your TLS sessions.
02 — Security by architecture, not policy
No inbound ports, WireGuard on every tunnel, TLS terminating on your device. The safe configuration is the only configuration.
03 — Say what it does
Our docs and this site describe the platform as it is — including its current constraints. If we haven't built it, we don't market it.