Thyme Products

Thyme separates authoring an automation task, running it, accessing a blockchain, and paying for gas. You can use the products together or integrate the services your application needs.

Product	What it does	Start here
Flow	Stores immutable function releases, provisions execution environments, runs schedules, and tracks execution results.	Quickstart
SDK	`@thyme-labs/sdk` defines typed tasks, call descriptors, lifecycle hooks, and task context.	SDK reference
CLI	`@thyme-labs/cli` scaffolds, runs locally, uploads releases, and manages Flow resources from scripts.	CLI reference
Lift	Sponsors supported account-abstraction operations under integration policies and budgets.	Lift quickstart
Gate	Gives applications authenticated access to available blockchain RPC endpoints.	Gate quickstart

A Flow execution

SDK task → local CLI run → uploaded function release
                                  ↓
                  executable = release + profile + args
                             + secrets + schedule + gas mode
                                  ↓
                    task reads the chain and returns calls
                                  ↓
                 profile permissions and gas policy apply
                                  ↓
                    submission → receipt → lifecycle hook

The task returns what to call. Flow selects where and how to execute from the executable configuration. A read through an RPC endpoint is not a transaction; a successful task run is not yet an on-chain confirmation. See Tasks, Functions & Executables.

For supported Roles profiles, Flow uses managed Lift sponsorship. Applications integrating Lift directly manage their own integration, keys, policies, and supported smart account. These are different setup paths: follow Flow + Lift or direct Lift integration.

Credentials are specific to each service

Credential	Where it is used	What it does not grant
Flow management credential	CLI management commands and `/api/v1`	Lift integration access, Gate RPC access, or wallet ownership
Flow upload credential	Uploading a task bundle with sufficient scope	Every management operation unless its scopes allow them
Lift integration key	Lift JSON-RPC requests for an integration	Access to Flow management resources
Gate RPC key	Endpoints shown for that key in the Gate Console	Flow management or Lift sponsorship
Executable webhook URL	Invoking that executable's configured webhook	General management access
Owner wallet signature	On-chain account and role configuration	An API login session

Use the right credential for each endpoint. Keep bearer keys and webhook URLs out of source control, screenshots, and shared logs. A workspace role and a task's on-chain permissions are separate controls.

Development environments and availability

Select the intended deployment before authenticating or uploading. A development Console, API, Lift integration, and Gate key must be configured for that environment. Available chains, runtime backends, profile kinds, and sponsorship support are deployment-specific; a chain listed in Gate does not automatically have Lift sponsorship or support every Flow profile kind.

These docs describe SDK 0.8.0, CLI 0.10.0, and the current application source. Package names, API routes, and some Console labels still use functions; use those literal names when copying commands. In prose, Flow is the product name.

Pick a workflow

Build an automation: first task, scheduling, and monitoring.
Integrate an existing deployment: management API, management CLI, and CI.
Review execution access: profiles, permission manifests, and Roles verification.
Manage releases safely: release management and migration guide.
Sponsor your app's transactions: Lift API and policies.
Connect to chain data: Gate endpoints and usage.