Kontrol7
Hosting, under control. The hosting control panel your customers log into, on servers you own: websites, mail, DNS, databases, backups, virtual machines, object storage and AI endpoints, with unlimited customers and sites. Add a server in one paste, give it a job, and it stays the way you set it.
What your customers can have
Everything a plan can include, and how resellers and their customers fit in.
Everything Kontrol7 manages for a customer is one kind of thing, and every kind is created, changed, suspended, brought back and removed the same way. That is why "sell one mailbox" and "sell a two-hundred-site reseller plan" run on the same machinery.
What a plan can include
Websites, DNS zones and records, certificates, databases and database users, mailboxes and mail domains, forwarders, FTP accounts, scheduled jobs, backup policies, virtual machines, private networks, storage buckets and AI endpoints. Private networks, storage buckets and AI endpoints are still in Preview.
How accounts fit together
account (a reseller holds customers; quotas roll up)
└── subscription → plan → what it grants
└── the websites, mailboxes, databases ... themselves
An account can have a parent. That is what makes a reseller tree a tree rather than a special case, and it is why suspending a reseller suspends everything beneath it without deleting anything. When a reseller's own plan is cancelled, only the reseller's own services are removed at the end of the grace period; each of its customers is judged on their own.
A plan is a bundle of grants
A plan does not describe a product in prose. It grants a number of each kind, with the allowances they run under, and its kind decides which grants are even allowed.
| Plan kind | May include |
|---|---|
| Shared hosting, reseller hosting | anything |
| Managed database | databases, backup policies |
| Business email | mail domains, mailboxes, DNS zones |
| DNS hosting | DNS zones |
| Virtual private server | virtual machines, backup policies, private networks |
| Object storage | buckets |
A grant the kind does not sell is refused with the reason, rather than accepted and ignored.
Where the walls are
The website is the unit of isolation, not the account. Each site runs in its own container with its own ceilings for CPU, memory and processes, and its own disk allowance, which is enforced where the server's disk is prepared for it and measured everywhere. A customer with five sites has five walls, and sites on the same server cannot reach each other.
Databases are deliberately not one container each. They live on shared engines on database servers, with a database, a user and grants per customer, because one copy of the engine per customer is a cost nobody gets back.
Last updated 3 November 2026