We build
Infrastructure products, open source under Apache 2.0. You get the whole product; there’s no community edition with the useful parts held back.
We’re a Montréal-based software company. We build infrastructure products, release the whole thing under Apache 2.0, and charge for the part that actually costs something: support, deployment and migration, from the people who wrote the code.
A small company can be good at a few things or mediocre at many. We picked the few. Below, what’s on sale today is labelled apart from what we’re still building.
Infrastructure products, open source under Apache 2.0. You get the whole product; there’s no community edition with the useful parts held back.
Support and professional services for the organizations that run what we build. Flat yearly rates, published, banded by deployment size. No per-address meter.
Training and a Certified Operator track, built alongside the product’s hardening program, so your team can run the platform without us and prove it. Want seats in the first cohort? Tell us — early interest sets the order we build in.
DNS, DHCP and IP address management are the three services every network runs and nobody notices, until they break and everything breaks at once. For twenty years, commercial DDI has meant sealed appliances and quote-only pricing. We think it deserves a proper open-source home.
Unified DNS, DHCP and IPAM — one control plane, on your hardware.
Feature-complete and in beta. We don’t put it into business-critical production until it clears an explicit readiness bar — which is exactly what the free trial and the parallel-run evaluation are for.
We didn’t come to DDI from a business plan. We came from running this infrastructure, at scale, on the incumbents’ products, in our own day jobs.
DNS, DHCP and address management in production — including the incumbent DDI platforms, which is how we know precisely where they are excellent and where they overcharge.
AWS, Azure, Google Cloud and Cloudflare as places we actually work. Multi-cloud DNS is a first-class driver in the product because it was a first-class problem for us.
Infrastructure as code, CI/CD, config management and the discipline that comes with them: reproducible builds, reviewable changes, no snowflake servers.
Docker and Kubernetes in anger. It’s why the appliance embeds k3s, why the product also ships as a Helm chart and a Compose file, and why the engines keep serving when the control plane is down.
AI used where it earns its place: migration workflows, config import, an operator copilot. Every change it proposes is reviewed and approved by a human before it commits.
DNSSEC, RBAC against LDAP/OIDC/SAML/RADIUS/TACACS+, tamper-evident audit trails, and the evidence collection that turns an audit from weeks into days.
Each of these is checkable. That’s the point of writing them down.
Every support tier and every fixed-price service, published, with an automatic discount for education and public sector. You should be able to budget for us without booking a call.
Apache 2.0, the whole product. If this company disappeared tomorrow you’d still have a working system and all of its code. Continuity doesn’t depend on us, and that’s deliberate.
No capability appears in our marketing before it exists in the product. Where a comparison is a vendor’s own commissioned study, we cite it as one.
Imports, migrations and config changes show you the diff before anything is written. A change you did not see coming is a change you cannot review.
We’re not here to take over your architecture or compete with your technicians. A good engagement ends with your people running it without us.
A young company that pretends to be an old one gets found out in the first reference call. So: