Kontrol7

Kontrol7 decides what a product is. Your billing decides how it is sold. The catalogue is where the two meet.

Kinds

A plan has a kind: shared hosting, reseller hosting, managed database, business email, DNS hosting, virtual private server or object storage. Ready-made plans exist for each kind; every one is an ordinary plan you can edit, rename or retire. Prices are set in your billing system, not here.

A plan is a bundle of grants and allowances

Grants are what an account may hold: so many websites, databases, mailboxes, mail domains, DNS zones, backup policies, virtual machines, private networks, buckets or AI endpoints. Allowances are the ceilings they run under: storage and data transfer per month for the account; memory, CPU, processes and simultaneous PHP requests per site; connections per database; mailbox size; vCPUs, memory and disk per virtual machine; storage per bucket.

Grants are checked whenever something is created, and every refusal says why. The ceilings apply to each thing as it runs. A website's disk allowance is enforced where its server's disk is prepared for it (see Adding a web server, and preparing its disk), and measured everywhere. Data transfer is measured and reported for billing.

A plan also switches things on: one-click applications, staging copies, Redis, SSH and SFTP, long-running processes, a dedicated address, the assistant and building sites with it, automatic WordPress updates, on-demand malware scans, a copy of backups in the customer's own storage, a public IPv4 address for each virtual machine, and whether its virtual machines are managed or looked after by the customer.

Virtual machine sizes are bounds, not labels

A VPS size lives in the plan allowances and applies per machine: vCPUs, memory and disk. An order naming no size gets the plan size. An order above it is refused with "beyond this plan" rather than quietly accepted and billed.

Why a location might not be offered

A location is offered for a kind only when a server there holds every job that kind needs, accepts new work, has checked in recently, and is below its capacity watermark. A virtual server also needs working virtualisation there, a managed database a running engine, and business email a passing mail readiness check. So an unavailable location is a statement about capacity or readiness, not a fault. DNS is the exception: it is served from every nameserver, so it has no location.

Preview

Some products and features carry a Preview label until they have run on real servers: object storage, AI endpoints, private networks, DNS served by Cloudflare, and Zephyr on a virtual server. Each says in one line why it is still Preview. The label shows in the plan editor, the plans list, the ready-made plans and the catalogue your billing reads. Everything else, including mail and virtual machines, is generally available.

Measured facts

Each kind reports facts Kontrol7 has measured, and a product page may claim these and nothing else.

• Hosting — the PHP, Node and Python versions on offer; which web server each location runs; where per-site containers run; HTTP/3 and IPv6 locations; the one-click applications; automatic certificates; DNSSEC; backup intervals with restore-drill counts.
• Virtual private server — bootable images, the vCPU, memory and disk bounds, root login by SSH key, snapshots, IPv6 locations, private networks (Preview).
• Managed database — engines by location, the PostgreSQL extensions present by default, connections per database.
• DNS — nameservers, DNSSEC, IPv6, record types, and whether every nameserver serves every zone.
• Business email — webmail, the mail ports, the authentication records published, and mail readiness by location.