drift Docs
Start
What is Drift?
The tour, if you are new here.
Use cases
Whether Drift does your thing.
Getting started
Nothing to deployed, in one command.
Architecture
How a slice is put together.
What it costs
The free grant, four unit prices, two rules.
Build
Canvas
Static sites, same origin as your API.
Tools
Operate
Auth
Route gates, API keys and your account.
Security
Boundaries, sandboxing and hardening.
Troubleshooting
Error codes
What went wrong, and what to do about it.
Legal
Acceptable use
What a slice may not be used for.
Data processing
The DPA, and every sub-processor.

CLI Reference

One page per noun, each with every verb, flag and output it carries. The binary's own three commands (drift, --version and upgrade) are on the CLI overview.

The commands

Session

Your login lives in ~/.drift/session.json, one profile per account you're logged in to, each with its own active slice, so switching accounts with drift account use never points a second account at the first one's slice. Every authenticated request carries:

  • Authorization: Bearer <jwt>, your identity
  • X-Slice: <active-slice>, the target slice

Tokens are refreshed automatically on a 401 that means the session expired. If the refresh fails, you're prompted to log in again. Account has the file's shape and how to work as more than one account, and Authentication has the token lifetimes.

Bare drift opens the terminal dashboard.

It runs over the same data with slices down the side, and Atomic / Backbone / Canvas panes for browsing functions, documents and sites.