macOS · iOS · iPadOS · Mac Catalyst. Single-import, @Published license state, offline-ready Ed25519 lease verification.
SDKs and platforms
Keylight ships first-party SDKs for Swift, Rust, and JavaScript/TypeScript today. They verify licenses identically — the same signed v3 lease and Ed25519 check, proven by a shared set of cross-SDK conformance vectors. The HTTP API is stable and public, so any other platform can integrate the same way.
Available today
Section titled “Available today”CLIs, daemons, and desktop apps — including a first-party Tauri plugin. Synchronous and runtime-free (no async/Tokio), with the offline lease verifier built in.
Browser, Node, Deno, Bun, and edge/Workers from one fully-typed package. Online activation plus offline Ed25519 verification — server-side validation, Electron apps, and web apps alike.
Cross-platform desktop, Unreal Engine games, and JUCE audio plugins. Header-only, zero-dependency core with the offline Ed25519 lease verifier built in — plus native Unreal (FHttpModule) and audio-thread-safe JUCE adapters.
More platforms — demand-driven
Section titled “More platforms — demand-driven”We add a first-party SDK when a real builder needs one, not to fill out a grid. The most-requested next candidate:
C# / .NET
Windows apps (WPF, WinUI, MAUI) and Unity / Godot projects. On request
If your stack isn’t a first-party SDK yet, you’re not blocked: the REST API ships licensing on any platform today, and the conformance vectors mean a ~60-line verifier behaves exactly like the SDKs above.
Anything else: use the REST API
Section titled “Anything else: use the REST API”The Keylight backend is a thin, well-documented HTTP service. If your platform isn’t in the list above, you can still ship licensing today by calling the API directly:
- Every request to
/{tenantId}/activate,/{tenantId}/validate, and/{tenantId}/deactivateis a plain JSON POST. - Authenticate with the
X-Keylight-SDK-Keyheader (one per tenant, rotatable from the dashboard). - Successful responses include an Ed25519-signed lease you can verify locally with the tenant’s public key — no need for a network round-trip on every app launch.
The signature format and lease schema are documented in Offline leases, so a 60-line implementation is enough for most platforms.