License

You must have a valid Scrydon license bundle before completing setup. Contact sales@scrydon.com to request one.

The bundle is a JSON file containing the signed JWT and the public half of the key that signed it:

{
  "jwt":       "eyJhbGciOiJNTC1EU0EtNjUiLCJ0eXAiOiJKV1QiLCJraWQiOiJrZXktMjAyNi0wMSJ9…",
  "publicKey": "hT3nK…"
}

The license is signed with ML-DSA-65, a post-quantum signature scheme, and publicKey is the base64url-encoded raw public key — not a PEM block. The guided installer uses it to check the bundle offline; the platform itself accepts a license only if a Scrydon signing key built into the release verifies it.

After installing the chart, paste the bundle into the /setup wizard. Alternatively, pre-seed its jwt via the auth.secrets.LICENSE Helm value. See Helm: pre-seed the license.

To inspect a bundle before installing and confirm the tier, entitlements, and expiry match what you ordered, use the in-browser License Checker.

License verification runs in the api-platform pod at runtime through the @scrydon/better-auth-license Better-Auth plugin. There is no init container and no scrydon-license Kubernetes Secret to manage. The license JWT is stored in the platform_config table and is replaced through the platform UI.

See Licensing for the full lifecycle.