Why host your own ingress?
Right now your domain, your certificates and your traffic almost certainly pass through one or two American providers. They set the price, they set the terms, and they decide what you are allowed to host. When they have an outage, all you can do is wait for them to fix it.
Dinemic moves that layer back onto machines you already have, regardless of the provider. Install one agent on each machine, describe what you want in the Control Plane, and Dinemic sets up the rest: authoritative DNS, load balancing, Let's Encrypt certificates, and an encrypted Dinemic Network Mesh linking all your servers. Any provider, any country, bare metal, or a Raspberry Pi under your desk.
Dinemic is built by a small independent team in Italy and Poland, with no outside investors. There is no foreign platform in the path of your traffic, no account you are forced to keep, and no terms that can change against you. You pick the providers - and if one of them disappoints you, you move to another without rebuilding anything.
Use the hosted Dinemic Console or run the control plane yourself. Your traffic never touches our infrastructure: the control plane configures your machines and then steps out of the way. If it goes offline, everything keeps serving.
How it works
All in one to expose your web apps
Authoritative DNS
Your zones are served by BIND on your own nodes. Dinemic keeps the records pointing only at load balancers that are actually alive, so a failed node drops out of rotation without you touching anything.
Load balancing - HAProxy
Health-checked routing with path priorities and weighted backends, enough for canary releases. Configs are generated and reconciled on every node, never hand-edited.
Automatic TLS
Let's Encrypt certificates issued over DNS-01, one SAN certificate per zone, distributed to every load balancer and renewed before they expire. No shared storage, no cron jobs, no certbot on each box.
Dinemic Network Mesh
Your application servers join the Dinemic Network Mesh - encrypted WireGuard® tunnels between all your machines - and never need an open port. They can sit behind NAT, in your home lab, or on hardware you keep in the office.
Scale by adding machines, not by rewriting config
Rent another VPS - a different provider, a different country - install the agent and deploy a load balancer peer on it. DNS records, mesh routing and certificate distribution update themselves within minutes. Remove it and Dinemic will stop serving traffic through it immediately (with respect to DNS TTL).
This is the part that single-host reverse proxies cannot do.
Licensing
The agent, the control plane and the command line tool are open source under AGPL-3.0-or-later. Running Dinemic on your own infrastructure does not require a commercial licence. A commercial licence is available if AGPL does not fit your product - get in touch below.
There are two ways to run the control plane. Use the hosted Dinemic Console and you are configuring your own servers from day one, without installing anything else. Or run the control plane at your own and everything is under your full control. The same agents, the same CLI, and you can move between these two.
The CLI and the API cover everything the web interface does, so automation is never a second-class path.
Pricing plans
console.dinemic.com
Contact
Questions, commercial licensing, or you want to run Dinemic as part of your hosting offering: contact@dinemic.com.
Bug reports and feature requests belong in the project repositories. Security issues: please email instead of opening a public issue.