panel.ai.idA hosting panel that keeps running when a server dies.
panel.ai.id is a cluster-native hosting control panel for providers who want cPanel/WHM-class depth without a single panel server as a single point of failure.
Built for hosting providers
One panel for many nodes, with a control plane that elects a new leader on its own when a node fails. How ready each feature is today is in the status section.
Cluster-native control plane
Three controllers with leader election and shared state in etcd. If the leader dies, another controller takes over.
Standard Linux resource control
Per-account CPU, memory and I/O limits with cgroups v2 from the ordinary Linux kernel, no proprietary kernel layer.
Database workload attribution
MariaDB and PostgreSQL queries are tied to accounts and sites, so you can see where load comes from.
Provider, reseller, customer
A multi-tier model with packages, limits and permissions, tested so that one tenant cannot see another.
Full web hosting
Apache with per-site PHP-FPM, cron, domain aliases, TLS, a file manager, SFTP, and per-site backup and restore.
Migration from cPanel
Import pkgacct archives: a compatibility report first, then zones, sites, databases and files through the panel API.
API first
Everything in the console is in the API, with scoped tokens, idempotency keys and signed webhooks.
Per-node metering
Plans, usage metering and statements to pass on to a billing system such as WHMCS.
Development status
We only call a feature working once it has been shown on real servers. Status as of 14 October 2026:
| Area | Status | Notes |
|---|---|---|
| Control plane, leader failover | Running on dev cluster | Tested by killing and rebooting the leader node. |
| Web hosting (Apache, PHP-FPM, cron) | Running on dev cluster | Tested on the development hosting node. |
| Databases, site backup and restore | Partial | Backup and restore tested; off-site schedule not yet. |
| DNS, ACME, 2FA, billing, cPanel import | Built and tested | Not yet enabled on the cluster. |
| Full HA for customer sites | Planned | Site failover is DNS-based for now. |
| Email (Postfix, Dovecot, rspamd) | Planned | A separate module after version 1. |
Security comes first
Security is designed in from the start, not added later.
Per-node identity
Every node gets its own key and certificate; enrollment tokens work only once.
Tenant isolation
Cross-tenant access is refused by the authorization engine and proven by negative tests.
Audit trail
Sessions, sign-in throttling and audit logs are kept in PostgreSQL.
Staged changes
Every infrastructure change has a preflight check, a health gate and a tested rollback.