Most hosting panels were designed in an era when a single server ran everything. The architecture made sense then: one machine, one panel, one place to log in. Today, with multi-server infrastructure, automation pipelines, and operators managing dozens of nodes, those same designs create real friction.
adminbolt was built for the way modern hosting operations actually work. Here is how the core architecture decisions shape what you can do with it every day.
Agents: why local execution matters
At the center of adminbolt's design is the agent model. Each server that adminbolt manages runs a small, efficient agent process. When you make a configuration change, create an account, adjust a resource limit, or trigger a backup, the agent on that server handles the work locally.
This is different from architectures where everything flows through a central system that then issues commands to servers over the network. With a local agent, the execution happens where the resources are. The agent validates the result immediately, on the machine that ran the operation.
In practice, this means a few things. Changes happen quickly because they are not waiting for round-trip network calls. Errors are caught locally before they affect other systems. Adding a new server means deploying an agent and registering it - nothing else needs to change. And if the connection to the control plane is interrupted briefly, servers continue operating normally because the agent does not depend on constant connectivity.
The agent model is well-established in infrastructure tooling for exactly these reasons. adminbolt applies it to the hosting panel context where it has not historically been common.
API-first: every action available programmatically
There is a meaningful difference between a panel that has an API and a panel that is built API-first. In the first case, the UI is the primary interface and the API covers some subset of what the UI can do. In the second case, the API is the foundation - the UI, the CLI, and any external tooling all use the same underlying endpoints.
adminbolt is built the second way. The control panel interface does not have privileged access to features that the API lacks. Every action you can take in the UI, you can take via API. This is not a design goal that was added later. It is how the system was architected from the start.
For operators, this matters in concrete ways. If you connect adminbolt to WHMCS today, the integration has access to the full surface of the panel: account provisioning, DNS management, SSL issuance, service control. When you build automation next quarter - deployment pipelines, custom dashboards, provisioning scripts - that automation works with the same complete API. There are no gaps to work around, no features that require a UI interaction, no version lag between what the panel can do and what the API exposes.
If you are evaluating adminbolt for a setup that depends on automation, the API is worth testing early. Documentation is at docs.adminbolt.com.
Configuration control: for operators who tune their environment
Standard panel setups often give you defaults and limited paths to deviate from them. Changing PHP configuration for a specific domain requires a support ticket or a custom workaround. Adjusting mail policies means editing config files directly. Security rules are either all-on or all-off.
adminbolt approaches this differently. Operators can adjust service parameters directly through the panel for specific accounts, domains, or services:
PHP versions and extensions can be set per domain. PHP 7.4 through 8.5 are available, with full extension management. Customers who need specific PHP configurations get them without affecting other accounts.
Mail policies including SMTP limits, spam filtering thresholds, and deliverability settings are adjustable per domain or per account. You can tune for customers with different sending patterns without a blanket policy that creates problems for edge cases.
Resource limits at the account level: memory, CPU, and I/O constraints. Set them globally, override them for specific accounts, adjust as needs change.
Security rules including ModSecurity rulesets, Fail2Ban trigger thresholds, and firewall policies. Configure them from the panel without SSH access.
For hosting providers who differentiate on service quality, this flexibility matters. Premium customers expect environments tuned to their needs. The ability to make those adjustments through the panel rather than through manual server work is part of what makes that feasible at scale.
Built for production from the start
The architecture described here is not a roadmap. adminbolt runs real production hosting environments with the agent model, the complete API, and the configuration controls all in place. Domains, mail, DNS, SSL, databases, backups, user permissions - the standard set of hosting services is fully functional.
If you want to evaluate the architecture on your own infrastructure, the install is a single command:
curl -sSL https://get.adminbolt.com/install.sh | bash
See the technical specification for requirements, or get in touch if you have questions about how the architecture fits your specific setup.