RightSide Docs
RightSide docs

Ship past localhost.

RightSide is the agent-native deployment finishing layer. A coding agent deploys your application, receives structured failures it can act on, and stops only after it has a verified HTTPS URL.

Invite-only closed beta. Canonical RightSide control, runtime, edge, and installer services are live. Access is allowlisted and public signup is unavailable. Beta projects and data are disposable and may be erased before public beta.

Start here

The completion contract

  1. Inspect the project and confirm it can run as a bounded HTTP workload.
  2. Deploy through the RightSide CLI or MCP tool, not an improvised infrastructure shell.
  3. Read structured build, activation, and health results.
  4. Repair failures in the source when the fix is inside the project.
  5. Report success only when RightSide returns the application URL and verification succeeds.
prompt → deploy → structured failure → repair → verified HTTPS URL

One-command setup

curl -fsSL https://get.rightside.host/install | sh

The installer places the CLI and stdio MCP server under your user account, opens browser authorization, registers detected supported coding clients, and runs rightside doctor. It does not require sudo.

Installer trust. This short command trusts HTTPS and control of get.rightside.host for the bootstrap. The downloaded bootstrap verifies the immutable release payload against its manifest-pinned checksum, but the bootstrap itself is not out-of-band checksum-pinned by this one-line form.

One prompt for Claude Code or Codex

Install and set up RightSide on this machine. Verify that Node.js is 22.13 or newer and that this is Linux x64, WSL2 x64, or Apple silicon macOS. Run `curl -fsSL https://get.rightside.host/install | sh`, let me complete browser authorization, and never ask me to paste a token, device code, cookie, or secret into chat. Then run `rightside doctor --json`. If it passes, inspect this project and deploy it with RightSide. Do not claim success until RightSide returns an HTTPS URL and you verify that URL responds correctly.

Read the quickstart for supported systems and the invite-only closed-beta access boundary.