Geo-routing, health checks, and weighted load balancing on the hosting side. Domain and IP-based filtering on the security side. One API, one platform, built to survive losing a region.
In testing now, launch approaching — we're planning limited free access for our first cohort of users.
Beyond records and zones — traffic control that usually needs a separate product.
The category PiHole and NextDNS popularized — built as part of the same platform, not bolted on.
Hosting and filtering share the same geo-distributed nodes, control plane, and data plane.
Three bets we're building toward.
Threats keep getting caught further downstream than they should. We think filtering and anomaly detection belong at the DNS layer, before a request ever reaches an application.
Address space and device counts are both growing fast. Dinio is built to stay comfortable with both, not patched to tolerate them.
Compute keeps moving closer to users and further from any single data center. We want Dinio to be infrastructure that fits naturally into that shift — however it gets abstracted, from IaaS to FaaS.
Join the Dinio DNS private preview, or send a short brief about what you're building. Either gets a thoughtful reply within two business days.