Self-Hosting Overview
Complete guide to deploying Greptile infrastructure on-premises
This section provides comprehensive guides for self-hosting Greptile using the akupara repository. We offer two primary methods of deployment: docker-compose and kubernetes. We strongly recommend using the docker-compose method as it is simpler and more flexible.
The akupara repository contains all the infrastructure code and deployment guides for running Greptile on-premises. Make sure to download the latest release from GitHub.
Deployment Options
Docker Compose
Recommended approach - Simple and flexible deployment using Docker Compose
Kubernetes
Enterprise-grade deployment using Kubernetes with Helm charts
Architecture Overview
Docker Compose Architecture
The docker-compose deployment provides a streamlined architecture suitable for most on-premises deployments:
Kubernetes Architecture
The Kubernetes deployment offers a more complex but scalable architecture:
Getting Started
Choose your deployment method:
- For most users: Start with Docker Compose Deployment
- For enterprise environments: Consider Kubernetes Deployment
Prerequisites
General Requirements
- Access to the akupara repository
- Linux-based deployment environment
- Network access for pulling Docker images
- SSL certificates for HTTPS endpoints
Docker Compose Requirements
- Docker and Docker Compose installed
- Minimum 8GB RAM, 4 CPU cores
- 100GB+ available disk space
Kubernetes Requirements
terraform,helm, andkubectlinstalled- For AWS deployments:
awscliwith appropriate credentials - Access to a Kubernetes cluster (EKS, GKE, AKS, or self-managed)
Support
For additional support with self-hosting:
- Review the detailed deployment guides in this section
- Check the akupara repository for the latest updates
- Contact our engineering team for enterprise support
Self-hosting requires an enterprise license. Contact sales@greptile.com for licensing information.