Skip to main content

Next steps

Must-read (Wave 51 packaging & trust)​

  1. Entitlements — Policy / Plan / FeatureLimit / custom data.
  2. Verify trust (JWKS) — local ES256 verify (not RSA-in-binary).
  3. Device Identity — golden image: never bake installation private keys.
  4. Webhooks vs Local Relay — integrator push ≠ on-site sync.

Also useful​

  1. Core Concepts — shared vocabulary.
  2. Licensing Models — node-locked, floating, offline/air-gapped, trials, metered.
  3. License Keys — human key shape, normalize rules, safe handling.
  4. Offline · Air-gapped · Floating.
  5. Runtime configuration · Secrets · Customer Portal · Checkout · Deployment · Troubleshooting · Security.
  6. Reference — API overview, SDKs, OpenAPI downloads.

Integrating soon?​

  • Prefer the official Runtime SDKs — .NET, JavaScript/TypeScript, Python, Java, Go, Rust, and C++ (preview/alpha; nuget.org / npmjs / PyPI / Maven Central / proxy.golang.org / crates.io / vcpkg/Conan publish gated).
  • Do not hardcode secrets into apps or docs examples — see License Keys and Runtime Secrets.
  • Treat Runtime as a separate hostname/contract from Management.

Feedback loop​

Public behavior changes (API, errors, config, entitlements) must update English and Russian docs in the same product wave (FADR-0007). This portal is part of that Definition of Done.