Quick Decision
Use Cloud if you want Greptile running in minutes with zero infrastructure management. Use Self-Hosted if you need data sovereignty, air-gapped environments, or custom LLM providers. For self-hosted, choose based on team size:- Docker Compose: Up to 100 developers. Single VM, simpler operations.
- Kubernetes: 100+ developers. Horizontal scaling, high availability.
Self-Hosted: Docker Compose
Runs all services on a single Linux VM using Docker Compose.Two Setup Paths
AWS with Terraform — If you’re on AWS and want automated provisioning:- Terraform creates VPC, EC2, RDS PostgreSQL, ElastiCache Redis
- Bootstraps the EC2 with Docker Compose and starts Greptile
- Single
terraform applygets you running - Go to AWS Terraform guide →
- You provision a Linux VM and any external databases
- Clone the repo, configure
.env, run Docker Compose - Works anywhere Docker runs
- Go to Manual Setup guide →
Requirements
VM Sizing:
Software: Linux (Ubuntu 20.04+, Amazon Linux 2023), Docker 23.x+, Docker Compose v2.5+
Network: Inbound access on port 3007 for SCM webhooks. Outbound HTTPS to LLM and SCM providers.
Self-Hosted: Kubernetes
Runs services across a Kubernetes cluster using Helm charts. Provides horizontal scaling, rolling updates, and high availability.Requirements
Cluster: Kubernetes 1.21+ (1.25+ recommended), Helm 3.0+ External Services: PostgreSQL with pgvector (RDS recommended), Redis (ElastiCache recommended) Sizing:
Go to Kubernetes guide →
External Dependencies
All self-hosted deployments require:LLM Providers
You need three model types configured:
Supported providers: OpenAI, Anthropic, AWS Bedrock, Azure OpenAI, GCP Vertex AI.