Identity and access
OIDC single sign-on, role bindings, zone-scoped roles and Kubernetes RBAC. Give each person and service the permissions they need.
Read the docskudurru Enterprise
Your DNS.
Your infrastructure.
Your team in control.
Run kudurru on your own infrastructure with commercial production rights and the tools to manage access, review changes and operate across nodes.
The same DNS server, with enterprise entitlements for the way your organization works. Deploy with Kubernetes and CRDs, or with Docker and Compose.
Enterprise capabilities
Built for the people
who run the network.
These capabilities are available today. Your Order Form identifies the Enterprise plan or the named modules included in your purchase.
An audit trail you can export
Review stored events, see who changed what, and export the audit trail for your own review and retention workflows.
Read the docsStatistics beyond 24 hours
Use long-term rollups to review DNS activity over weeks and months without retaining every individual query.
Read the docsPolicies for different teams
Create policies beyond the default for client groups and schedules. Let users request access from the block page and review those requests in the dashboard.
Read the docsAn edge with a floating IP
Use the kudurru supervisors for dnsdist load balancing and keepalived virtual IP failover. See backend health and VIP ownership alongside your nodes.
Read the docsDNS records from Kubernetes
Connect external-dns through the webhook provider to manage DNSRecordSet objects. Cloudflare and UniFi integrations remain on the roadmap.
Read the docsChoose your scope
Commercial Core grants business or government production rights for the core DNS server and dashboard, within the node count and scope of your agreement. It includes authoritative zones, forwarding, encrypted transports, blocking and short-term statistics.
Enterprise adds the enterprise modules and advanced entitlements identified in your Order Form. A Commercial Core purchase does not automatically include those modules.
Support scope, response times and any SLA are agreed separately in the Order Form or an incorporated support schedule. MSP, affiliate and government use must be expressly covered by the Order Form.
Eligible personal, homelab and qualifying nonprofit use remains free under the Community License, with a free key for up to 3 nodes. Compare licenses and keys
What counts as a node?
A node is one independently running kudurru DNS server instance or replica. Three running Kubernetes replicas count as three nodes, even on the same host. DNS clients are not nodes.
Production nodes count across the environments and clusters covered by your agreement. Stored images, stopped standbys and backups do not count. Separate dnsdist and keepalived processes are not additional kudurru nodes merely by existing.
Include staging, disaster recovery and failover needs when discussing your deployment. The Order Form defines those entitlements; extra running nodes are not included by default.
Keys stay local
Nodes verify license keys locally with a signature check. There is no license-server connection in the DNS path. DNS queries continue to be answered regardless of key state; a missing or expired key can limit management features.
Read the commercial agreement for the terms and the enterprise docs for deployment and licensing details.
Start with your deployment
Let’s size it together.
Tell us your organization, node count, deployment model and the features you need.