One Linux user per account
Account creation runs useradd: its own user, group and home under /home, mode 0711, so Apache can reach public_html and other accounts cannot list it.
For hosting companies & MSPs
Vanta Panel is a self-hosted control panel for hosting companies that charges $10 per server for unlimited accounts, where cPanel charges per account. It ships the mail server, authoritative DNS with private nameservers, a customer panel, a cPanel importer and a free WHMCS module.
Free for 1 account then $10 a server for unlimited 14-day money-back
The arithmetic at your scale
cPanel Premier covers 100 accounts and then adds $0.49 a month for every account after that, so the licence keeps climbing for as long as your business grows. Vanta Panel Unlimited is $10 a month for the server, whether it holds 30 accounts or 3,000.
| Accounts | cPanel per year | Vanta Panel per year | You keep per year |
|---|---|---|---|
| 100 | $839.88Premier | $120Unlimited | $719.88 |
| 200 | $1,427.88Premier + 100 | $120Unlimited | $1,307.88 |
| 500 | $3,191.88Premier + 400 | $120Unlimited | $3,071.88 |
| 1,000 | $6,131.88Premier + 900 | $120Unlimited | $6,011.88 |
Above 100 accounts, every new customer adds $5.88 a year to a cPanel licence. On Vanta Panel Unlimited it adds nothing.
Licences are per server, so a fleet costs $10 × servers. 3 servers with 200 accounts each pay $360 a year here and $4,283.64 on cPanel list price.
Migration
With the Import from cPanel tool in vWHM. Package each account on the old server, copy the archive across and import it: Vanta Panel recreates the site files, databases, mailboxes and cron jobs. The old cPanel server is never modified and keeps serving until you move the domain, so not switching is your rollback.
/scripts/pkgacct <user> if you have root on the cPanel server, or the customer’s own Download a Full Account Backup if you do not. Same archive either way.
scp it into /var/lib/vantapanel/cpimports/ on the new server and it appears on the Import page. Check that the sha256sum matches on both ends.
vWHM reads the archive, you tick what to bring across, and it imports in the background. Test the site through a hosts-file line, then move the DNS.
What the archive cannot bring across
Mailbox passwords (cPanel’s hashes are not portable), custom DNS records such as SPF, DKIM or an external MX, SSL certificates (issued fresh in one click), and addon domains or FTP accounts. There is no bulk importer: plan a large estate as a scheduled project.
Migrating a whole server from cPanel The step-by-step guide, with screenshots
Billing
Yes. The WHMCS module is a free download with no separate licence. It works with every tier, and the tier's account limit applies, so hosting companies run it on Unlimited. WHMCS then drives each account’s lifecycle over a scoped API token.
| In WHMCS | On your server |
|---|---|
| New order | Account created with its username, domain, password and plan |
| Invoice overdue | Account suspended |
| Payment received | Account unsuspended |
| Upgrade or downgrade | The new package’s limits applied |
| Password reset | Panel password changed |
| Cancellation | Account and its databases removed |
The module authenticates with a token you create in vWHM, scoped to accounts:read, accounts:write and accounts:delete. It only travels over HTTPS, and you can revoke it at any time. Bill from your own system instead? The same REST API is documented, so you can provision against it directly.
Multi-tenant isolation
You are putting strangers on one kernel, so this matters most. Each Vanta Panel account is its own Linux user, and on a fresh install its PHP runs in a private PHP‑FPM pool as that user. Below is what the panel writes to disk, not a security posture.
Account creation runs useradd: its own user, group and home under /home, mode 0711, so Apache can reach public_html and other accounts cannot list it.
PHP runs as the account, with open_basedir pinned to its home, exec and system disabled, and a private session and upload tmp. Servers upgraded from an older release keep their default until vWHM’s Isolate accounts switch moves them, reversibly.
Each pool is ondemand with pm.max_children and pm.max_requests set, so one customer’s traffic spike cannot take every PHP worker on the box.
Every database user is granted rights on its own database and nothing wider. phpMyAdmin signs in as that user, so it only sees what the grant allows.
FTP users belong to the account’s group, with /usr/sbin/nologin and a home inside the account. SSH keys are per account. Nothing shares a login.
Apache writes an error and an access log per account, so usage is attributable. Packages set the disk, bandwidth, database, mailbox and subdomain limits each account is held to.
And what it is not
This is Unix-user isolation with per-account PHP‑FPM pools, the model cPanel uses, not containers or virtual machines. Accounts share one kernel, one Apache and one MariaDB, so a kernel exploit or a starved box affects everyone; sell hard resource guarantees as a separate VPS. How the panels are protected
Your product line
Everything a shared-hosting plan needs, in one licence: your own mail server, DNS on your private nameservers, free SSL, databases, backups and modern runtimes. The tiers differ only in how many accounts, mailboxes and databases a server holds; none holds the mail server back.
Vendor risk
A small vendor asking you to put your customers on its software owes you direct answers, including the unflattering ones. Anything else? Ask before you buy, or read the terms and refund policy.
A licence binds to one machine, and Unlimited puts no cap on accounts, mailboxes or databases on it. So the bill is $10 a month times the number of servers, and it stops moving as customers arrive: 3 servers with 200 accounts each is $360 a year, against $4,283.64 on cPanel list price. You can move a licence between servers yourself at no charge: release it from the old machine in your client area and activate it on the new one. Rebuilding a box is not a new licence.
Nothing you host goes offline. Websites, email and DNS keep serving, because those are stock Apache, Postfix/Dovecot and PowerDNS running on your machine — the panel manages them, it does not sit in front of them. Management degrades on a published schedule instead. From day 0 the panel reverts to free-tier limits, so you cannot create new hosting accounts, mailboxes or databases, and a renewal banner appears in vWHM; nothing existing is ever deleted. On day 3 automated backups pause — restoring an existing backup keeps working the whole time. On day 7 your customers see a service notice in vPanel. On day 14 vWHM locks to the renewal screen. Paying restores everything on the next licence check, within minutes.
The panel keeps working on its cached licence for a seven-day grace window; that is a constant in the source, not a promise. During grace the panel reports the number of days left rather than failing silently. Only after seven days of the licensing API being unreachable does it fall back to free-tier limits, and even then it does not lock you out of your own machine.
The panel is PHP source running on your own server. There is no hosted control plane to switch off, no compiled blob, and no component of your hosting that calls home to work. If our licensing server stopped answering tomorrow, the panel keeps your paid limits for a seven-day signed grace window and then falls back to free-tier limits — it does not brick and it does not lock you out of the machine. The worst case is a working server, running the same open-source services it runs today, that will not let you add new accounts from the UI. Your sites, mail and DNS never stop.
No, and there is nothing proprietary to unlock. Sites are ordinary Apache vhosts with the files under /home, mail is Postfix and Dovecot in standard Maildir format, DNS is PowerDNS, databases are MySQL/MariaDB, and certificates are ordinary Let's Encrypt certificates. Backups are plain .tar.gz archives with mysqldump .sql files inside — you can open one with tar and read it. You can rsync the entire server somewhere else, or point a different control panel at the same machine, without asking us for anything. We hold no encryption key and no piece of your stack lives on our servers.
No. You install the panel on your own VPS; we do not provision it, log into it, or receive a copy of anything on it. Your server checks in with us daily. That check-in sends the licence key and plan, a machine fingerprint, an install id, the panel version, the PHP version and OS name, your account count, and the account usernames and domains on that server; we use it to verify that a paid key is not being used on more servers than it covers. It never sends files, mailbox contents, databases, passwords or your customers' site content. You can switch it off with touch /etc/vantapanel/no-telemetry, and the privacy policy sets it out in full.
There is no separate reseller SKU, because there is nothing to gate: you buy a licence per server at the same price everyone pays, and every feature is already in it. You sell hosting under your own brand with your own nameservers, your own mail server and your own WHMCS. What Vanta Panel does not offer today is full white-labelling of the panel itself: vPanel carries Vanta Panel branding. If that is a blocker, say so before you buy rather than after.
Email support at support@vantapanel.com. Vanta Panel is a young product built by a small team; there is no enterprise customer list to point at, and inventing one would tell you nothing. What there is instead: a free tier that is the identical build, a live demo you can click through before you talk to anyone, documentation that includes the migration runbook in full, and a 14-day money-back window on your first payment. Put one real customer on it before you move fifty.
How to evaluate it
Prove it on one customer before you plan the estate. Vanta Panel has no case studies to show you, and we will not invent any; this costs a VPS for a month and tells you more than any reference call.
One command on a fresh Ubuntu or Debian VPS. The Free tier is the identical build, capped at 1 account, 1 mailbox and 1 database: enough to move one real customer and look at the result.
Not the simplest one. Pick the account with the mail volume, the odd cron jobs and the legacy PHP version, and import it while the original keeps serving.
Install the WHMCS module against that server, place a test order, let it provision, then let the invoice go overdue and watch it suspend. If that loop works, the rest is volume.
$10 a month for the server, with unlimited accounts, mailboxes and databases on it, and the mail server, authoritative DNS and private nameservers already in the box.
curl -fsSL https://get.vantapanel.com | sudo bash