Reliability
You're trusting LicenseFort with something real: the ability to stop your software running for your customers. Here's exactly what happens if we're ever the problem — described plainly, not as a vague uptime badge.
If LicenseFort is unreachable, your customers keep running.
Every product has a configurable offline-grace window — 72 hours by default, adjustable 0–720 hours (or disabled entirely) in Dashboard → Products. If a device already validated successfully and a later check can't reach LicenseFort at all — network failure, timeout, an outage on our end — it keeps working until that window expires instead of locking out the moment we're unreachable.
Enforced everywhere, not just documented
Built into the Protect Software wizard's injected code (MT4/MT5, the Windows launcher) and every official SDK — Python, .NET, Go, PHP/WordPress, and the Chrome extension client. Each one caches the grace window from the last successful check and honors it locally when a live check fails.
Never overrides a real rejection
Grace only ever covers "couldn't reach LicenseFort." The moment a device gets an explicit answer — revoked, expired, wrong account — that cached grace period is cleared immediately. A denied license can't be resurrected by disconnecting the network.
You choose the window, per product
0 hours (fail closed instantly) up to 720 hours (30 days). Not gated by plan tier — every LicenseFort plan, including Free, gets the same control.
Reaches software already in the wild
The current grace window is read live off the validate response, not baked into a build once and forgotten — change the setting in your dashboard and it applies the next time each customer's software checks in successfully, no re-download or recompile required.
See it in the wizard on the MT4/MT5 page, or in code in the SDK docs.
What's actually monitored
A dedicated health check — GET /api/v1/health — exercises the same database connection POST /api/v1/license/validate depends on, polled continuously. You can hit it yourself right now — it's not gated behind anything. A public, live status page (so you can see current and historical uptime instead of taking our word for it) is on the way; this page will link directly to it the moment it's live, not before.
If LicenseFort ever shuts down
No licensing vendor in this space publishes a real answer to this, so here's ours. This is a forward commitment about what we'll do if that day ever comes — not a feature running today, since it only matters in a scenario we hope never happens.
If LicenseFort ever ceases operating, before the validation API goes offline for good we commit to:
- Advance notice. Every tenant with an active account gets a direct email with a real shutdown date, not a surprise.
- A full export of every active license record — every key, product, and activation you own — in a documented, machine-readable format, downloadable directly from your dashboard.
- A final SDK/wizard update that adds a local, offline verification mode reading that export directly — so software already in your customers' hands keeps validating against data you hold, not a server that no longer exists.
- 12 months of that offline validity from the export date — enough time to migrate to another provider or your own backend without your customers' software breaking the day we close.
More on how LicenseFort protects what it holds on /security, and the full list of who processes data on our behalf on /subprocessors.