Skip to main content

Security and Backup

License Center protects signing and authentication material and provides an encrypted, portable full-installation backup for disaster recovery.

💾 Create a backup​

Only a platform administrator can see the Backup tab in Settings. Select Backup, enter and confirm a passphrase of at least eight characters, and save the downloaded .lcb file. The passphrase cannot be recovered by License Center.

The encrypted file contains every organization and database record, the node identity, activation state, integration credentials, authentication material, and managed signing keys. Keep the file and its passphrase in separate, approved secret-management locations.

Backups are portable between desktop and server installations. During restore, License Center re-encrypts persisted secrets with the destination installation's master key. Host-specific configuration such as ports, public URLs, allowed origins, cookie policy, and session durations is not included.

♻️ Restore a backup​

Open Settings > Backup, select Restore, choose the .lcb file, enter its passphrase, and type RESTORE. License Center validates and stages the complete backup before replacing live data. If the final database or node-identity update fails, the prior installation is restored automatically.

Restore replaces all current organizations and data and restores the backed-up node identity. All active sessions and password-reset requests are invalidated, so everyone must sign in again. Wait for WordPress and WooCommerce sync jobs to finish before creating or restoring a backup.

🛡️ Protect one-time exports​

Generated signing keys may be exported only once as encrypted PKCS#8. Store the file and passphrase separately. Test restoration in an isolated environment before relying on it for disaster recovery.

🌐 Network security​

  • Publish server deployments through HTTPS.
  • Enable secure cookies in production.
  • Keep allowed origins explicit.
  • Restrict database, master-key, and backup access to the License Center service identity and authorized operators.
  • Monitor /healthz and /readyz without exposing business data.

📋 Operational recovery checklist​

  1. Create an encrypted backup from Settings > Backup and store its passphrase separately.
  2. Record the application version and relevant host configuration without copying credentials into the ticket.
  3. Test restoration in an isolated environment.
  4. Verify sign-in, activation status, product catalogs, order balances, and the ability to decrypt a managed signing key.
  5. Confirm public JWKS endpoints and license verification before returning the service to production.

Filesystem-level backups remain possible for deployment operators. Stop the service and capture the SQLite database, WAL/SHM files, node ID, and matching master-key source together.

⚠️ Do not use clean reset as recovery​

Deleting the SQLite database creates a new tenant identity and invalidates the old activation context. A schema reset is a development action, not a backup or production recovery method.