Operate
Administration
The operator console is a separate application at a private address. It reviews licenses, customers, test payments, plugin packages and service analytics, then manages access with explicit authority.
Administrator access
The operator console is not part of the public website and is not linked from it. Operators receive its private address from the service owner; administrators also see an Open administration link in their customer account. It distinguishes its sample preview from the connected service. Connected administrator access must be explicitly granted by the service operator. A customer session alone never grants access to other customers or license administration.
Overview and customer analytics
Sign in directly in the operator console. Overview shows current license status, active site capacity, expiries in the next 30 days and recent observed actions. Customer analytics include references found in licenses or test orders, not every provisioned identity. Select a customer to review its licenses.
Periods and data history
Choose the last 7, 30 or 90 UTC calendar days for payment and service activity. License totals always describe the current snapshot. Service observations are collected after Go starts, for at most 90 days and 200 recent actions in process memory. Service observations reset on restart. The persistent local setup keeps test orders in a private JSON ledger; other setups can use memory-only test orders. The dashboard identifies the active storage mode. Historical license creation dates and earlier activity are unavailable. CSV reports identify their period and observation start.
Service health and refresh
Services shows uptime, average handling time, rejected requests, server errors, successful downloads and fixed API endpoint counters. Health/session checks, admin reads and public assets are excluded from traffic counts. Enable optional refresh every 30 seconds or refresh manually. A failed refresh marks the last snapshot stale and disables changes; session expiry removes private data and requires sign-in.
Plugin packages
Packages lists the active ZIP and up to 20 earlier packages. The package built with the service is registered at startup. An upload must be a ZIP of at most 64 MiB whose plugin header Version equals the version entered; it becomes active after confirmation. Reusing a version with different contents is rejected. Activating an earlier package is a rollback; download links issued for the previous package stop working.
Manual fulfillment
Issuing a license requires a verified customer reference, a unique order reference, future expiry and a site limit. Replaying an existing fulfillment must not issue a second bearer key. Site approval, renewal and revocation are explicit operator actions.
Test orders
Test checkout orders are examples, not proof of payment. They do not authorize manual license issuance. The payment provider, tax policy and billing terms remain unconfigured until selected and approved.