Documentation

Add an organization model credential, understand which coding harness runs, and rotate or revoke it safely.

Understand isolated workspaces, preview ports, disposable database branches, pushed changes, and cleanup.

Build an unsigned APK, let SproutOS protect the signing key, publish releases, and verify installs and updates.

Create Postgres, Valkey, OpenSearch, or object storage as a standalone resource or attach it to a project.

Return after each batch so idle connections do not keep consuming compute.

Read service usage, credit, overhead, and queue residency without hidden rounding.

Install the latest production-approved CLI, sign in, create projects, configure services, and deploy.

Give Codex, Claude Code, or another repository agent the SproutOS CLI and platform operating contract.

Use tenant-scoped credentials for Postgres, Valkey, search, and object storage.

Run production migrations from GitHub Actions before deploying every project that depends on them.

Choose a build preset, publish a finished artifact, distinguish preview from production, and verify the release.

Verify a generated hostname, activate a custom domain, and move production traffic to a known ready release.

Store secrets and public values in production, preview, development, or all targets without leaking them into source.

Use the same sprout deployment contract from GitHub Actions, a terminal, or a coding-agent harness.

Function duration, request size, memory, and concurrency.

Where repositories, deployable projects, workflows, services, and usage live.

Authorization Code with PKCE, optional database access, tokens, and revocation.

Connect ordinary S3 SDKs to mutable application storage through the SproutOS storage proxy.

Use deployment states, runtime logs, request identifiers, workflow runs, and usage records to verify real behavior.

Attach tenant-scoped search and keep index names, credentials, and application data isolated.

Understand the ownership boundary for projects, services, billing, credentials, and team permissions.

Attach a tenant-scoped Postgres database, manage connection credentials, and create disposable branches.

Map one repository or monorepo to deployable projects, workflow workers, branches, and a primary domain.

Create an organization, connect GitHub, deploy a project, attach a backend service, and verify the result.

Create a BullMQ TypeScript, BullMQ Rust, or Celery Python project for interval and webhook work.

Choose a project runtime, understand deployment overrides, and prepare arm64-compatible artifacts.

Create a repository-backed copy from a reviewed listing, complete setup inputs, and review maintenance pull requests.

Connect caches and BullMQ workers through the tenant proxy without leaving idle invocations running.

Create a definition through the API, connect one trigger to actions and controls, save versions, and inspect runs.

Decide between a repository-backed BullMQ or Celery worker and a versioned visual workflow definition.