Answered before you had to ask.

It brings the cPanel, Plesk and DirectAdmin installations across your servers into one interface. Creating an account, fixing a DNS record, checking the mail queue, adding a firewall rule — you do all of it on one screen instead of switching panels server by server.

No. ctapanel sits on top of the panel you already run; it doesn’t replace it. Your cPanel stays cPanel and its own interface keeps working. What you change here shows up there, because the work goes through the panel’s own API.

Ten minutes for the first server: in WHM you create an API token with all privileges marked and paste it into the panel. Once the agent finishes its first lap — usually a few minutes — the metrics and lists fill in. No developer time and no demo call needed.

We never ask for a root password. cPanel/WHM and DirectAdmin need an API token, Plesk an admin key, and a panel-less server an SSH key. Mark every privilege on the token: the panel does not only read — it creates accounts, resets passwords and manages mail, and WHM refuses each missing privilege on its own. The token is stored encrypted, is never shown again after you save it, and you can revoke it from your own panel whenever you want.

Not on a server with a panel: the connection goes through the panel’s own port (2087 for cPanel, 8443 for Plesk, 2222 for DirectAdmin). On a server without a panel we connect over SSH, and nothing extra gets installed there either.

Yes, within clear limits. Its state, services, firewall, PHP and runtimes all show up; panel-specific things like hosting accounts and mailboxes don’t, because that server has none. Every screen says which row is empty and why.

cPanel/WHM, Plesk Obsidian and DirectAdmin — plus servers with no panel at all. All four sit side by side in the same list, each managed with the tools it actually has.

It doesn’t, and we don’t hide that. Country-based IP blocking only exists where CSF is installed, zones only on firewalld, .NET management only on Plesk. If a panel doesn’t offer something, the screen doesn’t show that field at all, so you never click into an error. The comparison table is on the home page.

Whatever your panel supports: AlmaLinux, Rocky, CentOS, CloudLinux, Ubuntu and Debian. CloudLinux is detected separately, because some features — Node.js on cPanel, for instance — depend on it.

Not yet. Today ctapanel manages Linux servers. Classic ASP.NET needs IIS, so it runs nowhere here; modern .NET does run on Linux and is managed from the panel on Plesk. We put that on the feature page too, so you know before you buy.

Three on the Solo plan, fifteen on Team, unlimited on Scale. As the count grows the lists paginate and the filters work per server, so it never turns into one enormous table.

Yes — we don’t keep a one-way copy. Creating accounts, suspending, DNS records, PHP versions all go through the panel’s own API, so you see the same result if you log into the panel. A change you make by hand in the panel shows up here on the next lap.

Four ways: between servers in your fleet, from a remote panel at another company, over FTP or over SSH. Each has its own step plan and you watch where you are live. Start a second migration and it queues, so two transfers don’t eat each other’s bandwidth.

Not entirely. You pick a server in the panel and run commands for disk, memory, service state, processes, ports and the mail queue — no PuTTY needed for that. There are no package installs, no file editing and no interactive sessions like vim; for those you still connect over SSH.

No. The assistant is rule-based and makes no network requests; it builds answers from the panel’s own data. Your host names, IPs and customer details never reach a third-party service. It can drop a suggested command into the terminal, but running it stays your decision.

Yes. You can suspend selected accounts together and move every site stuck on an end-of-life PHP version in one pass. Long-running work like this is tracked step by step in the job queue.

The panel watches your servers and raises alerts for things like an offline server, a stopped service, a filling disk or a growing mail queue, and each alert lowers the fleet health score. Today alerts live inside the panel — email and webhook notifications aren’t there yet.

It isn’t. The password itself is kept nowhere; only its vault path, how many days ago it changed and who changed it. Servers past 90 days come up as a security finding.

There are four roles: owner, sysadmin, support and read-only. Permissions are split at screen and action level, so someone on support can create an account but cannot switch the firewall off. Who reaches which servers is written in the table.

Anything irreversible asks for a separate confirmation, and the confirmation quantifies the impact: before restarting a service it tells you how many sites and mailboxes it touches. In the terminal, patterns like rm -rf / are stopped before they run. You also can’t stop the panel’s own service or delete its own firewall rule.

On the server side, yes: you switch two-factor on and off in the sshd policy and see its state per server in the security centre. Operator two-factor is tracked in the team table, and anyone missing it shows up as a banner.

Yes. The audit log records every change with who made it and when, filtered by job, alert, account, server, security, package, SSL and report. The panel’s own work is written under its own name, so no row closes with “the system did it”.

The server keeps running but the panel can’t read it: metrics stop and alerts don’t arrive. So you don’t hear about it from a customer, a key with under 30 days left becomes a security finding, and under 14 days a critical one.

Yes, on cPanel and Plesk servers running the ctapanel agent. The agent packages each account or site with the panel’s own tool, so a backup holds its files, databases and email. Every backup is a full package; there are no incremental backups. You send it to ctabox, S3-compatible storage, another of your servers or your device. DirectAdmin and panel-less servers can’t be backed up yet.

Yes. You restore a whole package to the same server or another one with the same panel, and confirm it with a one-time WhatsApp code. Restoring overwrites the site’s current files, databases and email, so take a fresh backup first if you need one. A single file, database or mailbox can’t be restored on its own, but you can browse a backup’s file index to see what it holds.

A schedule that runs more than two hours late raises a warning, and one whose latest backup failed raises a critical alert. Each stale backup also costs 1.5 points of fleet health score. You don’t have to remember to open the list: it comes to you on the dashboard. The Backups screen also flags paused schedules and servers with no schedule.

Inside the European Union. The contents of your servers are never copied: the panel reads each screen on demand. The only things stored long-term are the connection profile, the metric history and the audit log.

No, per fleet. A plan sets a server limit, and every server inside that limit is included at the same price — adding one doesn’t raise the bill. Annual billing gives you two months free.

Nothing for 14 days: no card, no feature gates. If you don’t pick a plan at the end, the account is suspended and we leave your servers alone — your data waits untouched until you pick one.

Cancel in one click, no contract. On a panel connection we install nothing: removing the record leaves nothing of ours behind, and you can revoke the API key you created for us. Your panel is never touched. If you installed the optional metrics agent it stays on that server; the panel gives you the removal command and one command clears it.

From inside the panel and over email, with a real person. The Scale plan adds priority response and a named technical contact. If your question belongs on this list, the answer lands here too.