The interface
Built for people who run networks
Every screen is a REST call underneath — if you can click it, you can automate it.
SpatiumDDI doesn't just configure your DDI servers — it runs them. BIND9, PowerDNS and Kea ship as first-class service containers the control plane owns, and they keep serving even when it doesn't.
IPAM tree, DNS zones, DHCP scopes — one UI, one REST API. Hostname changes in IPAM propagate to DNS; reservations propagate to DHCP. No more three-tab reconciliation.
Spaces, blocks and subnets with full IPv4 and IPv6 — EUI-64, random or sequential allocation. Split, merge, resize, find-free, plus a CIDR planner that previews before it commits.
BIND9 or PowerDNS per server group, auto-registering. RFC 2136 dynamic updates, DNSSEC inline signing, split-horizon views, RPZ blocklists and record-level drift detection against the live zone.
Kea with group-centric high availability — load-balanced or hot-standby, with self-healing peer drift. DHCPv6, prefix delegation, PXE/iPXE boot profiles and a 95-entry option library.
Point it at existing Windows DCs over WinRM — nothing installed on the Windows side. Cloudflare, Route 53, Azure DNS and Google Cloud DNS are first-class drivers too.
Boot one ISO, answer a few prompts, and you're on HTTPS with the full stack in minutes. Atomic A/B upgrades, health-gated rollback, and a fleet view for every node.
Group-based RBAC with LDAP, OIDC, SAML, RADIUS and TACACS+. Hand a subnet or a zone to a department without handing over root. Every mutation lands in an append-only audit log.
Every screen is a REST call underneath — if you can click it, you can automate it.
Both give you the whole stack — control plane, workers, and the DNS / DHCP service containers.
Debian 13 + embedded k3s. HTTPS in 2–5 minutes, no Docker or Kubernetes setup.
1. Download the ISO from the releases page
2. Boot it on a VM or bare metal
3. Answer the installer wizard
4. Browse to https://<your-ip>The developer-friendly path. Bring your own host.
git clone https://github.com/spatiumddi/spatiumddi
cd spatiumddi
cp .env.example .env # set POSTGRES_PASSWORD + SECRET_KEY
make build
make migrate
make up
Default login is admin / admin, and it forces a password change on first use.
Full walkthrough in Getting Started.
The recommended setup order: server groups → zones / scopes → subnets → addresses.
System topology, component relationships and the HA design.
Spaces, blocks, subnets, VLAN / VXLAN, custom fields, import and export.
Zones, records, views, server groups, blocklists, DDNS and Windows DNS.
Servers, scopes, pools, static assignments, DDNS and Windows DHCP.
Docker Compose, Kubernetes, bare metal and the OS appliance image.