Skip to content
SPECIFICTION
Get listed

SagaOS Kea Pilot

github.com

Free plan WebLinuxAPISelf-hosted
Visit github.com
Spec score 7.8 #12 of 25 in DHCP Management Software

What it is

SagaOS Kea Pilot is a web management platform for Kea DHCP, BIND9 DNS, and Dynamic DNS, aimed at ISP and enterprise network operations. It manages DHCPv4 and DHCPv6 subnets, address pools, host reservations, leases, options, and Kea high availability. For DNS, it handles BIND9 zones and records, RFC2136 dynamic updates, and synchronization with DHCP lease events. A live health dashboard, WebSocket updates, service status tracking, performance metrics, audit logs, and analytics support operational monitoring. The platform also lists multi-tenant data isolation and granular role-based access control, with REST endpoints for DHCP and DNS operations. Configuration tools cover backup, restore, versioning, and rollback. Deployment is documented for Linux and Docker, with Ubuntu 20.04+, CentOS 8+, RHEL 8+, and Debian 11+ listed. Minimum requirements are 2 CPU cores, 4 GB RAM, and 20 GB SSD; BIND9 is optional in the minimal installation. The software is MIT licensed and free. The README documents admin/admin as the initial login and says it must be changed for production.

Spec sheet

Purpose
The project describes itself as a web management platform for Kea DHCP, BIND9 DNS, and Dynamic DNS, aimed at ISP and enterprise network operations.Read 30 Sep 2026 · github.com
Deployment
The project documents Linux installation and Docker deployment, and lists Ubuntu 20.04+, CentOS 8+, RHEL 8+, and Debian 11+ as supported operating systems.Read 30 Sep 2026 · github.com
API
It provides REST API endpoints for DHCP and DNS operations and WebSocket events for live updates.Read 30 Sep 2026 · github.com
Integrations
The documented stack includes Kea DHCP, BIND9, PostgreSQL, Docker, and Nginx; BIND9 is optional in the minimal installation.Read 30 Sep 2026 · github.com
Security
Listed security measures include CSRF protection, input validation, secure sessions, SQL injection prevention, XSS protections, rate limiting, and audit logging.Read 30 Sep 2026 · github.com
Support
The README directs users to GitHub Issues, its documentation and community discussions, and says commercial support is available for enterprise deployments and custom integrations.Read 30 Sep 2026 · github.com
License
The repository states that the software is MIT licensed and permits commercial use, modification, and distribution; it also provides the software without warranty.Read 30 Sep 2026 · github.com
Access control
It lists multi-tenant support, data isolation, and role-based access control with granular permissions.Read 30 Sep 2026 · github.com
Access controls
It lists multi-tenant data isolation and role-based access control with granular permissions and user management.Read 30 Sep 2026 · github.com
Authentication
The README says the project supports TOTP and hardware-token multi-factor authentication as an enterprise feature.Read 30 Sep 2026 · github.com
Authentication caveat
The documented initial credentials are admin/admin, and the README says to change them for production.Read 30 Sep 2026 · github.com
Configuration
Configuration tools include backup, restore, versioning, and rollback.Read 30 Sep 2026 · github.com
DHCP
It supports DHCPv4 and DHCPv6 management, including subnets, address pools, host reservations, leases, DHCP options, and Kea high availability.Read 30 Sep 2026 · github.com
DNS
It provides BIND9 zone and record management, RFC2136 dynamic updates, and DDNS synchronization with DHCP lease events.Read 30 Sep 2026 · github.com
Initial credentials
The README documents admin/admin as the default login and says it must be changed for production.Read 30 Sep 2026 · github.com
Monitoring
The project lists a live health dashboard, WebSocket updates, service status tracking, performance metrics, audit logging, and analytics.Read 30 Sep 2026 · github.com
Requirements
The listed minimum system requirements include 2 CPU cores, 4 GB RAM, and 20 GB SSD storage.Read 30 Sep 2026 · github.com
System requirements
The README specifies at least 2 CPU cores, 4 GB RAM, and 20 GB SSD, with higher recommendations for production.Read 30 Sep 2026 · github.com

Plans and prices

MIT-licensed software Free No paid tiers or usage limits stated Read 30 Sep 2026 · github.com

Every SagaOS Kea Pilot plan and price →

Strong points and limits

Strong points

  • Manages DHCPv4 and DHCPv6, including reservations.
  • Supports BIND9 zones and DHCP-linked DDNS synchronization.
  • Includes audit logs, analytics, and live status updates.
  • MIT licensed with no paid tiers stated.

Limits

  • Minimum listed requirements are 2 CPU cores and 4 GB RAM.
  • Initial login is admin/admin and must be changed for production.
  • BIND9 is optional in the minimal installation.

Who it suits

SagaOS Kea Pilot suits ISP and enterprise network operators managing DHCP and DNS services. It is intended for Linux or Docker deployments and lists multi-tenant access controls and operational monitoring.

Verdict

SagaOS Kea Pilot combines DHCP and DNS management with monitoring, access controls, and configuration rollback tools. Change the documented initial credentials before production use, and plan for the stated minimum system requirements.

Where Specifiction places it

Alternatives to SagaOS Kea PilotAll alternatives →