Maintenance in progress
This section is currently being expanded and updated. Some content may not yet be available or may be incomplete. For urgent questions, please reach out at info@scailabs.ai.
This section is currently being expanded and updated. Some content may not yet be available or may be incomplete. For urgent questions, please reach out at info@scailabs.ai.
Desktop editors, terminal clients, and native apps you can install directly. Not SDKs.
No releases yet — teams publish here via their docs API key's downloads:write:<product> scope.
Latest releases for each ScaiLabs product. Updated automatically by each team's publishing pipeline.
## scaivault-sdk (Rust) 1.10.0 Minor release. Only the Rust SDK changes; the other SDKs already had this. - **`Signing::create_key_with(path, suite, &CreateKeyOptions)`** sets `rate_limit_per_min`, `description` and `hsm_backed` when a key is created. These settings were accepted by the API but could not be set from Rust. They cannot be changed after creation. - `CreateKeyOptions` is re-exported at the crate root. `create_key(path, suite, name)` is unchanged.
Download .crate## @scaivault/sdk (JavaScript / TypeScript) 1.9.1 Security release. - **Redirects are no longer followed.** `fetch` used to follow redirects and re-send `X-API-Key` to the target. Every request now uses `redirect: "manual"`, and a redirect throws `ScaiVaultError` (code `REDIRECT_NOT_FOLLOWED`) without retrying. Destroying a signing key now needs the new `sign:destroy` scope (server-side); `sign:manage` covers rotate, disable and enable.
Download .tgz## ScaiVault.Sdk (.NET) 1.9.1 Security release. - **Redirects are no longer followed.** The default `HttpClient` used to follow redirects and re-send `X-API-Key`. The SDK now uses a handler with `AllowAutoRedirect = false`, and a 3xx throws `ScaiVaultException` with its status code. If you pass your own `HttpMessageHandler`, disable redirects on it. Destroying a signing key now needs the new `sign:destroy` scope (server-side); `sign:manage` covers rotate, disable and enable.
Download .nupkg## scaivault-sdk (Python) 1.7.0 - **Signing engine**: new `client.signing` on the async and sync clients — create keys, `sign`, `batch_sign` (up to 100), `verify`, `get_public_key`, `rotate`, `disable`, `enable`, `destroy`. Suites ECDSA P-384, Ed25519 and ML-DSA-65; bytes in, bytes out. - **Errors**: structured error responses (`{"error": {"code", "message", "details"}}`) now populate `message`, `error_code` and `details` on every exception, in every domain. - `ScaiVaultClient(..., transport=...)` accepts a custom httpx transport (useful for testing). - `scaivault_sdk.__version__` now reports the real version.
Download .whl## scaivault-agent 1.6.0 **Custom output filenames.** A `[[certificate]]` block may now set `fullchain_file`, `cert_file`, `chain_file`, and/or `key_file` to write that artifact to an additional, explicitly-named path — so a service that references a fixed filename (apache `SSLCertificateFile`, dovecot `ssl_cert`, a single haproxy pem) can point straight at an agent-managed file instead of a reload hook copying it into place. - A relative value resolves under `out_dir`; an absolute value is used verbatim. - Overrides use the same `cert_mode`/`key_mode`/`owner`/`group` and the same atomic rename as the canonical files, so a concurrently-reloading service never sees a half-written file. - The canonical copies under `out_dir` are always kept — the renewal and content-aware checks read them — so an override adds a target, it never removes the defaults. No config changes are required for existing hosts; the new fields are optional and default to the previous behaviour.
Download .whl**ScaiVault certificate agent v1.0.0** — renews ScaiVault-managed TLS certificates on a host and reloads the service that uses them. Install with pip
Download .whlScaiKey Go SDK **v1.0.2** — bug-fix release. Single-object admin calls now return populated models instead of silently empty ones. > **Upgrade recommended for anyone on 1.0.0 / 1.0.1 that reads single objects.** > Behaviour-only fix; no API, type, or module-path changes. Drop-in. Requires Go 1.22 or later. Module path `scailabs.ai/scaikey-go`. ```go require scailabs.ai/scaikey-go v1.0.2 replace scailabs.ai/scaikey-go => ./scaikey-go-1.0.2 ``` ### The bug Every admin endpoint wraps its payload in a `data` envelope. For a **list** the body is `{"data": [ ... ], "pagination": { ... }}`; for a **single object** it is `{"data": { ... }}`. The SDK decoded list bodies into `Page[T]` (which has a `data` field) correctly, but decoded single-object bodies **straight into the model type** (`User`, `Group`, `Application`, ...), none of which has a `data` field. The JSON then matched nothing, so every single-object call returned a **zero-valued struct with a nil error** — a silent empty result, not a failure. Affected (all now fixed): `Users.Get/Create/Update`, `Groups.Get`, `Applications.Get/Create/Update/RotateSecret`, `Tenants.Get`, `Partners.Get`, `IdentityProviders.Get/Sync/TestConnection`. List calls and the unauthenticated `Public.GetApplicationByClientID` (which the server does **not** envelope) were never affected and are unchanged. ### The fix Single-object calls now decode into a generic `dataEnvelope[T]` (`{"data": T}`) and return its `.Data`, mirroring `DataEnvelope<T>` in the TypeScript and .NET SDKs and the explicit `response["data"]` unwrap in the Python SDK. All four ScaiKey SDKs now unwrap the envelope the same way; the Go SDK was the only outlier. This removes the need for any caller-side `data`-unwrapping shim. Two hermetic tests pin it (`envelope_test.go`): a single-object body must decode to a populated model, and the list path must keep decoding array + pagination. ### Standard library only Unchanged: the SDK imports nothing outside the Go standard library. ### Documentation <https://www.scailabs.ai/docs/scaikey/tutorials/web-app-login-and-logout>
Download .gzScaiKey Python SDK **v1.1.9** — makes webhook event parsing forward-compatible, so a new ScaiKey event type never breaks an older consumer. Follow-up to the 1.1.8 verifier fixes, reported by the Storey team. ## Fix - **Unknown (newer) event types no longer fail the delivery.** `WebhookEventType` is a closed enum, so before this an `event_type` newer than the installed SDK raised `WebhookPayloadError` (422). ScaiKey then retried and incremented `consecutive_failures`, so *ScaiKey shipping a new event type* looked like the consumer's endpoint degrading — and any subscriber to a `*` or `user.*` glob was exposed by default. `WebhookEvent.type` is now `WebhookEventType | str`, resolved left-to-right: - a type this SDK version **knows** resolves to the `WebhookEventType` member, exactly as before — `.value`, `isinstance(..., WebhookEventType)` and enum comparisons all keep working (fully backward compatible); - a type **newer** than this SDK arrives as a plain `str` instead of raising, so the event is delivered and the consumer can ignore or log it. No consumer code has to change, and no `strict=` flag to remember. Match known types against the enum; treat any other `type` as unhandled. `WebhookPayloadError` still fires for genuinely unreadable bodies (malformed JSON, or an envelope missing required fields) — only the closed-enum check was relaxed. ## Handling unknown types ```python from scaikey_sdk.webhooks.events import WebhookEventType event = verifier.verify_header(body, sig_header) if isinstance(event.type, WebhookEventType): dispatch(event) # a type this SDK knows else: log.info("unhandled webhook type %s", event.type) # newer than this SDK ``` ## Companion note (docs) The Webhooks reference now calls out that `group.member_removed` (and `application.group_unassigned`) does **not** by itself tell you whether a user lost access to your application — re-read `applications.get_effective_users()` (own-app, no admin scope) after the event to decide. Thanks to Storey for the observation.
Download .whl@scailabs/scaikey **v1.0.3** — adds group membership enumeration. Purely additive. ### Added The `GroupsClient` had only `list()` — no way to read a group's members, which Python and .NET have both had since 1.0.0. Anything driving group-derived permissions from TypeScript had to drop to raw HTTP. - **`groups.listMembers(groupId)`** — a group's direct members. - **`groups.listEffectiveMembers(groupId)`** — direct members plus those inherited from nested (child) groups. - **`groups.addMember(groupId, userId)`** / **`groups.removeMember(...)`** - **`groups.listNestedGroups(groupId)`** — groups nested inside this one. - **`groups.listParentGroups(groupId)`** — groups containing this one. - **`GroupMember`** and **`NestedGroup`** types. `GroupMember` models what the endpoints actually return — the *user* projection, `{id, email, display_name, status}` — not a membership row, so there is no `group_id` or `added_at`. (The Python SDK declared those as required and failed on every call until 1.1.5; this ships pinned to the real shape from the start, and is verified against a live server.) ### Also Contract tests now cover the new methods, so the shape is checked against a real ScaiKey rather than a fixture. Run with `SCAIKEY_CONTRACT_URL` and `SCAIKEY_CONTRACT_TOKEN` set; skipped otherwise. ### In 1.0.2 Fixed OIDC discovery for GLOBAL applications — the platform document sits under an extra `/oauth` segment, so `getOidcConfiguration()` 404'd for every cross-tenant app. ### In 1.0.1 One base URL now serves every client: pass the origin and each client builds its own prefix. Base URLs carrying an API prefix are reduced to the origin, so existing configurations keep working.
Download .tgz**v1.0.2** — fixes OIDC discovery for GLOBAL applications, and IdP payload parsing. Backward compatible. ### Fixed - **`getOidcConfiguration()` / `GetOidcConfigurationAsync()` 404'd for every GLOBAL application.** It built `/api/v1/platform/.well-known/openid-configuration`; the real document sits under an extra segment — `/api/v1/platform/`**`oauth`**`/.well-known/openid-configuration`. The two flavours are genuinely asymmetric on the server: | | discovery path | |---|---| | tenant | `/api/v1/auth/tenants/<slug>/.well-known/openid-configuration` | | platform | `/api/v1/platform/`**`oauth`**`/.well-known/openid-configuration` | A trap for anyone tempted to simplify this: platform **jwks** is at `/api/v1/platform/.well-known/jwks.json` — *without* the `oauth` segment. A blanket rule fixes discovery and breaks jwks. Both shapes are modelled explicitly and pinned by tests, including one guarding the jwks path. Reported against the Python SDK by the Storey team; the same construction existed here. ### Fixed (.NET only) - **`IdentityProvider.ProviderType` silently kept its default value.** The model bound only `provider_type`, but the admin list sends `type` and the tenant-scoped list sends `protocol`. Neither populated the property, so it deserialized to the first enum value — a wrong answer rather than an error. Enablement is likewise sent as a `status` string ("ACTIVE"/"INACTIVE") by the admin list. All spellings are now accepted. ### Upgrading No code changes required. ### In 1.0.1 One base URL now serves every client: pass the origin (`https://scaikey.scailabs.ai`) and each client builds its own prefix. Base URLs that already carry an API prefix are reduced to the origin, so existing configurations keep working. Tenant OAuth previously omitted the `/auth` segment and had never resolved.
Download .nupkgUpload and download now work against the registry. Before this release neither did, and no call authenticated. - Authentication fixed: the client sent `X-API-Key`; the API only reads `Authorization: Bearer`, so every request was unauthenticated. - Upload rewritten against the real API. It targeted `/api/v1/uploads/...`, which does not exist. It now uses the versioned upload routes, sends parts as raw bodies at the server's `part_size`, and marks the version ready on `complete()` - without that last step a version stays `uploading` and cannot be downloaded. - `add_file` stages and hashes; the transfer happens in `complete()`, because the registry needs the full file list when the version is created. Added `staged_files`. A session that raises before `complete()` aborts in-flight uploads and removes the version it created. - Download fixed: it requested `.../versions/{v}/files/{path}`; the route is `.../versions/{v}/download/files/{path}`. - Added `vm_image` to `ModelType`; `User-Agent` reports the real package version.
Download .gzUpload and download now work against the registry. Before this release neither did, and no call authenticated. - Authentication fixed: the client sent `X-API-Key`; the API only reads `Authorization: Bearer`, so every request was unauthenticated. - Upload rewritten against the real API. It targeted `/api/v1/uploads/...`, which does not exist. It now uses the versioned upload routes, sends parts as raw bodies at the server's `part_size`, and marks the version ready on `complete()` - without that last step a version stays `uploading` and cannot be downloaded. - `add_file` stages and hashes; the transfer happens in `complete()`, because the registry needs the full file list when the version is created. Added `staged_files`. A session that raises before `complete()` aborts in-flight uploads and removes the version it created. - Download fixed: it requested `.../versions/{v}/files/{path}`; the route is `.../versions/{v}/download/files/{path}`. - Added `vm_image` to `ModelType`; `User-Agent` reports the real package version.
Download .whlScaiLog Python 1.0.2 — SDK and agent in one wheel. Two fixes over 1.0.0: - CRITICAL: the split-topology agent (scailog-agent) no longer flattens per-entry tenants (PI was being encrypted under the agent's --tenant, making the right tenant erasure/DSAR unreachable). - The [agent] extra was missing PyYAML, so pip install scailog[agent] produced an agent that crashed on import. Fixed. Upgrade the agent: pip install "scailog[agent]==1.0.2" The agent has always been part of this package
Download .whlScaiLog Go SDK 1.0.1 — source distribution. Same SDK code as the 1.0.0 line (per-entry tenancy, _global namespace)
Download .gzScaiLog 1.0.0 — first stable release. - Per-entry tenancy: tenant is resolved per entry (explicit argument, then request context, then logger default). A process serving many tenants no longer needs a logger per tenant. - Global namespace: use the reserved tenant _global for events belonging to no tenant (bootstrap, system-wide failure). - BREAKING: the fallback to the reserved default tenant is gone. A logger with no tenant from any source now fails loudly rather than silently mislabelling every entry. Set SCAILOG_TENANT, bind per request, or pass it per call. Semantic versioning applies from 1.0.0: no breaking change before 2.0.0. The Go archive is source-only
Download .nupkgScaiLog 1.0.0 — first stable release. - Per-entry tenancy: tenant is resolved per entry (explicit argument, then request context, then logger default). A process serving many tenants no longer needs a logger per tenant. - Global namespace: use the reserved tenant _global for events belonging to no tenant (bootstrap, system-wide failure). - BREAKING: the fallback to the reserved default tenant is gone. A logger with no tenant from any source now fails loudly rather than silently mislabelling every entry. Set SCAILOG_TENANT, bind per request, or pass it per call. Semantic versioning applies from 1.0.0: no breaking change before 2.0.0. The Go archive is source-only
Download .tgzScaiScribe SDK — v0.1.1 alpha. See https://www.scailabs.ai/docs/scaiscribe/changelog
Download .tgzScaiScribe SDK — v0.1.1 alpha. See https://www.scailabs.ai/docs/scaiscribe/changelog
Download .nupkgScaiScribe SDK — v0.1.1 alpha. See https://www.scailabs.ai/docs/scaiscribe/changelog
Download .whlOfficial .NET client for ScaiGrid, targeting .NET 8 LTS. 0.2.0 adds the ScaiEcho sub-client — client.ScaiEcho.AnalyzeAsync for batch pyannote analysis and client.ScaiEcho.DiarizeStreamAsync for standalone real-time diarization. Streaming via IAsyncEnumerable of DiarizeSegment using the built-in System.Net.WebSockets.ClientWebSocket, no extra dependencies. Both bearer-header and bearer-subprotocol WebSocket auth. Backfills Transcribe and Speakers CRUD. MIT.
Download .nupkgOfficial TypeScript and JavaScript client for ScaiGrid. 0.2.0 adds the ScaiEcho sub-client — client.scaiecho.analyze() for batch pyannote analysis and client.scaiecho.diarizeStream() for standalone real-time diarization. Streaming uses the platform WebSocket — native on Node 22+ and all browsers, install ws on older Node. Both bearer-header and bearer-subprotocol auth modes. Backfills transcribe and speakers CRUD. ESM and CommonJS bundles, MIT.
Download .tgzOfficial Python client for ScaiGrid. 0.2.0 adds first-class ScaiEcho support — client.scaiecho.analyze() for batch pyannote analysis and client.scaiecho.diarize_stream() for standalone real-time diarization. Sync and async clients sharing one surface. Streaming uses the optional websockets library, install with pip install scailabs-scaigrid[ws]. Both bearer-header and bearer-subprotocol WebSocket auth modes. Backfills transcribe and speakers CRUD. Python 3.10+, MIT.
Download .whlOfficial Python client for ScaiDrive. Async-first (httpx) with a sync wrapper sharing the same surface. Resumable uploads with streaming sha256, Range downloads with local hash verification. 95 methods across 9 resources, Python 3.10+.
Download .whlOfficial TypeScript and JavaScript client for ScaiDrive. Async, fetch-based, ESM + CJS bundles with .d.ts, Node 18+. Resumable uploads with content_sha256 verification, Range-aware streaming downloads, X-Content-SHA256 + ETag integrity. 95 methods across 9 resources (files, folders, shares, external links, permissions, quotas, search, sync, users).
Download .tgzOfficial .NET client for ScaiDrive targeting .NET 8 LTS. Async-first throughout with CancellationToken on every method. Resumable uploads with content_sha256, Range downloads with X-Content-SHA256 integrity. Constructor overloads for owned-HttpClient and IHttpClientFactory injection. 95 methods across 9 resources.
Download .nupkg**ScaiDNS SDK v0.1.0** — first published release. Resource coverage (all three SDKs at parity): - Domains, Records, Reverse Zones, DNSSEC, Templates - Import / Export (incl. multipart file upload) - API Keys, Access Grants, Roles - Users, Groups, Admin (platform config, tenants, audit logs, stats, sync status) - Me / auth context See the API reference at https://scailabs.ai/docs/scaidns/reference for the full endpoint inventory.
Download .whl**ScaiDNS SDK v0.1.0** — first published release. Resource coverage (all three SDKs at parity): - Domains, Records, Reverse Zones, DNSSEC, Templates - Import / Export (incl. multipart file upload) - API Keys, Access Grants, Roles - Users, Groups, Admin (platform config, tenants, audit logs, stats, sync status) - Me / auth context See the API reference at https://scailabs.ai/docs/scaidns/reference for the full endpoint inventory.
Download .tgz**ScaiDNS SDK v0.1.0** — first published release. Resource coverage (all three SDKs at parity): - Domains, Records, Reverse Zones, DNSSEC, Templates - Import / Export (incl. multipart file upload) - API Keys, Access Grants, Roles - Users, Groups, Admin (platform config, tenants, audit logs, stats, sync status) - Me / auth context See the API reference at https://scailabs.ai/docs/scaidns/reference for the full endpoint inventory.
Download .nupkgInitial public release of the ScaiSend SDK. - All 19 endpoints covered: mail send, full template CRUD with versions, bounce / spam / global / group suppression management. - Built-in retry on 429 and 5xx with exponential backoff + jitter
Download .tgzInitial public release of the ScaiSend SDK. - All 19 endpoints covered: mail send, full template CRUD with versions, bounce / spam / global / group suppression management. - Built-in retry on 429 and 5xx with exponential backoff + jitter
Download .whlInitial public release of the ScaiSend SDK. - All 19 endpoints covered: mail send, full template CRUD with versions, bounce / spam / global / group suppression management. - Built-in retry on 429 and 5xx with exponential backoff + jitter
Download .nupkgOfficial Python SDK 1.0 — full backend coverage. Sync + async clients. Typed errors. CLI.
Download .whlOfficial TypeScript/JavaScript SDK 1.0 — works in Node 18+ and modern browsers. ESM + CJS builds, full type definitions, fetch-based.
Download .tgzOfficial .NET SDK 1.0 — targets .NET 8. HttpClient-based, thread-safe, System.Text.Json with records.
Download .nupkgScaiLabs software is dual-licensed. Pick the option that fits your situation.
Which license applies to your use case, and how the dual licensing works. View · Download .md
Default free-use license. Source-available with copyleft-style obligations for derivative works and services. View · Download .md
For organisations that need to ship ScaiLabs software in closed-source products or as part of a commercial service. View · Download .md
Questions about which license applies to your situation? Reach out at licensing@scailabs.ai.
Can’t find what you’re looking for? Our team can help with custom integrations, deployment guidance, and technical support.
Get in Touch →