Quickstart: hosted platform

This walks through taking a team repo — the same one from the local quickstart — into production.

1. Sign in

Sign in to app.runravel.ai with SSO.

2. Connect a repo

Install the Ravel GitHub App and pick the repo and branch that define your team. Ravel checks out that commit into an isolated worktree — never your live checkout — and validates the config exactly the way ravel validate does locally. Nothing activates until validation passes.

3. Configure trust

Before the first deploy goes live:

• Bind secrets — for every secret your agents’ tools.json or plugin.ts declares, bind a value scoped to the team (and, if you need different values for different agents, to the specific agent). See Secrets.
• Set a spend ceiling — a daily dollar cap for the team. See Spend governance.
• Grant access — give your people a role: viewer, operator, or owner. See Identity & access.

4. Deploy

Deploying activates the worker: an isolated container running your team, reachable at a subdomain. The deploy pipeline goes through the same stages either way — fetch → build → env-check → activate — and you can watch it happen live from the console.

After activation, the platform waits through a health-check probation window. If the new worker doesn’t come up healthy, it’s rolled back to the last good commit automatically — a bad deploy can’t take a running team down.

5. Redeploy

git push

A push to the connected branch fires a webhook, and the same validate-then-activate pipeline runs again. Config-only changes hot-reload the worker; changes to dependencies or secrets restart it. Either way, state persists across the redeploy.

Next

• Connect a repo — the deploy pipeline in more detail
• Identity & access
• Secrets