# Product entitlement and offline use

> How a Suite remains usable through temporary control-plane interruptions.

_Updated: 2026-09-22_

A paid Business Suite receives a protected company-level entitlement with the
Product, Basic/Pro/Max plan, release identity and validity period. The private
estate caches current entitlement so ordinary work does not require a remote
round trip for every request.

A screening-data outage is an availability incident, not a detected sanctions
match. It does not by itself cancel or revoke a current paid-period entitlement.
Railbase continues signed licence validation through a heartbeat whose rolling
window is no longer than 24 hours; a confirmed hit follows the separate
suspension and review process described in the Terms.

Managed Cloud also requires a current company admission permit, refreshed within
120 seconds. Losing that permit pauses the affected company until connectivity
and eligibility recover. The longer on-premise offline window below does not
extend this Cloud permit.

## Temporary interruption

On-premise control-plane or network interruptions use the published grace policy.
The estate continues under its last valid state while reconnect attempts and
operator warnings are recorded. Grace is designed for availability, not as a
permanent disconnected licence.

## Expiry, cancellation and restoration

When entitlement ends, Product operation becomes unavailable under the
applicable term and grace rules. Customer records remain in the private estate.
After payment, current KYC/export checks and Product eligibility are restored,
the Account can refresh entitlement without rewriting those records.

## FAQ

### Does every user action call railbase.app?

No. Normal Suite work is local to the private estate.

### Can we operate permanently without licence refresh?

Only if an executed Order expressly provides that entitlement model. The normal
subscription requires periodic signed refresh.