AgentRail is a local-first product. You can run the full lifecycle API on your own machine, a VPS, or any Linux server you control — without a hosted account. Self-hosting gives you full control over your data, credentials, and runtime environment.Documentation Index
Fetch the complete documentation index at: https://agentrail.app/docs/llms.txt
Use this file to discover all available pages before exploring further.
What self-hosting includes
When you self-host AgentRail using the source-available runtime, you get:- The local API server (
agentrail server start) that serves tasks, events, CI status, review feedback, and ship operations - The full task lifecycle API and SDKs
- Local event streaming and webhook primitives
- Adapter interfaces for GitHub, CircleCI, and Linear using your own credentials
- CLI-managed setup for agents, routing rules, and provider state
What self-hosting does not include
Self-hosting is a single-instance runtime. It is not the same as the planned AgentRail Cloud team control plane. The following capabilities are Cloud-only and are not part of the self-hosted runtime:- Managed provider connectors — AgentRail Cloud operates credential storage, OAuth apps, webhook verification, retries, and backfills on your behalf. In self-hosted mode, you supply your own tokens and manage your own webhook exposure.
- Durable shared run history — Cloud persists routing decisions, run history, event cursors, and audit logs across your team. Self-hosted setups store state locally on the machine running the server.
- SSO, RBAC, and SCIM — Access control and identity federation are Cloud features.
- Fleet routing and dashboards — Multi-agent assignment, capacity management, and operational dashboards are Cloud features.
- Support and compliance — SLA coverage, SOC 2 evidence, incident response, and backup guarantees are Cloud features.
Deploying AgentRail on a VPS with Docker is self-hosting, not a Cloud-equivalent team control plane. See the AgentRail Cloud section below for details on what is and is not included.
Two setup paths
There are two ways to get AgentRail running on your own infrastructure:- CLI-managed setup (recommended)
- Docker (server only)
The CLI-managed path is the recommended way to self-host AgentRail. It handles routing configuration, provider state, and agent credentials through interactive setup commands.This writes local config to
Run init
~/.agentrail/, creates operator bootstrap state, and can create your first agent profile interactively. Choose your routing mode (rules_only or ai_assist) and GitHub review policy when prompted.Start the server
Keep this running in one terminal:The server starts the AgentRail API, begins provider delivery for configured polling or webhooks, and keeps managed agents awake.
Create your first agent
In a second terminal, if This creates scoped agent credentials, writes
agentrail init did not already create one:~/.agentrail/agent.env, and sets up starter routing for your repo..png?fit=max&auto=format&n=TNCV8lxzL1ij3U4N&q=85&s=7345b71aa1c450c74f35b67c2655fc43)