Continuity and portability
Your exit plan starts before an outage.
Keep your records and trust keys under your control. An export helps you prepare; it does not automatically replace a running licensing service.
What keeps working if PermitCore is unavailable?
| Capability | What you can rely on | What you must prepare |
|---|---|---|
| Already-issued offline tokens | Local signature verification with independently trusted public keys, until the signed deadline and within the signed license/product/device context. | Ship the required public keys and proof. A disconnected app cannot discover a later server revocation. |
| Online validation and activation | These requests need a reachable licensing service. | A tested replacement service or an intentionally designed final offline build. A perpetual license does not make a token permanent. |
| Floating seats and usage reporting | New checkouts, heartbeats and server-side usage operations need their service. An existing lease remains bounded by its deadline. | Plan how your application stops or changes behavior when renewal fails. |
| New Store purchases and renewals | Your Stripe or Paddle account remains your own provider relationship. Billing at the provider does not by itself deliver a PermitCore license. | Arrange fulfillment and customer support, and manage subscriptions with the provider. A PermitCore outage does not automatically cancel provider billing. |
| Independent issuance | Your exported active private signing key can sign compatible proof. | Protect the key, implement the documented format and test a separate issuer. Export does not deploy it or unlock paid hosted features. |
1. Download your account records
A CompanyAdmin with a verified email can use Company Settings → Export My Data (ZIP) on every plan. The ZIP contains company/team/product records, encrypted license inventory and controls, activation records, available audit events from the last 90 days, and API-key metadata. It includes the encryption salt and license IVs, but no plaintext license values or passphrase.
The archive also includes customer profiles, Store catalog/design, orders, subscription/payment receipts and references, bundles, templates, usage records, access/reseller configuration and historical public signing keys. Provider event, SSO, floating and webhook records contain metadata only.
This is a selected data export, not a complete database backup. Uploaded file bytes, raw event/delivery payloads, authentication/provider secrets and platform-global configuration are excluded. Image and download URLs are references: keep original asset files and provider records separately. Reads are sequential rather than a transactionally consistent restore snapshot. Review the exact export contents and exclusions before depending on a recovery plan. Request assistance at info@permitcore.dev for data not covered by an available export.
Keep your license-key passphrase or recovery material separately. Ciphertext, IV and salt cannot recover a forgotten passphrase on their own. Encrypt your backup storage and restrict access: the archive contains personal data.
2. Take your signing keys anytime
Every plan, including Free, allows its CompanyAdmin to open Settings → Security → Business Continuity, read the warning, acknowledge responsibility and export the active signing key. The export includes the private PKCS8 key, public SPKI key and kid. API keys cannot perform this sensitive export.
Never put a private signing key in a customer application. Customer apps receive only trusted public verification keys. Keep a protected vendor recovery package, record which key signed each release and preserve earlier verification keys from your release configuration. Rotation History contains metadata; the active-key export is not a bundle of every historical private key.
Export does not revoke PermitCore's copy, extend existing token deadlines, enable paid offline activation or grant Enterprise self-hosting. Follow the business continuity and rotation guidance.
3. Test recovery while the service is available
- Inventory validation, activation, floating seats, usage reporting, sign-in, downloads, payments and email dependencies in your application.
- Open your exports and verify that you can decrypt a test license using your retained passphrase. Confirm that the records and assets your migration needs are actually present.
- In an isolated environment, verify compatible proof with a trusted public key and test your independent issuer. Test a clean installation, a replacement device and the period after an old token expires.
- Test with PermitCore endpoints unavailable. Include expired proof, invalid signatures, wrong product/device context and failed seat renewal; an outage must not turn invalid evidence into authorization.
- If you self-host on Enterprise, retain both your database backup and the required deployment secrets, then test restoration. The account-data ZIP is not a substitute for that backup. See the self-hosting guide.
Our planned-shutdown commitment
For a planned service shutdown, we will announce the shutdown and an export window through our Status and Changelog pages and keep account-data and active signing-key exports available to authenticated CompanyAdmins during that window, including Free accounts. We will assist verified account owners with retrieving their tenant's available records and signing material. We will not publish private keys or hand them to unverified requesters.
An unexpected outage, loss of infrastructure or inaccessible account can prevent a later handoff. Export and test your own copies now. This commitment does not promise permanent offline access, an automatic final build, a complete migration service or recovery of data already deleted under the applicable retention policy.
Project contact: permitcore · Zagreb, Croatia · info@permitcore.dev. Read our security information and Terms alongside this plan.