Use self-hosting when the work needs a shared control plane.

Who this is for

This path is for developers who already understand the local workflow and now need shared coordination, shared review and policy visibility, or team-visible execution state.

What changes from local-only

• The workflow gains a shared authority surface.
• Review and policy state become team-visible.
• Async worker-backed execution becomes available.
• Deployment and compatibility decisions now matter.

What to read first

1. Local Quickstart
2. Workflow Doctrine
3. Self-Hosted Team Deployment
4. Compatibility Matrix
5. Package Targets

Deployment posture

The first goal of this page is clarity, not automation theater. Explain the shared path, the prerequisites, the boundaries, and the supported deployment combinations before promising speed.

What this page should not do

• It should not replace the deployment guide.
• It should not pretend self-hosting is the default first-run path.
• It should not collapse the public website and authenticated app into one thing.
• It should not hide compatibility or package boundaries.