Trust

What happens if we’re down. Or gone.

You are putting your revenue behind our uptime. That deserves a straight answer rather than a badge.

If we’re down

Your software can keep working.

Hybrid verifies locally at every start and only requires a successful check inside the offline window you signed. A failed check does not become a fake revocation.

Inside the signed window: local verification keeps working.
After the window: the SDK returns STALE — your application controls the recovery message.
Offline mode: the application never contacts DYCRYPT.

What remains in your hands

The public key verifies without us.

Your application already carries the product public key or certificate. It verifies the licence signature locally before it trusts dates, product identity, machine binding, or typed claims.

That means an existing Offline licence does not become unreadable because DYCRYPT is unreachable. Hybrid also keeps local proof, subject to the offline window you chose and signed.

Signed answers fail closed.

For Online and Hybrid, DYCRYPT signs each check answer with the same product key. A different host can copy the JSON shape, but it cannot produce a receipt your application accepts.

If the issuer cannot answer or the receipt is invalid, the check is not recorded as successful. The application reaches STALE instead of trusting a forged ACTIVE.

Procurement question?

Ask for the evidence that exists now.

Tell us which uptime, continuity, certification, residency, or key-custody control your review requires. We’ll separate current evidence from roadmap work.

Start a trust review →