SpatiumDDI
github.com
- Free plan
- Linux
- Web
- API
- Self-hosted
What SpatiumDDI is
SpatiumDDI is a self-hosted control plane for DNS, DHCP, and IP address management. It organizes IPv4 and IPv6 addresses into hierarchical spaces, blocks, and subnets, and manages configurations for BIND9, PowerDNS, or Technitium DNS and Kea DHCP. Listed cloud DNS drivers include Cloudflare, Route 53, Azure DNS, Google Cloud DNS, DigitalOcean, Hetzner, Linode, and Vultr. It can connect to existing Windows DNS and DHCP servers through RFC 2136 and WinRM without software on domain controllers. Every interface action is available through a REST API, and Terraform and Ansible are named automation clients. Access controls include group-based RBAC and support for LDAP, OIDC, SAML, RADIUS, and TACACS+. Data is stored in PostgreSQL on the user's infrastructure; the project says it collects no telemetry, usage analytics, crash reports, or account data. Docker Compose and Kubernetes with Helm are supported deployment methods. The software is free under Apache 2.0, but is marked beta and described as suitable for labs, homelabs, and pilots with non-critical client populations.
Who it suits
It suits infrastructure teams managing DNS, DHCP, and IPAM who want to run the control plane on their own infrastructure. The project identifies labs, homelabs, and pilots with non-critical client populations as appropriate settings.
Good to know, and what to watch
- Manages IPv4 and IPv6 address hierarchies.
- REST API exposes every UI action.
- Supports several DNS and identity integrations.
- Free under Apache 2.0 wherever it runs.
- Supports Docker Compose and Kubernetes with Helm.
- The project labels the software beta.
- The project limits suitability to non-critical environments.
Plans
Every plan and priceSpatiumDDI
Free plan
The verdict
SpatiumDDI combines address management with DNS and DHCP configuration, automation, and access controls in a self-hosted system. Its beta status makes it a fit for labs and pilots rather than critical client populations.
What the maker publishes
- Access controls
- The project describes group-based RBAC and support for LDAP, OIDC, SAML, RADIUS, and TACACS+. source
- Automation
- Every UI action is available through a REST API, and the project names Terraform and Ansible as automation clients. source
- Data and privacy
- The project says data is stored in PostgreSQL on the user's infrastructure and that it collects no telemetry, usage analytics, crash reports, or account data. source
- Deployment
- Supported deployment methods listed are Docker Compose and Kubernetes with Helm; the OS appliance is marked beta. source
- DNS and DHCP
- It can run BIND9, PowerDNS, or Technitium for DNS and Kea for DHCP, with the control plane managing their configuration. source
- Integrations
- The project lists agentless cloud DNS drivers for Cloudflare, Route 53, Azure DNS, Google Cloud DNS, DigitalOcean, Hetzner, Linode, and Vultr. source
- IPAM
- IPAM supports hierarchical spaces, blocks, and subnets with IPv4 and IPv6 address management. source
- License
- The product ships under Apache 2.0, with every feature free wherever it runs. source
- Maker
- SpatiumNorth is described as a Montréal-based software company that builds infrastructure software in the open. source
- Maturity
- The project labels SpatiumDDI beta software and says it is suitable for labs, homelabs, and pilots with non-critical client populations. source
- Outbound connections
- A daily anonymous GitHub release check is enabled by default and can be disabled; the project says all features work air-gapped. source
- Purpose
- SpatiumDDI is a self-hosted control plane for DNS, DHCP, and IP address management. source
- Security reporting
- The security policy asks users to report vulnerabilities through a GitHub Security Advisory and aims to acknowledge reports within 48 hours. source
- Support
- SpatiumNorth sells support, deployment, and migration services from the people who wrote the code. source
- Windows support
- SpatiumDDI can connect to existing Windows DNS and DHCP servers using RFC 2136 and WinRM without installing software on the domain controller. source
Checked against the maker's pages on 30 Sept 2026.