Frequently asked — answered straight.
A few of the questions we hear most, with honest answers — including the things we don't do yet. If yours isn't here, just ask.
Do you offer a cloud or hosted (SaaS) version?
Not yet. DHCP is a niche corner of the network, owned deep by the people who run it — and policing DHCP traffic from a remote cloud, leaning on a pile of external resources to shape a protocol that lives inside your own network, is honestly a bit of a gimmick. Trust matters just as much: we can't secure a cloud instance as reliably as you can secure an appliance with plain network isolation.
None of that means never. We're actively building decentralized agents that run multi-node / clustered DHCP with enforcement kept local, and a hosted option may grow out of that work. We're just not there yet — and we'd rather say so than pretend otherwise.
Can I run it in Docker, Podman, or Kubernetes?
Not really. The only supported install methods are LXC, a virtual machine, or bare metal, as the manual states. The reasons are fairly concrete: a Kubernetes stack lives at Layer 3, which isn't the natural place to drive broadcast traffic; and while we won't pretend stateless containers are a bad thing, the appliance is already several services working together — and keeping all of that healthy across yet another platform is more cost than it earns us today.
This one is more legitimate than the cloud question, though. So if container deployment is genuinely what's blocking you, reach out and we'll arrange a one-time engagement to make it work in your environment.
Still wondering something?
If your question isn't here, ask us directly — we answer plainly.