Skip to main content
The Verglas SDKs expose the same endpoint contract against a local server and Verglas Cloud. A worker receives a connected client. A standalone application connects with an endpoint and bearer token.
The SDK packages are private workspace packages in the current prototype. Install them from this repository until published packages become available.

​
Choose an SDK

TypeScript

Use the fetch-only client and defineWorker contract in Bun, Node.js, and edge runtimes.

Rust

Use streaming Arrow reads and writes, exact table definitions, commit following, and the native worker trait.

​
Shared capabilities

​
Endpoint model

The SDK separates three destinations:
  • The Verglas endpoint handles query and logical write execution.
  • The Iceberg REST catalog handles table metadata and table creation.
  • The S3-compatible cache endpoint handles object bytes.
Local clients can discover the catalog and S3 endpoint from the server. Cloud runtimes receive all connection values from the platform.

​
Authentication

Do not hard-code a token. Workers receive a connected client and secret bindings through their context. Standalone applications read VERGLAS_ENDPOINT and VERGLAS_TOKEN from their environment.
The control-plane token written by verglas login manages tenant resources. A worker runtime receives a separate, scoped data-plane token for its table grants.