Kontrol7

Kontrol7 is a hosting control panel. You set up websites, DNS zones, mailboxes, databases, virtual machines, buckets and AI endpoints in the panel, and every server you give it is kept the way the panel says.

How it works

There are two parts. The panel is where you, your resellers and your customers set things up. The agent runs on every server you add. It sets the server up to match the panel, checks each change before it goes live, and reports back. The panel never signs in to your servers and never runs commands on them.

That is why a setting changed by hand is put back, why a server that restarts recovers by itself, and why a rebuilt server is set up again by the same path as any other change.

What a server is

A server is a machine you have added with one pasted command and given one or more jobs. The job decides what is set up on it.

Job	What it runs
Web	Websites, each in its own container, and the web server you chose for that machine
Database	Shared MariaDB and PostgreSQL, with a login and grants per customer
Mail	Mailboxes, webmail at mail.<domain>, sending reputation
DNS	A nameserver that serves every zone
Backup	Backups kept apart per customer, restore drills
Telemetry	The traffic and log store for the Analytics tabs
VM host	Virtual machines from cloud images
Object storage (Preview)	S3 buckets with their own credentials
AI (Preview)	OpenAI-compatible endpoints on the machine's own GPU

Mail always runs on its own machines, never beside websites: different reputation, different scaling, different attack surface.

The order things happen in

1. Install the panel.
2. Add a server with the pasted command and tick its jobs. The agent connects outbound — you do not open a port to it.
3. Add two DNS servers, choose your nameserver names and point them at those machines at your registrar.
4. Add a server for websites — with its disk prepared so each site's disk allowance is enforced (see Adding a web server, and preparing its disk) — one for databases, and one for backups, ideally somewhere else.
5. Create a plan, or add the ready-made plans, one per kind.
6. Point your billing at the orders API. If that is Zephyr, there is no integration work.
7. Put the first site up. DNS and the certificate are handled for you — this is the end-to-end proof.

The dashboard keeps a setup list along these lines, with a few more items: an off-site copy of the panel's own data, a firewall on every server, where alerts go, two-factor sign-in and a second person. It ticks each item itself when it is actually true, and names any web server whose disk allowances are not yet enforced.

What to read next

• Adding a web server, and preparing its disk — so a site's disk allowance is enforced, not only measured.
• Keeping servers the way you set them — what happens when a setting is changed by hand, a server restarts, a server is rebuilt, or the panel cannot be reached.
• What your customers can have — everything a plan can include, and how resellers fit in.
• Plans, locations and what you can sell — how a plan becomes something your shop can offer.
• Selling Kontrol7 hosting — connecting your billing, and what happens when an order is paid or missed.