What is Edgible?
Edgible is a platform for publishing services that run on hardware you control — a workstation, a server in your office, a small box at the edge of a network — without making that hardware itself reachable from the internet.
You install a small agent on each machine you want to serve from. You authenticate it against your Edgible organization. From that point on, you describe what you want to run in YAML and Edgible takes care of:
- Routing public traffic from the internet to your machine over an encrypted tunnel.
- Issuing and rotating TLS certificates for every hostname you publish.
- Starting, monitoring, and stopping your workloads (Docker Compose stacks, single containers, processes, or VMs).
- Enforcing access policy — public, organization-only, API-key, or short-code.
What the platform is not: a place where your code runs. Your workloads keep running on your own hardware. Edgible is the control plane and the public-facing edge — a thin layer that turns “a service on my machine” into “a service on the internet” without surrendering custody of the machine.
Who uses it
Section titled “Who uses it”- Builders self-hosting their own SaaS — run the API, the database, and the web app on a single box at home, expose just the web app at
app.example.com, keep the database internal. - Teams running on-premises infrastructure — give a remote engineer access to an internal tool without standing up a VPN, opening firewalls, or routing through a public load balancer.
- Edge and ML workloads — run a model on a GPU box that lives somewhere with consumer-grade internet, and serve inference requests from it as if it were in a data center.
- Hobbyists who want HTTPS without thinking about it — point a domain at it, deploy, done.
What you get out of the box
Section titled “What you get out of the box”- A CLI (
edgible) for everything: login, install, deploy, inspect. - A declarative YAML format (
apiVersion: v3,kind: Application) for describing workloads and how the public reaches them. - An agent that runs on each serving device, talks to the Edgible control plane over WebSocket, and reconciles desired state with reality.
- A managed gateway — the bit of public infrastructure your traffic enters before reaching your tunnel. You don’t run this; Edgible does.
- A web app for visibility into your devices, applications, and logs, alongside the CLI.
Where to go next
Section titled “Where to go next”- How it works — the data plane, in five paragraphs and one diagram.
- Quickstart — login to your first public URL, in about ten minutes.
- When to use Edgible — the scenarios it fits, and the ones it doesn’t.