Your edge network. On your servers.

Authoritative DNS, load balancing, automatic TLS and an encrypted Dinemic Network Mesh - managed from one API and one CLI, across any machines you control.

Open the Console Docs Source code - AGPL-3.0

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 under you. You pick the providers - and if one of them disappoints you, you move to another without rebuilding anything.

All in your hands. Use hosted Dinemic Console or host your own. Nothing in the running system depends on us. The control plane only configures your infrastructure. If it goes offline, your traffic keeps flowing.

How it works

Everything you see in the web interface is one command away. A zone, an application and a load balancer, then one deployment onto a machine: 

dinemic dns-zone create --domain example.com --email you@example.com
dinemic endpoint  create --name web  --scheme http --host 127.0.0.1 --port 80
dinemic lb        create --name edge --http 80 --https 443
dinemic peer      create --node $NODE --network $NET --config $LB

The same calls are available over the API, so your existing automation can drive Dinemic without anyone clicking through a dashboard.

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 it leaves the rotation just as quietly.

This is the part that single-host reverse proxies cannot do.

Who it's for

Dinemic is built for people running several public services across more than one machine: hosting providers and MSPs, agencies with many client sites, teams with data-residency requirements, and self-hosters who have outgrown a single box with a reverse proxy.

If you have one server and one site, a plain reverse proxy will serve you better - and we would rather tell you that now.

How this differs from the usual answers

Caddy, Traefik, nginx. Excellent at terminating TLS and routing traffic on one host. They do not run your DNS, and they have no idea that a second machine exists. Dinemic treats several machines as one system.

Tunnel tools such as Cloudflare Tunnel or Pangolin. They expose services from behind NAT through a single entry point. Dinemic does that too, through the Dinemic Network Mesh, but it also owns the layer above: authoritative DNS, so the entry point itself can fail over.

Kubernetes with ingress, cert-manager and external-dns. The closest match in what it does, and far more machinery than most teams running a handful of sites want to operate.

Status and licensing

Dinemic is in beta. It serves this website and several production domains.

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 you can run the Control Plane by yourself and nothing leaves your infrastructure at all. The same agents, the same CLI, and control plane.

The CLI and the API cover everything the web interface does, so automation is never a second-class path.

Contact

Questions, commercial licensing, or you want to run Dinemic as part of your hosting offering: contact@cloudover.io.

Bug reports and feature requests belong in the project repositories. Security issues: please email instead of opening a public issue.