Skip to main content

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

ComponentSelf-HostableDescription
AIP HubYesContext storage, sessions, invocation routing
Intelligence PipelineYesAuto-tagging, embeddings, search
Agent MeshYesDiscovery, delegation, trust config
SandboxesNoUse RunTools Cloud
Code ExecutionNoUse RunTools Cloud
TemplatesNoUse 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
Recommended (production):
  • 4+ vCPU, 8GB+ RAM
  • Managed PostgreSQL (RDS, Cloud SQL)
  • Redis for caching
  • S3-compatible storage for embeddings

Quick Start

# Clone the AIP Hub repo
git clone https://github.com/runtools/aip-hub
cd aip-hub

# Configure
cp .env.example .env
# Edit .env with your database and auth settings

# Deploy
docker compose up -d

Configuration

# Required
DATABASE_URL=postgres://user:pass@localhost:5432/aip
JWT_SECRET=your-secret-key

# Optional
REDIS_URL=redis://localhost:6379
OPENAI_API_KEY=sk-...           # For embeddings
EMBEDDING_MODEL=text-embedding-3-small
AUTH_PROVIDER=oidc              # or saml, ldap
OIDC_ISSUER=https://auth.company.com

Connecting to RunTools Cloud

Self-hosted AIP Hub connects to RunTools Cloud for agent execution:
import { AIPHub } from '@aip/client';

const hub = new AIPHub({
  // Your self-hosted hub
  endpoint: 'https://aip.your-company.com',
  apiKey: process.env.YOUR_HUB_KEY,
  
  // RunTools Cloud for agent execution
  agentProvider: {
    type: 'runtools',
    apiKey: process.env.RUNTOOLS_API_KEY,
  },
});

// Context stored on YOUR infrastructure
const session = await hub.sessions.create({ name: 'My Project' });

// Agent runs on RunTools Cloud
await hub.invoke({
  session: session.id,
  agent: 'my-deployed-agent',
  prompt: 'Build a landing page',
});

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