Operator tooling for Drift

Drift CLI

Tenant-scoped administration and recovery through explicit commands—without hand-built JSON, fragile curl workflows, or shortcuts around Drift authorization.

Start with the tutorial See the commands

Focused by design

Administrative work, kept inside the boundary

Drift remains authoritative for behavior, authorization, tenancy, and persistence. The CLI makes its supported operator workflows easier to invoke and automate.

Tenant-scoped keys

List, create, revoke, and rotate credentials inside the tenant established by the supplied admin key.

Known-ID recovery

Inspect and restore soft-deleted vertices or edges while preserving Drift version checks.

Automation-ready output

Use stable JSON envelopes, documented exit codes, and credential-safe configuration in scripts and CI.

Why it exists

An HTTP client, not a privileged backdoor

Drift CLI replaces ad hoc administrative requests while preserving the same API contracts, tenant context, key scopes, and optimistic-concurrency rules as every other Drift client.

Guides & reference

Choose your path

Learn a workflow, solve a task, inspect a contract, or understand a boundary.

Tutorial

Build the CLI and administer an existing Drift tenant from the ground up.

Open tutorial

How-to

Configure access, manage keys, recover records, and use JSON output.

Open how-to

Explanation

Understand client boundaries, credentials, and Drift tenant administration.

Open explanation

Reference

Check exact commands, configuration, environment variables, and exit codes.

Open reference

Where it fits

The places operators already work

Local terminals

Replace hand-built administrative requests with explicit, discoverable commands.

CI automation

Use machine-readable output and coarse exit codes without placing secrets in arguments.

Operational runbooks

Keep sensitive key and recovery actions reviewable, repeatable, and tenant-bound.