ISC Stork

ISC Stork is a browser-based operations console for teams running Kea DHCP. It is best suited to administrators who want one place to monitor service health and DHCP capacity, with selected configuration management. Its focused scope and open-source license are compelling, but the PostgreSQL setup and Kea configuration constraint narrow its fit.

Overview

Stork puts monitoring and selected management tasks for an existing Kea deployment behind a web interface. Operators can review DHCPv4 and DHCPv6 pool utilization and high-availability status, and manage reservations, subnets, and pools when the required Kea hooks are installed. That makes it useful as an operational console, not as a replacement for Kea or a general DHCP platform.

DNS visibility is more limited. Stork can display BIND configuration and zone information, but DNS support is in its early stages and the software cannot modify BIND configuration or other information. It can inform DHCP operations, but it is not a unified DNS and DHCP management console.

Key features

Health and capacity monitoring

Host and daemon reports include memory, CPU utilization, software versions, and uptime, alongside DHCP pool utilization and high-availability status. This gives operators useful service and capacity signals in one interface, though the stated scope is focused on Kea operations rather than broad infrastructure monitoring.

Selected Kea management

Reservation, subnet, and pool management is available through the GUI when the required Kea hooks are installed. Stork expects the running Kea configuration to be the configuration of record; the Kea Configuration Backend hook is incompatible with Stork management. Teams using that backend should not choose Stork for these management tasks.

Integrations and access

Stork can export traffic activity data to Prometheus for Grafana charts, and supports LDAP integration for administrator authentication and authorization. The server communicates with agents installed on application servers over gRPC channels secured with TLS. This design provides a defined path for telemetry and protected agent communication, while requiring operators to deploy and maintain both server and agent components.

Pricing

The free plan suits teams able to deploy and support the software themselves; Stork is open source under the MPL 2.0 license. Organizations that need professional assistance can pay for support, with cost depending on deployment size and service level. Free community help is available through the stork-users mailing list.

Platforms

Stork is self-hosted and runs on most Linux and Unix platforms as well as macOS. Deployments use a Stork server and agents on application servers, and the server requires PostgreSQL. This is a fit for teams prepared to operate supporting infrastructure, rather than those seeking a hosted service.

Who it's for

Stork makes the most sense for administrators already operating Kea who want a free, browser-based view of DHCP health, pool capacity, and high-availability status, plus management of selected resources. It is less suitable for teams seeking BIND configuration changes, a hosted deployment, or GUI management while using Kea Configuration Backend.

Pros and cons

• Pro: Free, MPL 2.0-licensed software provides DHCPv4 and DHCPv6 monitoring and selected Kea management without a software charge.
• Pro: Host and daemon health metrics, pool utilization, and high-availability status bring several useful operational signals together.
• Pro: Prometheus export and LDAP integration support monitoring workflows and administrator access management.
• Con: PostgreSQL plus a server-and-agent deployment adds operational requirements.
• Con: BIND support is display-only and described as early-stage, so DNS changes must be handled elsewhere.
• Con: The Kea Configuration Backend hook is incompatible with Stork management, limiting its usefulness for deployments relying on that backend.

ISC says an external audit identified seven potential vulnerabilities, all fixed and verified in Stork 2.4.0. The audit assessed Stork as meeting SLSA 0.1 and Level 1 criteria of SLSA 1.0.

Alternatives

Browse DHCP Management Software for a wider comparison.

• Subnetly is worth considering for a broader IPAM and DNS offering; its free monthly plan includes 256 IPAM addresses, 10 subnets, 2 DHCP pools, and one private and one public DNS zone.
• SagaOS Kea Pilot is another free, open-source option for teams seeking a Kea-focused tool.
• teemIP may suit teams looking for a free, open-source community edition with GitHub, wiki, and forum access.
• DacatDHCP is an alternative for Windows users who need a permanently free, IPv4-only local DHCP service.
• Danbyte is another free, open-source, self-hosted option with all features included and no seat license or license expiry.
• Jen Kea DHCP Management Console is an alternative for teams using ISC Kea with MySQL or MariaDB on Ubuntu 22.04/24.04 or Docker.
• SpatiumDDI is another free, self-hosted option.
• Open DHCP Server is an alternative for Linux self-hosting with up to 125 DHCP ranges.

Verdict

Choose ISC Stork if you already run Kea and want free, self-hosted monitoring of DHCP health and capacity, with selected GUI management when the required hooks are installed. Its strongest reason to choose it is the focused Kea oversight it offers without a software fee. Look elsewhere if you need BIND changes, use Kea Configuration Backend for management, or want to avoid operating PostgreSQL and a server-and-agent deployment.