- Jobs and runs. Trigger work over HTTP or a connected worker, then watch each run move from
queuedtocompleted, or todead_letterwhen its retries run out, in a live dashboard. - Your code, your infrastructure. Strait never runs your code itself. It reaches the endpoint you expose over HTTP, or a long-lived worker you connect over gRPC, and streams the results back.
- Workflows. Compose multi-step workflows with branching, parallel steps, sub-workflows, human approval gates, and compensation steps that roll back partial work when something fails.
- Durable execution. Workflows survive process restarts and multi-day sleeps, with checkpoints, expected-completion tracking, and stage notifications.
- Retries and resilience. Exponential, linear, fixed, or custom backoff with jitter, per-endpoint circuit breakers, and adaptive concurrency that backs off under load.
- Scheduling and events. Cron schedules with timezone support, plus event triggers and inbound event sources that start work when something happens elsewhere.
- Failure recovery. Inspect a failed run, fix the cause, and replay it. Dead-letter runs are kept for review instead of silently dropped.
- Observability built in. OpenTelemetry traces, Prometheus metrics, structured logs, and real-time SSE streaming, with optional ClickHouse analytics, audit logs, and log drains.
- SDKs and tooling. Official SDKs for TypeScript, Python, Go, Ruby, and Rust with the same feature set on each, plus a CLI and an MCP server.
- Cloud or community self-hosting. Start on Strait Cloud for the shortest production path, or run the community stack yourself when you need local evaluation, residency control, or air-gapped operation.
Get Started
Strait Cloud
Use Strait Cloud when you want the fastest path to a production job. Strait operates the API, scheduler, worker plane, storage, upgrades, and billing controls.
- Sign in at app.strait.dev.
- Create an organization and project.
- Create a project API key.
- Follow the Cloud quickstart to create a job and trigger a run.
export STRAIT_BASE_URL=https://api.strait.dev
export STRAIT_API_KEY=strait_replace_with_your_key
export STRAIT_PROJECT_ID=proj_replace_with_your_project_id
Community Self-Host
Use community self-hosting when you need local evaluation, compliance controls, residency control, or full ownership of the runtime.
Prerequisites: Docker with Compose v2, Git, and a POSIX shell.
git clone https://github.com/strait-dev/strait.git
cd strait
make selfhost
That starts the Strait API, dashboard, PostgreSQL, Redis, and Sequin on your machine. Open http://localhost:3000, sign up, and create your first job. Everything runs locally, with no Stripe, billing, or hosted Strait account required.
Full walkthrough and hardening guide: SELFHOST.md.
Deploy The Dashboard Separately
The dashboard supports a portable Node/Docker target and a managed Vercel target. Full walkthrough: apps/app/README.md.
Cloud Runtime Environment
Hosted Strait uses Infisical as the source of truth for runtime environment
variables. Keep the dev, staging, and prod Infisical environments in
sync with the variables documented in Environment Variables.
Go-triggered email delivery depends on both services:
APP_INTERNAL_URL points the Go service at the dashboard's internal
transactional email endpoint. INTERNAL_SECRET must be the same value for the
Go service and dashboard in each environment.
What you get
Cloud is the default hosted product. Community self-hosting runs the open-source edition. Billing is compiled out of the community dashboard image, so there is no Stripe connection, plan limit, or upgrade screen, and your data and users stay on your infrastructure.
Documentation
Dedicated repositories:
Repository layout
Turborepo monorepo managed with Bun. The bits that matter:
apps/
strait/ Go service. API, worker, scheduler, all in one binary.
app/ TanStack Start dashboard (React 19, Vite).
docs/ Mintlify docs.
packages/ Shared TS workspaces (billing, config, transactional) plus repo config and ops helpers (configs, monitoring, scripts). The @strait/ui component library ships as an external npm package.
docker-compose.base.yml Shared runtime stack.
apps/strait/docker-compose.yml Dev dependency ports (Postgres 15432, Redis 16379).
docker-compose.selfhost.yml Self-host overrides and dashboard profile.
SELFHOST.md Self-host walkthrough.
AGENTS.md Contributor operating guide.
Install and run workspace tasks:
bun install
bun run lint
bun run test
bun run build
Development Checks
Run source-backed documentation checks before committing Markdown changes:
bun run --cwd apps/docs lint
Run OpenAPI route parity before committing API changes:
cd apps/strait && go run ./scripts/check-openapi-parity
Run hooks:
lefthook run pre-commit
See AGENTS.md for the full contributor guide: tech stack, module layout, coding conventions, testing patterns, and repository workflow.
Support And Security
Use GitHub Discussions for questions, setup help, and design discussion. Use GitHub Issues for reproducible bugs and public feature requests.
Do not open public issues for vulnerabilities, exposed credentials, or reports that include private data. Email security reports to [email protected]. See SECURITY.md for the disclosure process and response targets.
Cloud customers should use their contracted support channel for production incidents and account-specific help.
