Skip to content

Licence and limits

AppArch runs on your own infrastructure, and what it may do is set by your licence. There is no purchase, plan-upgrade or payment screen in the app: your limits are read from the signed licence file that comes with your contract.

For how the licence first arrives and how to install: On-prem installation.

Limit familyExamplesHow it is counted
Static limitsworkspaces, total users, users per workspaceThe source table is re-counted on every check - no separate counter is kept. Delete a user and the allowance comes back immediately.
Monthly limitsArchPilot comments, ArchScan reports, API requestsCounted per calendar month. A new month starts the counter at zero, whatever day of the month it is.

Which modules are enabled also comes from the licence.

Work does not stop the moment a limit fills. A soft window opens first:

  • you keep running up to 10% above the limit,
  • and that tolerance lasts 7 days from the first breach.

When either runs out, further calls are refused with license_limit_exceeded. The point is that your pipeline should not stop dead mid-sprint - and the window is bounded so an overage cannot quietly become permanent.

Static limits clear themselves: once the count drops back to or under the cap, the window resets.

From the management area, without restarting the application:

  • upload a new .lic file under Management → Settings → Licence, or
  • on installations with internet access, collect the licence online with your installation credentials.

A new licence takes effect as soon as it verifies. If verification fails the previous licence stays in force - a bad file cannot lock the installation out.

A licence works on one installation: an air-gapped installation needs a file issued for its own installation code, and a licence already bound to another installation is refused. Several pods sharing one database count as one installation. To move to a new server, ask AppArch to release the licence first - see One licence, one installation.