143 | Self-hosting | 143.dev docs

Start with a single-node 143 instance, then harden the deployment before routing real coding-agent work.

The fastest supported self-hosting path is the single-node quickstart. It runs the production-shaped stack on one Linux host so you can validate GitHub, migrations, API/frontend health, worker loops, sandbox runtime, previews, and provider credentials before splitting capacity across dedicated hosts.

Use the other pages in this section to fill in required credentials and production checks around that quickstart.

Quickstart

Quickstart: single-node

Bring up Caddy, frontend, API, worker loops, Postgres, Redis, Chrome, sandbox DNS, and sandboxes on one host.

GitHub App setup

Create the GitHub App used for repo access and PR creation.

Platform LLM

Configure the LLM used for platform reasoning and classification.

Deployment checklist

Verify production readiness before real agent work.

Worker capacity

Size worker process and sandbox concurrency.

Quickstart flow

Prepare DNS, GitHub App credentials, LLM/provider keys, and access to the runtime images.

Copy .env.single-node.example, fill in the required values, and choose an IMAGE_TAG.

Run sudo deploy/scripts/prepare-single-node.sh on the host, then start the stack with make single-node-up.

Run the production checklist before allowing real repositories or automations to depend on the instance.

Operating responsibilities

Self-hosted operators own:

Secrets and encrypted environment management.
GitHub App credentials and callback URLs.
Database backups and migrations.
Worker host capacity and sandbox runtime health.
Log retention and production debugging access.
Provider credentials for platform LLM and coding-agent execution.

Self-hosting