Grace Period Behavior
When an Enterprise license expires, AppProfileSafe provides a 30-day grace period during which the application continues to operate with full Enterprise functionality. This allows time to renew the license without interrupting ongoing operations. After the grace period, the application falls back to the Community Edition.
Timeline
| Phase | Days Relative to Expiry | Edition | Notifications |
|---|---|---|---|
| Normal | > 30 days before expiry | Enterprise (full) | None |
| Expiring soon | ≤ 30 days before expiry | Enterprise (full) | Warning dialog on startup with days remaining and renewal link |
| Grace period | 0–30 days after expiry | Enterprise (full) | Warning dialog on startup stating the license has expired and showing the grace end date |
| Expired | > 30 days after expiry | Community | GUI shows "Community Edition" on the License tile. CLI returns exit code 3. |
GUI Behavior
During the grace period, the following changes are visible:
- The License tile on the Dashboard turns yellow and shows the grace end date with remaining days (e.g. "Grace ends 2026-04-30 (12 days)").
- A warning dialog ("License Info") is displayed automatically on every startup. The dialog explains that the license has expired and includes a direct link to the license renewal portal.
- All application features remain fully functional — export, import, mapping, simulation, and CLI operations work without restrictions.
After the grace period ends, the GUI continues to work but switches to Community Edition mode. All GUI features (export, import, mapping, simulation, DryRun, local audit log, run reports) remain available with unlimited applications. Enterprise-only features (CLI, SIEM/webhook event delivery, compliance reports) are disabled. See Community vs. Enterprise Edition for the full feature comparison.
CLI Behavior
In CLI mode, the grace period is handled the same way: a warning is written to the application log, and the operation proceeds normally. Once the grace period ends (> 30 days past expiry), the CLI returns exit code 3 and does not execute any operations. The CLI requires a valid Enterprise license at all times — there is no Community Edition fallback for CLI operations.
Renewing During or After Grace Period
To restore Enterprise functionality, deploy an updated License.json with a new SubscriptionEndDateUtc value. See Installing or Updating a License for instructions. The new license takes effect on the next application start — no other action is required.
This works at any time: during the grace period, after it has ended (while running in Community mode), or even on a fresh installation. There is no penalty or lockout for renewing late.