Platform, license and server status
Two console pages look after the installation itself: Platform & license holds your product's name and address and the license of this installation, and Server status shows how the server is coping right now.
Platform & license
Open Platform & license. It has two cards: License and Branding.
License
The License card shows the state of this installation's license:
| Status | Meaning |
|---|---|
| Active | The license is valid for this domain. |
| Not activated | No purchase code has been activated yet. |
| Needs a check-in | The license server could not be reached for too long. |
| Revoked | The license was revoked. |
| Moved to another installation | The purchase code was activated on another server. |
| Invalid | The stored license could not be verified. |
Once a code is activated, the card also shows the Purchase code (only its last characters), License type, Domain, Buyer, Support until and Last check, and at the bottom the Installation id.
To activate a license:
- Enter your Purchase code (CodeCanyon → Downloads → your item → License certificate & purchase code).
- Check the Application URL: the address of this installation. The license is tied to its domain.
- Choose Activate.
Check now asks the license server for a fresh confirmation straight away. The platform also checks in by itself about once a day. If the license server cannot be reached, nothing changes for 30 days.
Deactivate releases the purchase code from this installation, for example before you move to a new server. The console locks until a purchase code is activated again. See Move to a new server.
What a license problem affects
Without a valid license for the domain you are on, the console shows only Platform & license, and new shops cannot sign up. Shop portals, tills, kitchen screens and payment webhooks keep working, so shops never stop selling because of a license problem.
On a development address (such as localhost, a .test or .local name or a private IP address) the console works without a license, and the card says so. If the license is active but you open the console on another domain, the card shows "This license is for … ; you are on …".
More detail on licensing: License.
Branding
The Branding card sets how your platform presents itself. It is shown on sign-in, menus, emails and invoices.
| Field | What it does |
|---|---|
| Product name | Your product's name, for example "Riyadh Retail POS". It replaces :app in every label, and appears in sidebars, footers, page titles, password-reset emails and new billing invoices. |
| Application URL | The address of the platform. Changing the domain needs the license to be activated again. |
| Support email | The address shop owners can write to. |
Choose Save. The new name appears at once.
Example: you resell the platform to bakeries under your own brand. Set Product name to "BakeryPOS" and Support email to your helpdesk address. Shop owners see "BakeryPOS" on the sign-in page and on their invoices.
Server status
Open Insights › Server status to see the live load of the API server and its database, without opening a terminal. It is useful during busy hours, after an update, or while you run a load test.
The page refreshes by itself every 10 seconds by default; you can choose 30 seconds, 1 minute or off. It pauses while the browser tab is hidden.
| Section | What it shows |
|---|---|
| Alerts | Plain-language warnings: requests waiting for a database connection, connection pool almost full, machine overloaded, Java memory above 85 %, memory or disk almost full, server errors, waiting locks, queries running longer than 5 seconds. |
| Tiles | Sales per minute, API requests per minute (average time, in progress), machine CPU and load, machine and Java memory, database connection pool (active / max / waiting), disk. |
| Charts | The last 60 minutes: API requests per minute with errors in red, sales per minute, slowest response per minute. |
| Slowest API endpoints | Over the last 15 minutes. |
| Database | Version, connections, locks, cache hit rate, deadlocks, size; the queries running now (longest first, with what they wait on); the largest tables. Many full scans on a big table usually mean a missing index. |
| API process | Uptime, CPU, memory, threads, live screens connected, requests since start. |
| Server log | Recent warnings and errors, with filter and search. |
Good to know:
- Watching the page never slows sales down. When the database is busy, the page shows the last figures it has instead of taking a connection.
- If the database is overloaded, the traffic and process figures still show, with an error on the database sections.
- Request counts and the log reset when the API restarts.
- The page sees the API container and the machine. Other containers on the same server are not shown.
- Super administrator viewers can see the page, but the Server log is for super administrators only, because log lines may contain customer data.
Related pages
Last updated 10 Oct 2026