Overview
The AIP Hub is open source and can be self-hosted on your own infrastructure. This gives you full control over your context data, sessions, and agent invocations.Self-hosting is for the AIP Hub only. Agent sandboxes, code execution, and the RunTools platform are available exclusively via RunTools Cloud.
What You Can Self-Host
| Component | Self-Hostable | Description |
|---|---|---|
| AIP Hub | Yes | Context storage, sessions, invocation routing |
| Intelligence Pipeline | Yes | Auto-tagging, embeddings, search |
| Agent Mesh | Yes | Discovery, delegation, trust config |
| Sandboxes | No | Use RunTools Cloud |
| Code Execution | No | Use RunTools Cloud |
| Templates | No | Use RunTools Cloud |
Why Self-Host?
- Data Sovereignty — All context and conversation data stays on your infrastructure
- Compliance — Meet regulatory requirements (HIPAA, SOC2, GDPR)
- Custom Auth — Integrate with your existing identity provider (SAML, OIDC, LDAP)
- Air-Gapped — Deploy in private networks without internet access
- Unlimited Usage — No API limits on the hub itself
Deployment Options
Requirements
Minimum:- 2 vCPU, 4GB RAM
- PostgreSQL 15+
- 50GB storage
- 4+ vCPU, 8GB+ RAM
- Managed PostgreSQL (RDS, Cloud SQL)
- Redis for caching
- S3-compatible storage for embeddings
Quick Start
Configuration
Connecting to RunTools Cloud
Self-hosted AIP Hub connects to RunTools Cloud for agent execution:Hybrid Architecture
Self-hosted AIP Hub + RunTools Cloud gives you the best of both worlds:- Your data, your control — All context, sessions, preferences stored on your infrastructure
- Our compute — Agent sandboxes, code execution, and scaling handled by RunTools
- No ops burden — You don’t need to manage Firecracker, KVM, or sandbox infrastructure
Support
Community support via GitHub issues. Enterprise support available:Enterprise Support
Get dedicated support, SLAs, and migration assistance