Hi everyone,
Long-time viewer of Tom’s channel, first-time poster here. I’m Zachary, a sysadmin from Montreal, and I’ve been building an open-source DDI platform in my spare time that I wanted to share with this community since you’re exactly the people who’d have opinions about it.
It’s DNS, DHCP, and IPAM unified under one control plane and API. Apache 2.0, no telemetry. The itch I was scratching: there’s great open-source point tooling (NetBox for IPAM, BIND/PowerDNS, Kea) but nothing pulling them into a single pane the way the commercial DDI platforms do — and Infoblox/EfficientIP pricing puts those out of reach for smaller shops, which is most of us here.
How it works in brief: FastAPI + PostgreSQL control plane is the source of truth. It deploys and manages the DNS/DHCP service containers itself (BIND9, PowerDNS, Technitium, Kea) instead of just templating configs for external servers, and it can also manage existing Windows DNS/DHCP agentlessly over WinRM. Hostname change in IPAM propagates to DNS, reservation propagates to DHCP. The agents cache last-known-good config locally and keep serving if the control plane goes down. Deploys via compose, k8s, or a bootable appliance image.
Honest status: it’s beta. Running in my lab and a few friendly networks. Full disclosure — I also run a small company (SpatiumNorth) that offers support/deployment around it, but the software itself is 100% open, no gated features.
What I’d actually love from this crowd: tear into the architecture. Especially from the MSP folks — what would break in a multi-client deployment, and what’s missing before you’d trust it on a client network? Issues and PRs welcome on the repo.
Thanks for reading, and happy to answer technical questions.