Self-Hosting

Self-hosting means running the AgentRQ server on your own infrastructure rather than using the hosted service at agentrq.com. Since AgentRQ is open-source under the Apache-2.0 license, you can deploy it anywhere — your own servers, cloud VMs, Kubernetes clusters, or on-premises hardware.

Why Self-Host?

Reason	Description
Data sovereignty	Task data and agent messages stay within your infrastructure
Compliance	Meet regulatory requirements (HIPAA, SOC 2, GDPR) that prohibit external data processors
Custom integrations	Extend AgentRQ with internal tools, SSO providers, or proprietary data sources
Cost control	Eliminate per-seat or usage-based pricing at scale
Air-gapped environments	Run agents in networks with no external internet access

What You Get with Self-Hosting

When you self-host AgentRQ, you run the same server that powers the hosted version:

→ Full task board and workspace management
→ MCP server compatible with Claude Code
→ Real-time notifications via SSE
→ Bidirectional messaging between agents and humans
→ Attachment support

Getting Started

bash

# Clone the repository
git clone https://github.com/agentrq/agentrq

# Configure your environment
cp .env.example .env

# Start with Docker Compose
docker compose up -d

Once running, point your Claude Code MCP config to your self-hosted instance instead of mcp.agentrq.com.

Hosted vs. Self-Hosted

Feature	Hosted	Self-Hosted
Setup time	60 seconds	15-30 minutes
Data location	AgentRQ cloud	Your infrastructure
Maintenance	Managed	Self-managed
Custom integrations	Limited	Unlimited
Cost	Per workspace	Infrastructure only