TNS Panel
Introduction
TNS Panel is a multi-tenant web hosting control panel for AlmaLinux and Rocky Linux. It is built as a replacement for CentOS Web Panel (CWP), which is no longer maintained, and it keeps what CWP users expect: one panel for sites, mail, DNS, databases, FTP and backups on your own servers.
Who it is for
- Hosting providers and agencies that run shared hosting on their own VPS or dedicated servers.
- Providers migrating off CWP, cPanel, Plesk, DirectAdmin, HestiaCP, CyberPanel or aaPanel (see Migration).
- Resellers who need to sell hosting under their own brand.
What it manages
- Websites: Apache, nginx or OpenLiteSpeed as the public edge, PHP per account, Let's Encrypt certificates (including wildcards).
- Mail: Postfix, Dovecot and Rspamd, with webmail, DKIM, SPF and DMARC published for you.
- DNS: BIND with dynamic zones, DNSSEC and optional replication to Cloudflare.
- Databases: MariaDB and PostgreSQL with phpMyAdmin and phpPgAdmin.
- FTP/FTPS, file manager, browser terminal, cron, Git deployment, staging, containers, backups, statistics, firewall, malware scanning.
- Clustering: several nodes behind one panel (see Clustering).
The account hierarchy
TNS Panel has three roles, nested the way ISPConfig and WHM do it:
| Role | Can do | Sees |
|---|---|---|
| Admin | Everything on the node(s): services, firewall, updates, plans, resellers, clients | All accounts |
| Reseller | Creates hosting plans and clients inside the pool the admin gave them; white-label branding | Only their own clients |
| Client | Manages their own sites, mail, databases, FTP, backups | Only their own resources |
A client can also create sub-users with per-area permissions (see Client guide).
Every level only sees what belongs to it. The authorization check is repeated by the agent on the server, not only in the web interface.
Two separate web interfaces
The admin and client interfaces are two different applications on two different ports (admin 2087, client 2083). You can firewall the admin port to your own addresses and clients will never reach it, even if a permission check had a bug.
Interface language
The interface is available in English and Spanish. The language selector is on every page.
How this documentation is organized
Start with Requirements and Installation. The Admin guide and Client guide are task-oriented references. Security model explains what is and is not isolated between your customers.