Drift · SDK

drift Docs

Start

The tour, if you are new here.

The case for a smaller cloud.

Getting started

Nothing to deployed, in one command.

How a slice is put together.

The free grant, five unit prices, two rules.

Build

Serverless functions.

Write a function

The handler shape, and what you pay for.

Trigger, route, auth and secrets on one line.

Go, Python, Node, Ruby, PHP, Rust.

Runtime versions

Which interpreter version your function runs on.

The auth= gate, and per-route API keys.

Request headers

What reaches your handler, and what does not.

Queue-triggered and scheduled functions.

SSE and WebSocket from one function.

Outbound egress

What a slice may dial.

Limits and alerts

Timeout, memory and rate, and being told.

One language, one manifest, many functions.

The CLI surface

Every drift atomic command.

Secrets, data, blobs, queues.

JSON collections, upserted on _id.

Per-slice SQLite, with transactions.

Files and uploads, organised by bucket.

Encrypted config a function declares.

FIFO messages that trigger functions.

Key/value strings with a TTL.

Stop two workers doing one job.

In-slice pub/sub over WebSocket.

Static sites, same origin as your API.

Identity, devices and wallets.

Passwordless login with device keys.

Sign and verify with the slice's own key.

Ciphertext the slice cannot read.

Enroll a second device by attestation.

E2EE app data that follows an identity.

Tools

One binary, every noun.

The binary, and every noun.

Sign up, log in, delete.

Create, resize, snapshot, domains.

Deploy, diff, run locally.

Lint and explain a Driftfile.

One function at a time.

Reach into the data plane.

One read-only status command.

Deploy a static site.

Move off another cloud.

What bare drift opens.

Six languages, zero dependencies.

Writing a handler

Arguments, request, return.

Both namespaces, every call.

Documents, by _id or storage key.

Queries and transactions.

Strings with a TTL.

Read what the function declared.

Bytes, addressed bucket/key.

Push, and pull if you must.

A token you hand back.

Publish, and count who heard.

KeyAuth, JWT, Vault, Link, Pocket.

Logs, egress, cross-slice calls.

The same handler, six ways.

One file that describes your app.

Every top-level key, and the name rules.

A worked example

One app with every section written out.

Function limits, schedules, alerts, egress.

Collections, databases, buckets, secrets.

Sites, and the route each mounts on.

Custom hostnames the slice answers on.

One project, several slices, one file.

Lint it, hook a build on, read its errors.

Operate

Accounts, tokens and scopes.

Boundaries, sandboxing and hardening.

SDK

The Drift SDK is what your Atomic functions import to talk to the platform. It exists in six languages (Go, Python, Node.js, Ruby, PHP, and Rust) and every one exposes the same API surface, follows the same wire protocol, and gives you the same local-development experience.

The interpreted SDKs (Python, Node.js, Ruby, PHP) use only their language's standard library. The Rust SDK uses two crates (serde_json and ureq); the Go SDK uses only stdlib. No transitive dependencies, no version conflicts, no supply chain risk from us.

Where to go

Getting the SDK

Name the SDK, unversioned; never pin it.

Go and Rust provision it for you: Go's go.mod is generated and resolved at build, and a Cargo.toml is written only when your function ships none. Python, Node, Ruby and PHP expect their own manifest (requirements.txt, package.json, Gemfile, composer.json) to name it, and a function that imports the SDK without one is refused before the build with the exact line to add. Either way the version is the CLI's to resolve, not yours to pin. The table of who provides what →

Source code

All six SDKs are open source at github.com/ondrift/cloud/sdk: one repository, one release tag for all languages. Releases are tagged sdk/<version>, the CLI is tagged cli/<version> in the same repository, and both sit on the v0.1.x line while Drift is in closed alpha.