Architecture

At a high level, a TiiPanel deployment has three moving parts:

1. The control plane — the web UI and API your team and customers use. Installed once, on a single server.
2. Node agents — a lightweight background service on each hosting server, enrolled into your control plane. It carries out the provisioning tasks the control plane dispatches to it (creating accounts, issuing certificates, running backups) and reports status back. Agents connect outbound to the control plane — they never need an inbound port opened.
3. The licensing service (this website) — issues license keys, validates activations, and serves updates. Your control plane talks to it periodically over HTTPS; see the API docs.

customer browser ──▶ control plane (one, central) ──▶ dispatches work to ──▶ node agent(s) ──▶ system services
                              │
                              ▼
                    licensing API (this site)

A single-server deployment runs the control plane and its one node agent on the same machine. As you add servers, each new one runs just the agent and enrolls into that same control plane — the control plane itself still runs on exactly one server, whether you have one node or many.

Offline tolerance

The control plane is designed to keep working if it briefly can't reach the licensing API — see the grace period behaviour described in Licensing. A network blip should never lock a paying customer out of their own server.