Licenses and offline use
How company module entitlements remain usable through temporary connectivity and billing interruptions.
Updated
Local entitlement checks
When a company subscribes to a business module, Railbase stores a protected entitlement and checks normal execution locally. A brief railbase.app or network outage does not turn day-to-day module use into a remote round trip.
Activation, renewal, plan changes, revocation, and approved instance moves do need periodic marketplace connectivity. The admin shows the resulting status without exposing protected signing or activation material.
What is licensed
Every current commercial module is licensed per company per month. The entitlement identifies the company, module, plan, validity, and other commercial limits needed by that plan. It does not meter users, roles, positions, or approvers as paid seats.
Staying current
Railbase periodically refreshes entitlement state so renewal and plan changes take effect without reinstalling. A temporary grace state may cover an in-flight paid renewal; use the date shown in the account/admin rather than assuming a fixed recovery period. Trials and explicit revocations may follow stricter terms displayed at purchase.
Expiry and revocation
- Expired and unrenewed: the module becomes dormant after the applicable term/grace. Its stored data remains.
- Explicitly revoked or reversed payment: execution stops according to the stated revocation terms. Stored data remains.
- Restored subscription: Railbase refreshes the entitlement and the module resumes without a new install in the normal case.
Dormancy is not deletion. Purge is a separate, explicit operator action.
FAQ
Do I need continuous internet access?
No. Normal entitlement checks are local. Occasional connectivity is required for purchase, activation, renewal/state refresh, and update.
If a subscription lapses, do I lose data?
No. The module becomes dormant, while its records remain on your infrastructure.
Do auditors or employees increase the subscription price?
No. Billing is per company per month. Give every user only the roles they need; role assignment affects authorization, not price.