Home

EZ-Kea

A zero-config web interface for ISC Kea DHCP.

If you're just getting started, the README covers installing and running it in about a minute. These pages cover everything past that point.

Guides

• Installation — systemd, reverse proxies, and Docker-based Kea
• Deployment Scenarios — how EZ-Kea decides between LIVE and DEMO mode
• Configuration Reference — every environment variable and UI override
• Security Hardening — what to do before exposing it
• High Availability — configuring Kea's HA hook
• Testbed — containerized Kea for end-to-end testing
• Licensing — free tier, grace period, and license keys

Quick answers

Where does EZ-Kea store its own settings? Kea daemon paths and commands go in ez-kea-settings.json inside your data directory. Users, 2FA secrets, the license key, and SMTP settings go in a SQLite database (ez-kea.db) alongside it.

Does EZ-Kea need to run on the same host as Kea? Yes, for auto-discovery and reloads. It reads /proc to find running daemons and edits config files on local disk. A Docker-based Kea on the same host works via docker exec — see Installation.

Will it break my running DHCP server? Edits are written to the config file; nothing takes effect until you apply them. You can back up, restore, and syntax-check from the UI before applying.

What happens at 100 leases? See Licensing. Short version: a banner, then a 7-day grace period, then configuration edits are blocked. Kea itself keeps serving DHCP throughout.