Self-Hosting Overview
Overview of self-hosting Optima Forge.
Self-Hosting Overview
Optima Forge can be self-hosted on your own infrastructure for full data control, compliance requirements, or air-gapped environments. The platform is licensed under BSL 1.1.
Deployment Options
- Oracle Cloud ARM64 (Recommended): The golden path deployment using Oracle A1 Flex instances with PM2 and Cloudflare Tunnel. Best performance-to-cost ratio.
- Docker Compose: Full stack deployment with all sidecars. Best for local development and testing.
- Kubernetes: Enterprise-grade deployment with Helm charts for production clusters.
Infrastructure Requirements
- Minimum: 4 CPU cores, 16GB RAM, 50GB storage
- Recommended: 8 CPU cores, 48GB RAM, 200GB storage (Oracle A1 Flex)
- Docker + Docker Compose for sidecars
- Node.js 20+ runtime
- 15 Docker sidecar services (Redis, NATS, Neo4j, Qdrant, SpiceDB, OPA, Langfuse, etc.)
Sidecar Services
Forge requires several supporting services running as Docker containers:
- Redis (memory state, caching, queues)
- NATS JetStream (agent coordination, pub/sub)
- Neo4j (graph memory)
- Qdrant (vector memory)
- SpiceDB (permissions)
- OPA (policy engine)
- Langfuse (tracing)
- SearXNG (web search)
- Presidio (PII detection)
- LLM Guard (security scanning)
Database
Forge uses Turso/libSQL as its primary database with embedded replicas for low-latency reads. WAL replication via Litestream sends data to S3-compatible storage (Cloudflare R2 for production, OCI Object Storage for development).