1:"$Sreact.fragment" 2:I[68166,["/_next/static/chunks/871899d3339c746e.js","/_next/static/chunks/105be88731c1dd83.js"],"default"] 3:I[69776,["/_next/static/chunks/871899d3339c746e.js","/_next/static/chunks/105be88731c1dd83.js"],"default"] 13:I[22016,["/_next/static/chunks/871899d3339c746e.js","/_next/static/chunks/105be88731c1dd83.js"],""] 14:I[31664,["/_next/static/chunks/871899d3339c746e.js","/_next/static/chunks/105be88731c1dd83.js"],"default"] 1f:I[97367,["/_next/static/chunks/ff1a16fafef87110.js","/_next/static/chunks/58284bda24c88a12.js"],"OutletBoundary"] 20:"$Sreact.suspense" 23:I[55923,["/_next/static/chunks/871899d3339c746e.js","/_next/static/chunks/105be88731c1dd83.js"],"default"] 4:T14a1, Today is a day we have been working toward for a long time. **adminbolt is officially live in production.** For the hosting providers, agencies, and developers who have been following along: thank you. You asked good questions, pushed back on the right things, and shaped what we built. This launch belongs to you as much as it does to us. For everyone discovering adminbolt for the first time: welcome. --- ## What adminbolt is adminbolt is a hosting control panel. But describing it that way is a bit like describing a smartphone as a telephone. Technically accurate, completely misses the point. What we actually built is a platform that independent hosting companies can compete on. Not just manage servers with, but build a real product on top of. Something with a flat pricing model that does not penalize growth, an API-first architecture that makes automation genuinely possible from day one, and a foundation we are actively evolving. We started building adminbolt because we believed the hosting control panel market was stuck. Not broken. The incumbents work, and they have powered the internet for two decades. But they were built for a different era. The pricing models, the architectures, the interfaces were optimized for a world that no longer exists. > Independent hosting companies deserve a platform that helps them win on product, not one that makes winning harder every time they grow. --- ## Where we are going adminbolt ships today as a complete, production-ready hosting control panel. But the version we are most excited about is the one we are building toward. We think the next major shift in the hosting industry will be AI, not as a feature, but as a fundamental change in what a hosting platform can do: - Hosting that detects and resolves problems before customers notice them - Infrastructure that recommends the right resources at the right time - Environments provisioned from a single instruction - A platform that gets smarter with every server in the fleet The large hosting companies are already building this internally. We are building it as a platform, so every hosting company using adminbolt can compete with that capability rather than watch it pull further away. > We will move faster on AI than any legacy platform can. Clean architecture, no technical debt, a team with nothing to protect but the product. As AI capabilities ship, they go to every plan, every customer, automatically. No tiers, no add-ons, no gating. --- ## What is available today adminbolt ships on AlmaLinux 9 and installs in under five minutes. Everything below is included in every plan: - **Multi-server dashboard** - Your entire fleet from a single login. Real-time load, RAM, and disk monitoring across all machines. - **Web server management** - Per-site PHP runtime switching, resource isolation, WordPress-ready out of the box. - **Email infrastructure** - Full mail server, spam filtering, webmail, automatic DKIM/SPF setup. No extra license. - **Security stack** - WAF, malware scanning, brute-force protection, automatic SSL via Let's Encrypt. - **REST API** - Every panel action available via API. WHMCS integration live. Full automation from day one. - **Ecosystem compatibility** - LiteSpeed, CloudLinux, Imunify, Softaculous, JetBackup, Let's Encrypt. No rip-and-replace required. adminbolt uses **up to 60% less RAM** than traditional panels. More resources for your customers' sites, less overhead for your infrastructure. --- ## Pricing We built adminbolt on a flat per-server pricing model. No per-account fees. No feature tiers. Your bill does not grow because your customer base grows. | Plan | Price | For | |---|---|---| | VPS / Cloud | $20 / mo | Virtual machines and cloud instances | | Bare Metal | $45 / mo | Physical dedicated servers | | Standalone | $7 / mo | Single server, up to 2 accounts | Every plan includes the full feature set. **30-day free trial. No credit card required.** --- ## Partner program We are running a partner program for hosting companies who want to grow with adminbolt. Partners get wholesale pricing with volume discounts from 5 servers, direct access to our engineering team, and a genuine voice in what we build next. Hosting companies that join early are not just customers. They are shaping the roadmap. If you are running a hosting business and see something that could change the way you operate, we want to hear about it before we write the spec. Reach out at [adminbolt.com/contact](/contact) to apply. --- ## Thank you for being here on day one Launching a product is a strange feeling. You spend months believing in something privately, and then you make it public, and suddenly other people's reality gets to weigh in. We are ready for that. We know adminbolt is not finished. Every good product never is. What we are confident about is the direction: a hosting platform that gets faster, smarter, and more capable every month, and does it for the hosting providers who deserve a real partner, not just a vendor. If you try adminbolt and it is not what you needed, tell us. That feedback is how this gets better. If it is what you needed, tell someone else. --- [See features](/features) · [View pricing](/pricing) · [Install now](/docs/migration-guide) 5:Ta77, We are pleased to share that Plus Hosting Grupa has initiated a structured pilot program with adminbolt, evaluating our platform as a next-generation control panel across select environments in their European hosting portfolio. ## About Plus Hosting Grupa Plus Hosting Grupa is one of Croatia's leading cloud and hosting companies. Founded in 2001 and headquartered in Pula, the company is part of DHH, a publicly listed European cloud infrastructure group. They serve a broad customer base ranging from SMEs and digital businesses to enterprise clients across the region. This is not a small player exploring options. This is an established hosting group with over two decades of operational experience making a deliberate, structured decision to evaluate whether adminbolt fits their infrastructure direction. ## What the Pilot Covers The evaluation is production-grade, not a sandbox exercise. The scope includes: - Deployment across selected live environments within their portfolio - Full panel-level migration workflow validation - Performance benchmarking under real customer workloads - Security validation and architectural stress testing - Compatibility testing with their existing provisioning systems - Direct feedback loops between our engineering teams We are running this together. Their team is embedded in the process, and we are iterating based on what we learn from their production environment. ## Why This Is Happening The context behind this evaluation reflects a shift we are seeing across the industry. For hosting groups operating at scale, control panel licensing has become a strategic financial and risk-management question, not just a tooling decision. The key drivers Plus Hosting Grupa identified align closely with what we built adminbolt to address: long-term vendor dependency risk, unpredictable per-account licensing costs as portfolios grow, and the need for operational flexibility without being locked into a single vendor's roadmap. > "Hosting providers need strategic optionality. Control panels should enhance margin predictability and operational control." > > **Lukasz Gawior, founder of adminbolt** ## What This Means for Us Having a group like Plus Hosting Grupa run a production evaluation is a meaningful signal. It validates the direction we have taken with adminbolt: flat per-server pricing, an API-first architecture, and a migration toolchain built for real-world complexity. We are focused on making this pilot successful. The feedback we get from their environments will directly shape the product. That is exactly the kind of collaboration we want to be in. We will share more as the evaluation progresses. 6:T213b, Hosting providers evaluating their panel setup in 2026 have more options than at any point in the industry's history. Flat per-server pricing, API-first architecture, and multi-node support are now available in production-ready panels from multiple vendors. Choosing between them is not just a technical decision - it is a business decision that affects your costs, your automation capabilities, and your operational model for the next several years. This guide covers the main options: how they price, how they are built, and which situations each fits best. ## What to look for when comparing panels Three things tend to matter most for professional operators. **Pricing model.** Some panels charge per account, which means your licensing cost grows as you grow your customer base. Others charge per server, which means one fixed cost regardless of how many accounts that server hosts. The difference is small at low account counts and significant at scale. **Architecture.** Panels designed for single-server setups require a separate login for each box you manage. Multi-node panels let you manage multiple servers from one dashboard, one API, and one set of credentials. If you manage more than two servers, this distinction has a real impact on day-to-day operations. **Resource footprint.** A panel that uses more RAM at idle leaves less headroom for customer workloads on the same hardware. This affects account density and, ultimately, your margin per server. ## adminbolt adminbolt is a modern hosting control panel designed for professional hosting providers. It ships with everything you need for production hosting: domains, DNS, SSL via Let's Encrypt, email (Postfix + Dovecot), databases (MariaDB), backups, user permissions, and a full REST API. The architecture is agent-based and multi-node from the ground up. **Pricing:** VPS/Cloud at $20 per server per month (unlimited accounts). Bare Metal at $45 per server. Standalone licenses from $7 per month for partners and resellers. [See full pricing](/pricing). What sets adminbolt apart for professional operators: **Flat per-server pricing.** One monthly cost per server, regardless of whether that server hosts 5 accounts or 500. Your panel bill does not grow when your customer base does. **Multi-node architecture.** Add web nodes, email nodes, and database nodes from one panel. Separate your email infrastructure from your web infrastructure for better deliverability - without manual configuration. **Low resource footprint.** Around 380 MB RAM at idle. That leaves more capacity for customer sites on the same hardware compared to heavier panels. **API-first from day one.** Every panel action is available via API. Connect to WHMCS, Blesta, or any custom billing system without waiting for an official plugin. **Modern stack.** AlmaLinux 9, one-command install, no license key activation process. Best for: Hosting providers managing multiple servers who need predictable costs, automation support, and a panel built for modern infrastructure. [See how adminbolt compares](/pricing-comparison). ## DirectAdmin DirectAdmin is a long-established, lightweight panel with per-server pricing. It has been a preferred choice for operators who want a stable, familiar interface without the overhead of heavier alternatives. **Pricing:** Personal at $29 per month, Lite at $39 per month (up to 100 accounts), Standard at $49 per month. Per-server license. DirectAdmin runs lean: around 300 to 400 MB at idle. The interface is functional and well-understood by operators who have used it for years. The main limitation is that it is designed for single-server operations. Each server is managed separately, there is no built-in multi-node dashboard, and API coverage is more limited than panels built around automation first. Best for: Small hosting operations or single-server setups where cost matters and multi-server management is not a requirement. ## CloudPanel CloudPanel is a free, open-source panel aimed at PHP and WordPress hosting. It has a clean interface and a straightforward setup process. **Pricing:** Free. CloudPanel handles the basics well and gets new users running quickly. The tradeoffs are scope and support model: it is a single-server panel without built-in email node separation, multi-server management, or the depth of features that production shared hosting typically requires. Because it is open-source, security patches and updates are self-managed. Best for: Developers and small projects that need simple server management without full hosting panel requirements. ## CyberPanel CyberPanel is an open-source panel built around LiteSpeed. If LiteSpeed is already central to your stack, it is worth considering. **Pricing:** Free (open-source), or a paid bundle with LiteSpeed Enterprise. CyberPanel has solid LiteSpeed integration and a zero-cost entry point. The constraints are the LiteSpeed dependency and single-server scope. The ecosystem of third-party integrations is smaller than more established panels, and multi-server management is not available natively. Best for: Hosting operations that have standardized on LiteSpeed and want a free panel that fits that stack. ## HestiaCP HestiaCP is a free, actively maintained open-source panel covering web, mail, DNS, and databases in one package. **Pricing:** Free. HestiaCP is clean and reliable for what it does. The interface is straightforward and the project has an active community. The same single-server limitation applies, and there is no native multi-node or API-first automation capability. Best for: Hobby projects and small setups where cost is the main constraint. ## Plesk Plesk is a mature commercial panel with a broad feature set. It has been widely adopted in enterprise and agency contexts, and it includes Windows hosting support - something most Linux-focused panels do not offer. **Pricing:** Tier-based, billed monthly (annual plans removed January 2026). Web Admin (10 domains) €12.04/mo, Web Pro (30 domains) €18.29/mo, Web Host (unlimited domains) €31.38/mo. Plesk covers a lot of ground and has a well-established ecosystem of extensions and integrations. The tradeoffs are resource footprint (typically 500 to 700 MB or more at idle) and a pricing model that increases with account count or tier upgrades. For shops already deeply integrated with Plesk or running Windows workloads, switching has a real cost. Best for: Operations that need Plesk-specific integrations, Windows server support, or are already embedded in the Plesk ecosystem. ## Comparison at a glance | Panel | Pricing model | Multi-server | RAM at idle | API-first | | ----------- | --------------- | ------------ | ----------- | --------- | | adminbolt | Flat per server | Yes | ~380 MB | Yes | | DirectAdmin | Per server | No | ~300-400 MB | Limited | | CloudPanel | Free | No | Varies | No | | CyberPanel | Free / paid | No | Varies | Limited | | HestiaCP | Free | No | Moderate | No | | Plesk | Tier / account | Optional | ~500-700 MB | Yes | | cPanel/WHM | Per account | No | ~920 MB | Yes | Pricing and RAM figures are indicative. Check each vendor for current numbers. ## Which panel fits your situation **Professional hosting with multiple servers and predictable costs:** adminbolt. Flat per-server pricing, multi-node support, and a [feature set](/features) built for operators who need automation and scale without per-account licensing overhead. **Single server, tight budget, no multi-server need:** DirectAdmin for a commercial option, or CloudPanel, HestiaCP, or CyberPanel depending on your stack and willingness to manage open-source software. **Enterprise features, Plesk ecosystem, or Windows hosting:** Plesk, if the cost and resource footprint fit your model. **Hobby or side projects:** Free panels work well for low-scale, single-server setups where zero licensing cost matters most. If you want to evaluate adminbolt on your own infrastructure, the 30-day free trial gives you full access with no account limits and one fixed price per server. ```bash curl -sSL https://get.adminbolt.com/install.sh | bash ``` [View pricing](/pricing) and [see the full feature list](/features). 7:T146f, Hosting panel licensing comes in two fundamentally different models, and the difference between them becomes more significant the more your business grows. One model ties your licensing cost to how many accounts you run. The other charges a fixed fee per server regardless of account count. Understanding which model you are on - and what it costs at different scales - is worth ten minutes of calculation before you commit to a long-term infrastructure decision. ## Per-account pricing: how it works With per-account licensing, your monthly cost is determined by how many hosting accounts exist on a server. Most panels using this model structure their pricing in tiers: a base price for small account counts, progressively higher tiers for more accounts, and per-account overage charges once you exceed the top tier. This model is straightforward to understand at low account counts. At 10 accounts, the cost feels reasonable. The challenge appears as you grow: every account you add either moves you into a higher tier or adds a per-account charge on top of the base price. **cPanel/WHM pricing tiers (2026):** | Tier | Accounts | Price/month | | ------- | ---------- | --------------------------------- | | Solo | 1 | $29.99 | | Admin | Up to 5 | $35.99 | | Pro | Up to 30 | $53.99 | | Premier | Up to 100 | $69.99 | | Premier | 101+ | $69.99 + $0.49 per extra account | At 100 accounts you pay $69.99. At 200 accounts the license costs approximately $118.99. At 500 accounts you are paying over $270 per server per month in licensing alone. Check [cPanel's pricing page](https://www.cpanel.net/pricing) for the latest figures, as these can change. The structural issue is that per-account pricing makes growth more expensive. Adding customers is supposed to improve your economics. With per-account licensing, every new account incrementally increases one of your fixed overhead costs. ## Flat per-server pricing: how it works With flat per-server pricing, you pay one monthly fee for the server regardless of how many accounts it hosts. Ten accounts or a thousand accounts: the license cost is the same. This model aligns better with how hosting economics actually work. A server has fixed hardware costs. If you can run more accounts on it without increasing licensing overhead, your margin per account improves as the server fills up. **adminbolt pricing:** - VPS/Cloud: $20 per server per month, unlimited accounts. - Bare Metal: $45 per server per month. - Standalone: from $7 per month through the partner and reseller program. The same server, the same price, regardless of utilization. ## What the numbers look like at scale Comparison for a single server (adminbolt VPS at $20 per month vs cPanel list prices): | Accounts | Per-account (approx) | adminbolt | Annual difference | | -------- | -------------------- | --------- | ----------------- | | 30 | $53.99/mo (Pro) | $20/mo | ~$408/year | | 100 | $69.99/mo (Premier) | $20/mo | ~$600/year | | 200 | ~$119/mo | $20/mo | ~$1,188/year | | 500 | ~$270/mo | $20/mo | ~$3,000/year | These are estimates based on published list prices. The precise numbers will depend on your specific configuration and whether you qualify for discounts. The point is the direction of the relationship: at higher account counts, the pricing model matters more than the absolute base price. ## Which model fits your business Neither model is universally better. The right choice depends on where you are and where you are going. **Per-account pricing may make sense when** you run a small, stable account count where the per-tier cost is acceptable and you are deeply integrated with tooling that assumes a per-account panel. If growth is slow and the economics work at your current scale, switching may not be worth the disruption. **Flat per-server pricing makes sense when** you are growing your account count and want your panel costs to stay predictable. It is also the right choice if you manage multiple servers and want consistent, comparable costs across them, or if your business model depends on wide margins from high-density shared hosting. ## How to calculate your own number The calculation is simple. Count your accounts per server. Find the tier that covers your count on your current panel and note the monthly cost. Compare that to a flat per-server alternative. Multiply the monthly difference by 12. For most operators running 50 or more accounts per server, the annual difference justifies a closer look at flat pricing options. For operators running 200 or more accounts per server, the difference is often significant enough to make switching a straightforward business case. **Try adminbolt on your infrastructure for 30 days, no credit card required:** ```bash curl -sSL https://get.adminbolt.com/install.sh | bash ``` [See plans and pricing](/pricing) and [compare panels side by side](/pricing-comparison). 8:T1339, Before a single customer logs in or a single website loads, your hosting panel is already consuming server resources. This is not a flaw - the panel needs to run constantly to manage services, handle API requests, and keep everything operational. But the size of that footprint is not fixed. Different panels have very different idle resource usage, and that difference has a direct effect on how efficiently you can use your hardware. On a 4 GB VPS, the difference between a panel that uses 380 MB at idle and one that uses 920 MB is more than half a gigabyte of RAM that either goes to your customers or disappears into software overhead before anyone sends a request. Multiply that across a fleet of ten or twenty servers and the impact on your capacity planning becomes real. ## Why panel RAM usage is a business decision, not just a technical detail More available RAM means more room for everything that actually serves your customers. PHP-FPM workers run in parallel to handle concurrent requests. MariaDB uses cache to serve frequent queries from memory instead of disk. Each account on the server has a buffer to absorb traffic spikes without hitting resource limits. A lighter panel does not automatically mean better performance. There are many factors involved. But it does give you more room to work with on the same hardware. You can run more accounts per server before needing to upgrade or add a node. You can use smaller instances for the same workload. Either way, the margin impact is real. If you are running a fleet of servers and wondering where to find efficiency gains before investing in more hardware, checking your panel's idle footprint is worth doing. ## Typical RAM usage at idle across common panels These numbers are based on clean installs with services running and no customer accounts. Your actual numbers will vary depending on add-ons, configuration, and workload, but this gives you a useful baseline for comparison. | Panel | Typical RAM at idle | Notes | | ----------- | ------------------- | ----------------------------- | | adminbolt | ~380 MB | AlmaLinux 9, default stack | | DirectAdmin | ~300-400 MB | Lightweight, single-server | | Plesk | ~500-700 MB | Depends on enabled components | | cPanel/WHM | ~920 MB | Includes Java-based services | adminbolt and DirectAdmin are at the lighter end of the range. Plesk sits in the middle. These are idle baselines. During active work like backups, migrations, or bulk account operations, usage climbs on all panels. ## What the difference looks like on a 4 GB VPS Working with rough numbers and reserving about 500 MB for the OS and system buffers: With a panel consuming 920 MB at idle, you have approximately 2.5 GB left for MySQL, PHP workers, and customer sites combined. With a panel at 380 MB, you have roughly 3.1 GB for the same. That extra 600 MB might translate to three to five more PHP workers, a larger MySQL buffer pool, or simply better headroom during traffic spikes. On one server it is a modest gain. On ten servers it is a meaningful capacity difference that you do not have to pay for. ## How to measure your current panel's footprint Before drawing any conclusions, measure your actual baseline. Panel vendors quote idle figures under ideal conditions; your real-world number reflects your actual configuration. **Check overall RAM usage:** ```bash free -m ``` Look at the "used" value after the panel has been running for at least ten to fifteen minutes with no active tasks. **See which processes are using the most memory:** ```bash ps aux --sort=-%mem | head -20 ``` **Get a live view:** ```bash htop ``` Sort by the MEM% column. Panel daemons, web server processes, and database services will typically appear near the top. For the cleanest baseline: reboot the server, start the panel, create no accounts, wait fifteen minutes, then run `free -m`. That number is as close to a true idle footprint as you will get in practice. ## What adminbolt's footprint means in practice At roughly 380 MB idle, adminbolt runs the full stack needed for production hosting: Apache (MyApache) for web, PHP-FPM, Postfix and Dovecot for email, MariaDB for databases, DNS management, and the panel's own API and control layer. Everything is included in that number. There are no separate services to disable to get it lower. If you are planning capacity for a new deployment or trying to get more out of existing hardware, the panel's idle footprint is one of the more direct levers you have. It is worth measuring before you decide what to run. [See adminbolt features](/features) and [pricing](/pricing). **Try adminbolt for 30 days, no credit card required:** ```bash curl -sSL https://get.adminbolt.com/install.sh | bash ``` 9:T1170, You start with one server. You know it well. You know which accounts are on it, roughly how much RAM is free, when the last backup ran. Managing it feels manageable. Then you add a second server. And a third. And somewhere around the fourth or fifth, the operational picture changes. You have multiple dashboards to check, multiple login sessions open at once, and a growing mental map of which customer lives on which box. Something that was straightforward at one server becomes genuinely awkward at five. This is one of the most common friction points for growing hosting businesses, and it is one that has a clean architectural solution. ## What managing multiple separate servers actually looks like When each server has its own control panel, every operational task multiplies. Creating a new account means logging into the right server, checking which one has room, creating the account there, and updating your spreadsheet or CRM so you know where it ended up. Moving an account between servers involves manual backup, restore, DNS record updates, and verification that everything survived the move. Checking resource usage across your fleet means opening multiple browser tabs and piecing together a mental picture. Running updates or security patches means repeating the same steps on each machine separately. Automation is possible but requires custom scripts that have to be maintained for each server's configuration. None of this is impossible. Operators have been working this way for years. But it does not scale cleanly, and the overhead grows with every server you add. ## What changes with multi-node architecture Multi-node means there is one control plane and multiple servers connected to it as nodes. Each node can serve a different role: web server, email server, database server, or a combination. From the operator's perspective, there is one login, one dashboard, and one API. In practice, the day-to-day workflow shifts noticeably. You see all servers and all accounts from a single view. Creating an account means choosing a node from a list (or letting the panel balance automatically based on load) and filling out one form. Moving an account between nodes can be done from the same interface. Backups, SSL renewals, and updates are managed centrally. Service separation also becomes straightforward. If you want email on a different server and IP than web, you set up an email node. The panel handles the configuration between them. No manual config file editing, no manual credential syncing. ## How adminbolt implements multi-node adminbolt is designed around this model from the start. Adding a new server means installing the adminbolt agent on it and registering it as a node from your panel. The agent runs locally on the server, handles operations there, and reports back to the control plane. This keeps latency low and means each server can operate independently even if connectivity to the control plane is interrupted briefly. A common setup for a growing hosting business might look like this: two or three web nodes handling customer sites, a dedicated email node on a separate IP for better deliverability, and a database node for high-traffic accounts that benefit from isolated database resources. Everything is managed from one panel with one API connection to WHMCS or your billing system of choice. The agent-based model also scales cleanly. Adding another server does not require restructuring your setup. Install the agent, register the node, and it appears in your panel alongside the existing ones. ## When it makes sense to switch If you are running one server and have no immediate plans to add more, multi-node is not a pressing concern. But the moment you are regularly working across more than two servers, the operational overhead of separate dashboards starts to cost real time. The common trigger is realizing you are doing the same task in multiple browser tabs on the same day. That repetition is a signal that a unified management layer would pay off quickly. If you want to see what this looks like in practice, adminbolt has a 30-day free trial. Install it on your first server, add a second node, and see how the workflow changes when both servers appear in one place. ```bash curl -sSL https://get.adminbolt.com/install.sh | bash ``` [Features overview](/features) and [pricing](/pricing) (flat per server, no per-account fees). a:T1795, Most hosting setups start simple: one server handles everything. Web, email, DNS, databases - all running together on a single IP. It works, and for a small operation it is often perfectly fine. The trouble starts when something goes wrong with one of those services and the consequences spill over into the others. Email deliverability is where this problem shows up most visibly. When web and mail share an IP, the reputation of that address is affected by everything on the server. One compromised site, one spam complaint, one automated script that fires off too many messages - any of these can damage the IP's standing with mail providers, and that affects every domain on the box. Separating email and web is the standard fix. The question is how to do it without turning it into a significant infrastructure project. ## What actually goes wrong when they share an IP **Shared reputation with no isolation.** Blocklists operate at the IP level. If a site on your server gets hacked and starts sending spam, or if a shared hosting customer's script triggers a spam filter, the IP that email flows through gets flagged. Mail from every domain on that server - including customers who have done nothing wrong - suddenly has reduced inbox placement. You are responsible for a problem you did not cause. **Resource competition during critical moments.** Mail and web both consume CPU, RAM, and disk I/O. A traffic spike on a popular site can slow down the mail queue. A runaway cron job can delay delivery. Mail servers work best when they have stable, predictable resources. Mixed infrastructure makes that harder to guarantee. **Harder troubleshooting.** When deliverability issues arise on a mixed server, it takes longer to isolate the cause. Is it the sending domain? The IP? Something running on the web side? Separate servers mean separate logs, separate metrics, and faster diagnosis. ## The traditional approach: manual dedicated mail server The classic solution is to run a separate physical or virtual server dedicated to mail. You configure your MX records to point to it, run your mail stack there, and keep web traffic on your existing servers. This gives you IP isolation and eliminates cross-service interference. The downside is the operational overhead. Setting up and maintaining Postfix, Dovecot, DKIM, SPF, DMARC, and spam filtering on a separate server requires ongoing attention. You also need to keep user accounts synchronized between web and mail servers, which adds complexity to account creation, changes, and deletions. For many providers, this work is manageable - but it is real, ongoing work. ## The modern approach: email nodes in the panel Panels that support multi-node infrastructure let you add a dedicated email node without stepping outside the panel's management interface. The panel handles installation and configuration of the mail stack. Your MX records point to the email node's IP. Web stays on separate servers. Accounts are managed centrally through the panel - one place for everything. In adminbolt, the setup works like this: you add a server as an email node from the panel dashboard. adminbolt installs and configures Postfix, Dovecot, DKIM, SPF, and spam filtering automatically. You set your MX records from the same DNS interface you use for everything else. From that point, outbound mail flows through a dedicated IP with its own reputation, completely separate from your web traffic. Web nodes and email nodes share the same account management. Customers do not notice the separation; they just get more reliable email delivery. ## What changes after you separate them The most immediate change is isolation. A compromised site on a web node no longer threatens the IP your customers send mail through. The email node's reputation is built entirely on mail traffic, which is what mail providers expect to see. Troubleshooting becomes cleaner too. If a customer reports a deliverability problem, you are looking at the mail node specifically, not trying to sort through a mixed server's logs to find the cause. Over time, a dedicated mail IP that handles only mail tends to build a cleaner sending history with major providers. There are no guarantees in email deliverability, but removing the structural risk of IP sharing is one of the more impactful steps you can take. ## When it is worth doing For small setups with a handful of trusted accounts, the overhead of separation may not be justified yet. But there are a few clear indicators that it is time: **Growing account count.** More accounts means more surface area for incidents. As your customer base grows, the probability that something on the server affects the shared IP increases. **Transactional or business email.** Order confirmations, invoices, password resets - these messages need to reach the inbox reliably. A compromised web IP can disrupt delivery for everyone relying on that server for important mail. **Reseller or managed hosting.** If your customers are running their own businesses from email accounts you manage, your deliverability reputation is part of your service quality. Separation is both an operational improvement and a selling point. If none of those apply today, you can defer. But it is worth building the separation into your infrastructure before a deliverability incident forces it. ## Summary Email and web on the same IP share a reputation that neither fully controls. Separating them removes that dependency. The traditional approach works but requires manual setup and ongoing maintenance. A panel with multi-node support can handle the separation through the same interface you already use to manage everything else. [adminbolt features](/features) include multi-node support and dedicated email nodes. [Pricing](/pricing) is flat per server, no per-account fees. **Try adminbolt for 30 days, no credit card required:** ```bash curl -sSL https://get.adminbolt.com/install.sh | bash ``` b:Te53, Running a hosting business is not just about keeping servers online. It is about keeping control: of your costs, your workflows, and the tools you depend on every day. This blog exists because we think the hosting industry deserves better software, better documentation, and more honest conversations about what actually works. We are the team building adminbolt. We write here about what we learn, what we ship, and what we see operators dealing with in the field. ## Technical guides written for people who run real servers Most technical content for hosting operators falls into one of two categories: marketing copy dressed up as documentation, or Stack Overflow threads that were last updated in 2018. We are trying to do something different. Every guide we publish starts with a real operational problem. How do you separate email and web on different IPs without turning it into a weekend project? How do you measure what your control panel actually costs at the hardware level? How do you grow from one server to five without losing your mind managing five separate dashboards? The answers we write are the ones we have worked through ourselves. - [How to manage multiple hosting servers from one panel](/blog/manage-multiple-hosting-servers-one-panel) - [Why separating email and web hosting improves deliverability](/blog/separating-email-web-hosting-why-how) - [How much RAM does your hosting panel use? (And why it matters)](/blog/hosting-panel-resource-usage-compared) ## Honest pricing comparisons Panel licensing is one of the most significant ongoing costs in the hosting business, and it is also one of the least talked about. We cover how different pricing models work in practice: what they cost at scale, how the math changes as you grow, and what switching to flat per-server pricing looks like in the real world. We are not neutral on this topic. We think per-account licensing is bad for hosting providers and we will explain exactly why with numbers. - [Hosting panel pricing in 2026: per-account vs flat pricing explained](/blog/cpanel-pricing-2026-costs-save) - [Best cPanel alternatives for hosting providers in 2026](/blog/best-cpanel-alternatives-2026) - [Full pricing comparison: adminbolt vs other panels](/pricing-comparison) ## Product updates and roadmap When we ship a feature, we document it here. Not just "what changed" but why we built it, what problem it solves, and what it means for your setup. You can also follow the full roadmap on our [roadmap page](/roadmap). ## Industry context The hosting panel market has been unusually static for a long time. Multi-server management, API-first architecture, and predictable pricing are not new ideas, but they are still not standard. We write about where the industry is heading and what modern operators are building when they have the right tools. ## Who writes this adminbolt is built by people who have operated hosting businesses. We understand what it means when a panel bill goes up unexpectedly, when a migration turns into three days of manual work, or when your automation depends on a UI that changed without warning. The content on this blog comes from that background, not from a content team optimizing for page views. ## Get in touch If there is a topic you would like us to cover, a question about running adminbolt, or something you are trying to solve in your infrastructure, [reach out](/contact). We read every message and many of our articles come directly from conversations with operators. You can also subscribe to updates via the newsletter in the footer. No noise, just posts worth reading. c:T153d, When you offer managed VPS hosting, your control panel is not just a tool your customers log into. It is the layer that sits between your infrastructure and everything you do operationally: creating accounts, provisioning services, running backups, handling migrations, connecting billing systems. If that layer is slow, incomplete, or expensive to scale, it becomes the limiting factor in your business. Picking the right panel for managed VPS is a different decision than picking one for basic shared hosting. Here is what actually matters. ## Resource efficiency: what the panel costs before work begins Every panel has an idle footprint. RAM that gets consumed before a single customer opens a browser. On a small server this might feel irrelevant. Across a fleet of VPS instances, it shapes your economics directly. adminbolt runs at around 380 MB RAM at idle. That includes the full stack: web server management, DNS, email, databases, and the API layer. On a 4 GB VPS, that leaves roughly 3.1 GB for customer workloads. Heavier panels can consume twice as much at idle, leaving significantly less room for PHP workers, database caches, and everything else that actually serves your customers. The math is not dramatic on a single server. On 20 or 50 servers, the cumulative difference in margin and account density becomes substantial. [See full technical specifications and requirements](/technical-spec) ## Feature coverage: nothing should require a workaround Managed VPS customers expect more than file uploads and a basic DNS editor. They expect full-stack service management that works reliably under production conditions. That means the panel needs to handle: **DNS** with a complete zone editor covering A, AAAA, CNAME, MX, TXT, and SRV records. Not just the basics, but the full set you need for modern email authentication and service routing. **Email infrastructure** built on Postfix and Dovecot, with DKIM, SPF, and DMARC configured automatically. Plus spam filtering and webmail that does not require manual setup per domain. **SSL automation** via Let's Encrypt with auto-renewal that actually works, plus support for custom certificates when customers bring their own. **Database management** with MariaDB (MySQL 8 compatible), performance monitoring, and a web-based interface like Adminer for when customers or your support team need direct access. **Security tools** including ModSecurity for WAF-level protection, CageFS for process isolation between accounts, and a configurable firewall that does not require SSH to manage. **Backups** that run on a schedule, support incremental snapshots, and can be restored with a single action when something goes wrong. **Multi-PHP** support with per-account version selection from PHP 7.4 through 8.5, including extension management. adminbolt ships all of this out of the box. [See the full feature list](/features). ## API-first design: automation that does not require workarounds Managed VPS operations run on automation. Account creation from WHMCS or Blesta, DNS updates triggered by deployment pipelines, SSL issuance built into your provisioning workflow. A panel that treats its API as secondary to the UI forces you to build fragile workarounds: scripts that scrape web interfaces, manual steps that slip through the cracks, or integrations that break when the UI changes. adminbolt's API is not an add-on. Every action available in the panel is available via API. Provisioning, DNS, domain management, user administration, service control: all of it is accessible programmatically from day one. If you connect to WHMCS today and want to build a custom dashboard next quarter, the API is already there. [API documentation](https://docs.adminbolt.com/api) ## Pricing model: flat per-server vs. per-account This is where many managed VPS operators run into trouble as they grow. Per-account licensing means your panel bill scales with your account count, not with your infrastructure. At 100 accounts per server you are paying one amount. At 300 accounts the math is significantly worse, and the increase comes directly out of your margin. Flat per-server pricing inverts that relationship. With adminbolt, one server is $20 per month whether it hosts 10 accounts or 1,000. You can fill a server to its hardware limit without the panel bill growing. Your licensing cost becomes predictable, and growth makes your economics better rather than worse. [Full pricing comparison](/pricing-comparison) ## Dedicated support when you are running at scale Documentation and community forums cover most questions for small setups. But when you are managing dozens of servers with hundreds of customers, you occasionally need to talk to someone who built the software, not just someone who read the same docs you did. adminbolt's partner program is designed for operators running at scale. It includes direct access to the engineering team, priority support, and input into the roadmap. If you are evaluating adminbolt for a larger deployment, [reach out and we can discuss what that looks like for your operation](/contact). --- The install is a single command and takes under five minutes on AlmaLinux 9: ```bash curl -sSL https://get.adminbolt.com/install.sh | bash ``` Thirty-day free trial, no credit card required. [Start the evaluation](https://get.adminbolt.com). d:T1501, The adminbolt beta is open. It is not a demo environment with placeholder features or a waitlist for something that might ship in six months. It is a full hosting control panel running production workloads for real operators. If you are a hosting provider, reseller, or system administrator looking for a modern panel, here is what you need to know. ## What the beta includes The core of adminbolt covers everything you would expect from a production-ready hosting panel: **Domain management** with full DNS control. Add and configure domains, edit zone records directly, manage nameservers. The DNS editor covers A, AAAA, CNAME, MX, TXT, and SRV records. **Email infrastructure** built on Postfix and Dovecot. Full SMTP/IMAP support, DKIM, SPF, and DMARC configured automatically, spam filtering, and webmail. Per-domain settings where they matter. **SSL certificates** via Let's Encrypt with automatic issuance and renewal. Custom certificate support for customers who bring their own. **Database management** with MariaDB (MySQL 8 compatible). Performance monitoring, safe configuration options, and web-based management through Adminer. **Backups** running on a schedule, with incremental snapshots and one-click restore. On-demand backups when you need them. **User permissions** with role-based access for resellers, end customers, and administrators. Each role sees and can do what it should, nothing more. These are not placeholder features. They are tested, documented, and used in production deployments today. ## What makes the beta worth looking at specifically Beyond the standard feature set, the beta gives you access to what makes adminbolt different from older panels. **Agent-based architecture.** Each server runs a lightweight local agent. Configuration changes, deployments, and service operations happen on the server itself, not through a central intermediary. This keeps things fast and keeps servers operational even if connectivity to the control plane is temporarily interrupted. **API-first design.** Every action in the panel is available via the REST API. Account provisioning, DNS management, SSL operations, service control - all of it is accessible programmatically from day one. Connect to WHMCS, Blesta, or your own tooling without waiting for an official integration. **Configuration control.** PHP versions and extensions per domain, mail policy settings per account, resource limits you set and adjust directly, security rules configurable through the panel. Tune the environment for different customers without SSH. **Multi-server support.** Add multiple servers as nodes: web nodes, email nodes, database nodes. Manage all of them from one dashboard and one API. The email node feature lets you put mail on a dedicated IP for better deliverability without building a separate mail infrastructure from scratch. Beta participants work with these features early and help shape what comes next. ## Who should join The beta is designed for operators who are running production environments and want to evaluate adminbolt against real workloads. Specifically: Hosting providers who want a stable, modern panel that does not have unpredictable licensing costs. Operators who are considering migrating away from legacy setups and want to test the water before committing. Teams where automation and API access are a core requirement, not a nice-to-have. People who are willing to provide feedback and have opinions about how hosting tooling should work. If you are evaluating alternatives to your current panel, the beta is the right moment. You get full access, real infrastructure, and direct contact with the team building it. ## What beta participants get **Early access.** Use adminbolt before the general release and work with features while they are still being shaped. **Direct influence.** Your feedback affects feature priorities, design decisions, and roadmap sequencing. This is the window where operator feedback has the most impact. **Stable pricing.** adminbolt's pricing model is designed to be predictable and permanent. No surprise increases tied to your account count. **Direct support.** During the beta, you have access to the team directly, not just documentation and community forums. The beta is also the moment when adminbolt meets the real diversity of hosting environments: different OS versions, custom automation scripts, legacy integrations, compliance requirements. No internal test environment can reproduce all of that. Beta operators are part of building something that works in the real world. ## How to get started Getting started takes under five minutes. Check the requirements first: AlmaLinux 9, at least 2 CPU cores, 2 GB RAM minimum (4 GB recommended), 20 GB disk, root access. The full [technical specification](/technical-spec) has everything you need. Run the installer: ```bash curl -sSL https://get.adminbolt.com/install.sh | bash ``` Join the community on [Discord](https://discord.gg/YUchdPHHMy) or the [community forum](https://community.adminbolt.com) to connect with other operators and get direct support. --- The beta is open now. The foundation is ready. [See features](/features), [view pricing](/pricing), or [contact us](/contact) if you have questions before getting started. e:T1521, 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](https://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: ```bash curl -sSL https://get.adminbolt.com/install.sh | bash ``` See the [technical specification](/technical-spec) for requirements, or [get in touch](/contact) if you have questions about how the architecture fits your specific setup. f:Tf23, For years, hosting control panels have been both the backbone and the bottleneck of the industry. Providers rely on them for every operation: from creating accounts to managing DNS, from running backups to provisioning new services. Yet those same panels often introduce friction where there should be none, limit options that should be configurable, and add costs that grow in ways operators cannot easily predict or control. We want to be transparent about something: the panels that exist today are not failures. They work. They handle shared hosting reliably and have served the industry for decades. But a number of basic operational problems have remained unsolved for a surprisingly long time, and we think that deserves to change. ## The problems we are building to solve **No unified dashboard for multi-server operations.** Most panels are designed with a single-server mental model. When a hosting business grows to five or ten servers, operators end up with five or ten separate login sessions, five or ten dashboards to check, and no clean way to get a picture of the whole fleet from one place. This is a solved problem in infrastructure tooling generally. It should not require workarounds in a hosting panel. **Painful migrations between servers.** Moving accounts from one server to another is a manual, multi-step process on most panels: backup, restore, DNS changes, verification, cleanup. In an era of CDNs, cloud-native tooling, and automated deployments, this level of manual work stands out as an obvious gap. **Email and web forced onto shared infrastructure.** Many setups put email and web on the same server and the same IP. When something goes wrong with a site on that server, it can affect the email reputation for every domain on the box. The tools to separate them cleanly should be built into the panel, not treated as a custom infrastructure project. **No clear path from shared hosting to larger infrastructure.** Growing from a shared hosting setup to VPS-scale or dedicated server infrastructure often means switching panels entirely, rebuilding configurations from scratch, and migrating everything manually. There is no reason the panel should not support the full range of hosting models in one consistent interface. ## What we are building instead adminbolt is designed to match the best panels on the market on the fundamentals - domains, email, SSL, databases, backups, user management - while addressing the structural limitations that have remained unresolved. That means multi-node architecture built in from the start, not as an add-on. It means an API that covers every panel action so automation is never an afterthought. It means pricing that does not penalize you for growing your customer base. We also think hosting providers should be able to offer their customers more than storage and bandwidth. The most valuable parts of the internet stack are increasingly captured by SaaS platforms and managed services. A modern hosting panel should help providers work alongside agencies, freelancers, and partners in ways that create new value - not just manage commodity infrastructure. ## What this means for operators today For hosting providers evaluating adminbolt, the immediate differences are practical: predictable licensing with no per-account fees, configuration control that does not require workarounds or support tickets, and API-first architecture that makes automation straightforward from day one. The larger goal is a panel that helps hosting companies grow rather than one that creates friction as they do. The industry has been static for long enough that we think there is real room to build something better. Explore our [features](/features) or check the [technical specification](/technical-spec) for system requirements and what a real deployment looks like. 0:{"buildId":"N7W8jdbB70dGgzSRQ4mSQ","rsc":["$","$1","c",{"children":[[null,["$","$L2",null,{}],["$","main",null,{"className":"relative py-[72px] px-[52px] border-b-4 border-[var(--color-border)] bg-[var(--color-section)]","children":["$","div",null,{"className":"container text-center","children":[["$","header",null,{"className":"mb-[52px]","children":[["$","div",null,{"className":"flex items-center justify-center gap-[10px] text-[11px] font-medium tracking-[0.14em] uppercase text-[#e8820c] mb-[22px]","children":[["$","span",null,{"className":"block w-7 h-[1.5px] rounded bg-[#e8820c] opacity-70"}],"Blog"]}],["$","h1",null,{"className":"font-black text-[44px] leading-[1.06] tracking-[-0.03em] text-[#f0ede4] max-w-[680px] mx-auto mb-[16px]","children":["Insights for hosting",["$","br",null,{}],"professionals."]}],["$","p",null,{"className":"text-[15px] font-light leading-[1.75] text-[#f0ede4]/45 max-w-[560px] mx-auto","children":"Practical guides and comparisons: cut panel costs, reduce RAM usage, migrate without downtime."}]]}],["$","$L3",null,{"posts":[{"slug":"adminbolt-launch","title":"adminbolt is Live","description":"Today we're officially launching adminbolt in production. Here's what we built, why we built it, and what we're betting the next decade on.","date":"2026-03-19","content":"$4","author":"adminbolt team","category":"Launch Announcement","image":"/img/adminbolt_ready.jpg","readingTime":5},{"slug":"plus-hosting-grupa-pilot-adminbolt","title":"Plus Hosting Grupa Starts a Production Pilot with adminbolt","description":"Plus Hosting Grupa, part of the publicly listed DHH Group, has launched a structured production pilot of adminbolt across their European hosting portfolio. Here is what this means for us.","date":"2026-02-25","content":"$5","author":"adminbolt team","readingTime":2},{"slug":"best-cpanel-alternatives-2026","title":"Best cPanel Alternatives in 2026: A Hosting Provider's Guide","description":"Compare hosting control panel options for providers in 2026: pricing models, architecture, multi-server support, and who each panel fits best.","date":"2026-02-20","content":"$6","author":"adminbolt team","readingTime":7},{"slug":"cpanel-pricing-2026-costs-save","title":"Hosting Panel Pricing in 2026: Per-Account vs. Flat Pricing Explained","description":"How per-account and flat per-server pricing models work, what they cost at different account counts, and how to calculate which model fits your hosting business.","date":"2026-02-20","content":"$7","author":"adminbolt team","readingTime":4},{"slug":"hosting-panel-resource-usage-compared","title":"How Much RAM Does Your Hosting Panel Use? (And Why It Matters)","description":"Your control panel runs 24/7 and uses server RAM before a single customer logs in. Here is how to check your panel footprint and what it means for account density.","date":"2026-02-20","content":"$8","author":"adminbolt team","readingTime":4},{"slug":"manage-multiple-hosting-servers-one-panel","title":"How to Manage Multiple Hosting Servers from One Dashboard","description":"Growing from one server to five means five logins, five dashboards, and a lot of repeated work. Here is how multi-node architecture solves that.","date":"2026-02-20","content":"$9","author":"adminbolt team","readingTime":4},{"slug":"separating-email-web-hosting-why-how","title":"Separating Email and Web Hosting: Why and How","description":"When email and web share the same IP, one bad neighbor can hurt everyone's deliverability. Here is how to separate them without turning it into a full-time ops project.","date":"2026-02-20","content":"$a","author":"adminbolt team","readingTime":5},{"slug":"welcome-to-adminbolt-blog","title":"adminbolt Blog: Technical Guides and Updates for Hosting Providers","description":"Guides, product updates, and industry insights for hosting providers running adminbolt or evaluating cPanel alternatives. Practical content for VPS and dedicated server admins.","date":"2026-02-02","content":"$b","author":"adminbolt team","readingTime":3},{"slug":"why-enterprise-hosting-control","title":"Hosting Control Panel for Managed VPS Providers: What Actually Matters","description":"Managed VPS providers need more than basic shared hosting features. Here's what to look for: resource efficiency, full feature parity, API-first design, and flat pricing.","date":"2026-02-01","content":"$c","author":"adminbolt team","readingTime":5},{"slug":"adminbolt-beta-launch-how-to-join","title":"adminbolt Beta: What's Included and How to Join","description":"The adminbolt beta is open. Here's what's available, who should join, and what early operators get.","date":"2025-10-15","content":"$d","author":"adminbolt team","readingTime":4},{"slug":"adminbolt-architecture-api-first-agents","title":"adminbolt Architecture: Agents, API-First Design, and Full Configuration Control","description":"How adminbolt is built differently: lightweight agents on every server, API as the foundation, and operator-level configuration flexibility.","date":"2025-10-12","content":"$e","author":"adminbolt team","readingTime":5},{"slug":"adminbolt-vision-modern-hosting-panel","title":"adminbolt Vision: A Hosting Panel That Keeps Up With the Industry","description":"Current panels work, but fundamental problems remain unsolved. Here's what adminbolt aims to change for hosting providers.","date":"2025-10-08","content":"$f","author":"adminbolt team","readingTime":3}]}]]}]}],"$L10"],["$L11"],"$L12"]}],"loading":null,"isPartial":false} 15:T66c,M2.96792e-07 2.11642C2.96792e-07 1.58464 0.21125 1.07464 0.587278 0.698608C0.963305 0.322581 1.47331 0.111331 2.00509 0.111331H21.9927C22.2563 0.1109 22.5173 0.162454 22.7609 0.26304C23.0045 0.363626 23.2258 0.511269 23.4123 0.697516C23.5987 0.883763 23.7466 1.10496 23.8475 1.34843C23.9483 1.59191 24.0001 1.85289 24 2.11642V22.1041C24.0003 22.3676 23.9486 22.6287 23.8479 22.8723C23.7472 23.1159 23.5994 23.3372 23.4131 23.5237C23.2268 23.7101 23.0055 23.858 22.762 23.9588C22.5184 24.0596 22.2574 24.1115 21.9938 24.1113H2.00509C1.74169 24.1113 1.48086 24.0594 1.23752 23.9586C0.994184 23.8578 0.773096 23.71 0.586892 23.5237C0.400688 23.3374 0.253017 23.1162 0.152316 22.8728C0.0516145 22.6294 -0.000143013 22.3685 2.96792e-07 22.1051V2.11642ZM9.49964 9.26188H12.7495V10.8939C13.2185 9.95569 14.4185 9.11133 16.2218 9.11133C19.6789 9.11133 20.4982 10.9801 20.4982 14.4088V20.7601H16.9996V15.1899C16.9996 13.2371 16.5305 12.1353 15.3393 12.1353C13.6865 12.1353 12.9993 13.3233 12.9993 15.1899V20.7601H9.49964V9.26188ZM3.49964 20.6106H6.99927V9.11133H3.49964V20.6095V20.6106ZM7.5 5.36078C7.5066 5.66043 7.45328 5.95837 7.34317 6.23713C7.23306 6.51588 7.06838 6.76984 6.8588 6.98409C6.64921 7.19834 6.39894 7.36857 6.12268 7.48479C5.84641 7.60101 5.54972 7.66088 5.25 7.66088C4.95028 7.66088 4.65359 7.60101 4.37732 7.48479C4.10106 7.36857 3.85079 7.19834 3.6412 6.98409C3.43162 6.76984 3.26694 6.51588 3.15683 6.23713C3.04672 5.95837 2.9934 5.66043 3 5.36078C3.01295 4.77263 3.25569 4.21292 3.67624 3.80153C4.09678 3.39015 4.6617 3.15979 5.25 3.15979C5.8383 3.15979 6.40322 3.39015 6.82376 3.80153C7.24431 4.21292 7.48705 4.77263 7.5 5.36078Z10:["$","footer",null,{"className":"relative overflow-hidden bg-gray-50/80 dark:bg-black/10 border-t border-[var(--color-border)]","children":[["$","div",null,{"className":"absolute inset-0 bg-gradient-to-b from-white/20 via-gray-100/40 to-gray-200/60 dark:from-transparent dark:via-transparent dark:to-transparent pointer-events-none","aria-hidden":true}],["$","div",null,{"className":"relative container py-12 lg:py-20","children":[["$","div",null,{"className":"grid grid-cols-1 sm:grid-cols-2 lg:grid-cols-6 gap-10 lg:gap-8 mb-10","children":[["$","div",null,{"className":"lg:col-span-2 space-y-6","children":[["$","div",null,{"children":[["$","$L13",null,{"href":"/","className":"flex items-center gap-2 text-[var(--color-heading)] font-bold text-xl mb-2","children":[["$","div",null,{"className":"w-6 h-6 bg-[var(--color-primary-200)] rounded-sm"}],"Adminbolt Inc."]}],["$","p",null,{"className":"text-sm text-[var(--color-typography-lighter)] max-w-xs","children":"The hosting control panel built for the next decade."}]]}],["$","$L14",null,{}],["$","div",null,{"children":[["$","h3",null,{"className":"text-sm font-semibold text-gray-800 dark:text-white mb-2","children":"Address"}],["$","p",null,{"className":"text-sm text-[var(--color-typography-lighter)]","children":["Adminbolt, Inc.",["$","br",null,{}],"1111b S. Governors Ave., STE 25364",["$","br",null,{}],"Dover, DE 19904"]}]]}],["$","div",null,{"className":"flex items-center gap-2","children":[["$","a",null,{"href":"https://www.linkedin.com/company/adminbolt/","target":"_blank","rel":"noopener noreferrer","className":"w-10 h-10 inline-flex items-center justify-center hover:[&_svg_path]:fill-[var(--color-primary-200)] transition-colors","aria-label":"LinkedIn","children":["$","svg",null,{"width":"24","height":"24","viewBox":"0 0 24 25","fill":"none","xmlns":"http://www.w3.org/2000/svg","children":["$","path",null,{"fillRule":"evenodd","clipRule":"evenodd","d":"$15","fill":"var(--color-footer-icon)"}]}]}],["$","a",null,{"href":"https://discord.gg/YUchdPHHMy","target":"_blank","rel":"noopener noreferrer","className":"w-10 h-10 inline-flex items-center justify-center hover:[&_svg_path]:fill-[var(--color-primary-200)] transition-colors","aria-label":"Discord","children":"$L16"}]]}]]}],"$L17","$L18","$L19","$L1a"]}],"$L1b"]}],"$L1c","$L1d","$L1e"]}] 11:["$","script","script-0",{"src":"/_next/static/chunks/105be88731c1dd83.js","async":true}] 12:["$","$L1f",null,{"children":["$","$20",null,{"name":"Next.MetadataOutlet","children":"$@21"}]}] 22:T4b3,M22.0179 2.18903C20.3016 1.44525 18.5147 0.904329 16.6573 0.611328C16.4222 1.01702 16.1636 1.53541 15.9755 1.96364C14.0005 1.67064 12.0021 1.67064 10.0271 1.96364C9.81551 1.49033 9.58039 1.03956 9.32177 0.611328C7.46437 0.904329 5.654 1.44525 3.96118 2.21157C0.575552 7.05735 -0.34139 11.7679 0.105325 16.4334C2.10379 17.8533 4.31385 18.9352 6.6885 19.6113C7.22926 18.9126 7.69949 18.1914 8.09918 17.4251C7.32331 17.1546 6.59446 16.8165 5.88912 16.4109C6.07721 16.2756 6.24179 16.1404 6.42988 16.0052C10.5914 17.8984 15.4347 17.8984 19.5962 16.0052C19.7843 16.1404 19.9489 16.2756 20.137 16.4109C19.4316 16.8165 18.6793 17.1546 17.9034 17.4251C18.3031 18.1914 18.7733 18.9126 19.3141 19.6113C21.6887 18.9126 23.9223 17.8533 25.8973 16.4334C26.4145 11.0241 24.9568 6.33612 22.0179 2.18903ZM8.66345 13.5485C7.37033 13.5485 6.33583 12.4215 6.33583 11.0467C6.33583 9.67183 7.37033 8.52236 8.66345 8.52236C9.98009 8.52236 11.0146 9.64929 11.0146 11.0467C10.9911 12.4215 9.98009 13.5485 8.66345 13.5485ZM17.3156 13.5485C16.0225 13.5485 14.988 12.4215 14.988 11.0467C14.988 9.67183 16.0225 8.52236 17.3156 8.52236C18.6323 8.52236 19.6668 9.64929 19.6432 11.0467C19.6197 12.4441 18.6087 13.5485 17.3156 13.5485Z16:["$","svg",null,{"width":"26","height":"20","viewBox":"0 0 26 20","fill":"none","xmlns":"http://www.w3.org/2000/svg","children":["$","path",null,{"d":"$22","fill":"var(--color-footer-icon)"}]}] 17:["$","div",null,{"children":[["$","h3",null,{"className":"text-lg font-semibold text-gray-800 dark:text-white mb-4","children":"Product"}],["$","ul",null,{"className":"space-y-3","children":[["$","li",null,{"children":["$","$L13",null,{"href":"/features.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Features"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/integrations.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Integrations"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/pricing.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Pricing"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/pricing-comparison.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Compare"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/compare/cpanel.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"adminbolt vs cPanel"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/compare/directadmin.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"adminbolt vs DirectAdmin"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/compare/plesk.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"adminbolt vs Plesk"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/roadmap.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Roadmap"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/converter.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"cPanel converter"}]}]]}]]}] 18:["$","div",null,{"children":[["$","h3",null,{"className":"text-lg font-semibold text-gray-800 dark:text-white mb-4","children":"Resources"}],["$","ul",null,{"className":"space-y-3","children":[["$","li",null,{"children":["$","a",null,{"href":"https://docs.adminbolt.com","target":"_blank","rel":"noopener noreferrer","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Documentation"}]}],["$","li",null,{"children":["$","a",null,{"href":"https://docs.adminbolt.com","target":"_blank","rel":"noopener noreferrer","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"API Reference"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/docs/migration-guide.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Migration Guide"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/blog.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Blog"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/technical-spec.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"System Requirements"}]}]]}]]}] 19:["$","div",null,{"children":[["$","h3",null,{"className":"text-lg font-semibold text-gray-800 dark:text-white mb-4","children":"Partners"}],["$","ul",null,{"className":"space-y-3","children":[["$","li",null,{"children":["$","$L13",null,{"href":"/contact.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Partner Program"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/contact.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Become an Affiliate"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/contact.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Contact Sales"}]}]]}]]}] 1a:["$","div",null,{"children":[["$","h3",null,{"className":"text-lg font-semibold text-gray-800 dark:text-white mb-4","children":"Company"}],["$","ul",null,{"className":"space-y-3","children":[["$","li",null,{"children":["$","$L13",null,{"href":"/about.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"About Us"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/developer-application.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Careers (We're hiring)"}]}],["$","li",null,{"children":["$","a",null,{"href":"mailto:newhope@adminbolt.com","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Investors"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/contact.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Contact Us"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/bug-bounty.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Bug Bounty Program"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/privacy.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Privacy Policy"}]}],["$","li",null,{"children":["$","$L13",null,{"href":"/terms.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Terms of Service"}]}]]}]]}] 1b:["$","p",null,{"className":"text-center text-sm text-[var(--color-typography-lighter)] pt-4 border-t border-[var(--color-border)] mt-6","children":[["$","$L13",null,{"href":"/do-you-like-cpanel.html","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Do you like cPanel?"}]," · ",["$","$L13",null,{"href":"/","className":"text-sm text-[var(--color-typography-lighter)] hover:text-[var(--color-primary-200)] transition-colors","children":"Try adminbolt"}]]}] 1c:["$","div",null,{"className":"container py-8 border-t border-[var(--color-border)]","children":["$","$L23",null,{}]}] 1d:["$","div",null,{"className":"divider"}] 24:T66c,M2.96792e-07 2.11642C2.96792e-07 1.58464 0.21125 1.07464 0.587278 0.698608C0.963305 0.322581 1.47331 0.111331 2.00509 0.111331H21.9927C22.2563 0.1109 22.5173 0.162454 22.7609 0.26304C23.0045 0.363626 23.2258 0.511269 23.4123 0.697516C23.5987 0.883763 23.7466 1.10496 23.8475 1.34843C23.9483 1.59191 24.0001 1.85289 24 2.11642V22.1041C24.0003 22.3676 23.9486 22.6287 23.8479 22.8723C23.7472 23.1159 23.5994 23.3372 23.4131 23.5237C23.2268 23.7101 23.0055 23.858 22.762 23.9588C22.5184 24.0596 22.2574 24.1115 21.9938 24.1113H2.00509C1.74169 24.1113 1.48086 24.0594 1.23752 23.9586C0.994184 23.8578 0.773096 23.71 0.586892 23.5237C0.400688 23.3374 0.253017 23.1162 0.152316 22.8728C0.0516145 22.6294 -0.000143013 22.3685 2.96792e-07 22.1051V2.11642ZM9.49964 9.26188H12.7495V10.8939C13.2185 9.95569 14.4185 9.11133 16.2218 9.11133C19.6789 9.11133 20.4982 10.9801 20.4982 14.4088V20.7601H16.9996V15.1899C16.9996 13.2371 16.5305 12.1353 15.3393 12.1353C13.6865 12.1353 12.9993 13.3233 12.9993 15.1899V20.7601H9.49964V9.26188ZM3.49964 20.6106H6.99927V9.11133H3.49964V20.6095V20.6106ZM7.5 5.36078C7.5066 5.66043 7.45328 5.95837 7.34317 6.23713C7.23306 6.51588 7.06838 6.76984 6.8588 6.98409C6.64921 7.19834 6.39894 7.36857 6.12268 7.48479C5.84641 7.60101 5.54972 7.66088 5.25 7.66088C4.95028 7.66088 4.65359 7.60101 4.37732 7.48479C4.10106 7.36857 3.85079 7.19834 3.6412 6.98409C3.43162 6.76984 3.26694 6.51588 3.15683 6.23713C3.04672 5.95837 2.9934 5.66043 3 5.36078C3.01295 4.77263 3.25569 4.21292 3.67624 3.80153C4.09678 3.39015 4.6617 3.15979 5.25 3.15979C5.8383 3.15979 6.40322 3.39015 6.82376 3.80153C7.24431 4.21292 7.48705 4.77263 7.5 5.36078Z25:T4b3,M22.0179 2.18903C20.3016 1.44525 18.5147 0.904329 16.6573 0.611328C16.4222 1.01702 16.1636 1.53541 15.9755 1.96364C14.0005 1.67064 12.0021 1.67064 10.0271 1.96364C9.81551 1.49033 9.58039 1.03956 9.32177 0.611328C7.46437 0.904329 5.654 1.44525 3.96118 2.21157C0.575552 7.05735 -0.34139 11.7679 0.105325 16.4334C2.10379 17.8533 4.31385 18.9352 6.6885 19.6113C7.22926 18.9126 7.69949 18.1914 8.09918 17.4251C7.32331 17.1546 6.59446 16.8165 5.88912 16.4109C6.07721 16.2756 6.24179 16.1404 6.42988 16.0052C10.5914 17.8984 15.4347 17.8984 19.5962 16.0052C19.7843 16.1404 19.9489 16.2756 20.137 16.4109C19.4316 16.8165 18.6793 17.1546 17.9034 17.4251C18.3031 18.1914 18.7733 18.9126 19.3141 19.6113C21.6887 18.9126 23.9223 17.8533 25.8973 16.4334C26.4145 11.0241 24.9568 6.33612 22.0179 2.18903ZM8.66345 13.5485C7.37033 13.5485 6.33583 12.4215 6.33583 11.0467C6.33583 9.67183 7.37033 8.52236 8.66345 8.52236C9.98009 8.52236 11.0146 9.64929 11.0146 11.0467C10.9911 12.4215 9.98009 13.5485 8.66345 13.5485ZM17.3156 13.5485C16.0225 13.5485 14.988 12.4215 14.988 11.0467C14.988 9.67183 16.0225 8.52236 17.3156 8.52236C18.6323 8.52236 19.6668 9.64929 19.6432 11.0467C19.6197 12.4441 18.6087 13.5485 17.3156 13.5485Z1e:["$","div",null,{"className":"container py-6 flex items-center justify-between max-sm:flex-col max-sm:gap-y-6 max-sm:text-center","children":[["$","span",null,{"className":"text-[var(--color-typography-lighter)] text-sm font-normal","children":"© 2024 - 2026 adminbolt. All rights reserved. | Built for hosting professionals"}],["$","ul",null,{"className":"flex flex-wrap items-center gap-4 text-sm font-medium sm:mt-0","children":[["$","a",null,{"href":"https://www.linkedin.com/company/adminbolt/","target":"_blank","rel":"noopener noreferrer","className":"w-10 h-10 inline-flex items-center justify-center hover:[&_svg_path]:fill-[var(--color-primary-200)] transition-colors","aria-label":"LinkedIn","children":["$","svg",null,{"width":"24","height":"24","viewBox":"0 0 24 25","fill":"none","children":["$","path",null,{"fillRule":"evenodd","clipRule":"evenodd","d":"$24","fill":"var(--color-footer-icon)"}]}]}],["$","a",null,{"href":"https://discord.gg/YUchdPHHMy","target":"_blank","rel":"noopener noreferrer","className":"w-10 h-10 inline-flex items-center justify-center hover:[&_svg_path]:fill-[var(--color-primary-200)] transition-colors","aria-label":"Discord","children":["$","svg",null,{"width":"26","height":"20","viewBox":"0 0 26 20","fill":"none","children":["$","path",null,{"d":"$25","fill":"var(--color-footer-icon)"}]}]}]]}]]}] 21:null