Get started

Start with a guide

Each guide takes you from an empty server to an agent your team uses every day, with every setting along the way.

• Checkout p99 high Cache key misses PR #412 merged
  Guide · Chat & Responses Set up incident response Run Ryph with Docker Compose and put an agent on call. An alert fires, the agent investigates in Discord, Slack, Telegram or Zulip with your team, and proposes a fix as a pull request.

• Run 7f3a patch +12 −3

  Keys
  Guide · Secure forge interactions Give your team a secure agent Put an agent in your company chat that answers questions about your code, fixes what people report and builds reports from your data. It can't push to main, so every change waits for your team's review.

Choose where Ryph runs

To set Ryph up your own way, pick where it runs. Ryph runs the same everywhere, from one binary on your laptop to a cluster for your whole team. Each page takes you from nothing to an agent working on your code.

• curl … | sh 3 questions Run 7f3a
  On your machine Try Ryph with one command. It runs while your laptop does. Setup: One command
• docker compose up ryph postgres Run 7f3a, via the launcher
  Docker Compose One server you keep running: a NAS, a homelab box or a VPS. Setup: One compose file: Ryph, a launcher and Postgres
• appcontrol-planeforgemcp-gatewaylaunchermodel-proxymemorypostgreshistorian
  Networked Compose Every service in its own container, on one machine. Setup: One compose file, a dozen services and their secrets
• helm install ryph Services, one pod each Run Policies
  Kubernetes For teams: sandboxed runs, network policies and room to grow. Setup: A cluster, Postgres and object storage, then one helm install

Not sure which fits? Choose a deployment compares them side by side.