License Checker
Decode a Scrydon license bundle (or a bare JWT) in your browser to inspect tier, entitlements, and expiry — without standing the platform up.
Drop or paste your { jwt, publicKey } license bundle below. Decoding runs entirely client-side — the JWT is never uploaded anywhere. You can also paste a bare token if you only have the JWT.
Paste a license bundle (the JSON file your Scrydon account team delivered) or a bare JWT. Decoding happens entirely in your browser — nothing is uploaded.
What you'll see
| Section | What it shows |
|---|---|
| Header banner | Organization, tier, and license ID (jti claim). |
| Status pill | Time remaining — green over 30 days, amber under 30, red expired. |
| Standard claims | Customer ID (sub), issuer (iss), audience (aud), issued-at and expiry timestamps (ISO 8601). |
| Entitlements | Licensed CPU cores, RAM (GB), and VRAM (GB). VRAM is contractual only — the platform records it but does not runtime-enforce GPU limits. |
| Raw claims | The full decoded JWT payload as JSON, plus the bundled public key. Useful for support tickets. |
What this tool does not do
- It does not verify the signature. Verification requires checking the JWT signature against the bundled public key — the Scrydon platform does this at runtime on every request to a license-gated capability. Customers do not need to verify locally; if a bundle is tampered with, the platform will reject it at install or first request.
- It does not phone home. No request leaves your browser. You can disconnect from the network and the tool still works.
- It does not modify the bundle. Paste, decode, read — that's it.
Common questions
Why is the tier shown as "Tier not specified"?
Older test licenses sometimes ship without the scrydon.tier claim populated. Production-issued bundles always include it. If you see this on a customer-facing bundle, contact your Scrydon account team and ask for a re-issue.
My license shows "expired N days ago" but the platform still works.
Running pods are not killed when a license expires — license-gated capabilities just start returning 403 from the API. Restart deployments only after applying a refreshed bundle. See Licensing → Grace Period.
Can I check a bundle for a future install?
Yes — the tool only looks at the JWT's claims. You can decode a bundle before you ever touch a Kubernetes cluster, for example to confirm the tier and entitlements match what was ordered.
What if I only have the .jwt file, not the JSON bundle?
Paste the raw token directly into the textarea. The tool falls back to decoding a bare JWT if the input isn't valid bundle JSON. Note that the Scrydon /setup wizard requires the full bundle (it needs the public key) — a bare JWT works for inspection here but not for activation.
Related
- Helm — full install walk-through, including how the bundle flows into the
/setupwizard. - Licensing — license lifecycle, rotation, modes, and grace periods.
- Prerequisites — what to ask Scrydon for before starting an install.