Deployment overview
This guide helps you choose the right deployment method for your use case. Before selecting a deployment option, it’s useful to understand the core components that make up an Obot installation:
- Obot Server: The core application server, distributed as a container image.
- MCP Server Hosting Platform: The environment where Obot deploys users’ MCP servers. This matches the platform on which Obot itself is deployed (Docker or Kubernetes).
- PostgreSQL Database: The primary database for Obot. PostgreSQL 17+ is required.
Below you’ll find an overview of the available deployment options, along with system requirements and links to reference architectures.
Docker Deployment
Docker provides the fastest way to get Obot running on your local machine or a single server for development, testing, and proof-of-concept use cases.
- Simple setup using
docker run - Includes a built-in PostgreSQL database and local file storage
- Deploys MCP servers as Docker containers using the host’s Docker socket
For more details, see the Docker Deployment Guide.
Kubernetes Deployment
Kubernetes provides the best way to run Obot reliably at scale in production environments.
- Helm chart available at charts.obot.ai
- Integrates with cloud-native services such as KMS
- Requires an external PostgreSQL database; configure file storage for the features you enable
For more details, see the Kubernetes Deployment Guide.
Production System Requirements
For production deployments, the following components are required:
- Kubernetes: A production-grade Kubernetes cluster with capacity for Obot and the MCP servers it will manage
- External PostgreSQL database: PostgreSQL 17+
- Encryption provider: AWS KMS, Google Cloud KMS, or Azure Key Vault
- Authentication provider: See our supported Authentication Providers
- TLS/SSL certificates: For secure HTTPS access
- Backup strategy: Regular backups for the database and any file or object storage in use
Cloud Platform Reference Architectures
If you plan to deploy Obot on a managed Kubernetes service, these reference architectures provide infrastructure guidance and best practices:
Next Steps
- Choose a deployment method above
- Follow the corresponding deployment guide
- Set up the local Obot CLI
- Configure authentication
- Set up model providers
- Review the server configuration options
Getting Help
- See the FAQ