System Requirements
Recommended Hardware
Recommended Hardware
- CPU: 2+ cores - RAM: 8GB+ - Storage: 60GB+ free space
Required Software
Required Software
- Docker (latest stable version)
- Node.js (latest LTS version)
- Yarn or NPM (latest stable version)
- Domain name or fixed IP (for external deployments)
Required Ports
Required Ports
- 3000: Kodus Web App
- 3001: API
- 3332: Webhooks
- 5672, 15672, 15692: RabbitMQ (AMQP, management, metrics)
- 3101: MCP Manager (API, metrics)
- 5432: PostgreSQL - 27017: MongoDB
Internet access is only required if you plan to connect with cloud-based Git
services like GitHub, GitLab, or Bitbucket. For self-hosted Git tools within
your network, external internet access is optional.
Domain Name Setup (Optional)
If you're planning to integrate Kodus with cloud-based Git providers (GitHub, GitLab, or Bitbucket), you'll need public-facing URLs for both the Kodus Web App and its API. This allows your server to receive webhooks for proper Code Review functionality and ensures correct application behavior. We recommend setting up two subdomains:- One for the Web Application, e.g.,
kodus-web.yourdomain.com. - One for the API, e.g.,
kodus-api.yourdomain.com.
Note: If you're only connecting to self-hosted Git tools on your network and do not require public access or webhooks, you might be able to use a simpler setup, but this guide focuses on public-facing deployments.
Setup
1
Clone the installer repository
2
Copy the example environment file
3
Generate secure keys for the required environment variables
4
Edit the environment file
Edit See Environment Variables Configuration for detailed instructions.
.env with your values using your preferred text editor.5
Run the installer
6
Success 🎉
When complete, Kodus Services should be running on your machine.
You can verify your installation using the following script:
7
Access the web interface
Once you access the web interface for the first time, you'll need to:
- Create your admin account - This will be the first user with full system access
- Configure your Git provider - Connect GitHub, GitLab, or Bitbucket following the on-screen instructions
- Select repositories for analysis - Choose which code repositories Kody will review
For detailed steps on the initial configuration process, refer to our Getting
Started Guide.
Environment Variables Configuration
Use this section to fill your.env. Start with the public URLs, then set up
databases and RabbitMQ, and finally add provider-specific settings.
Namespace Configuration
These settings define the public URLs and host binding used by the web app and API. If you are not using MCP Manager, you can skip the MCP entries here and the full block below.LLM Provider Configuration
Database configuration
Use local containers for Postgres and MongoDB by default. Update credentials to match your security requirements.RabbitMQ configuration
RabbitMQ is required in 2.0. Keep the URI in sync with the values below.Git Provider Configuration
Choose and configure your preferred Git provider. You can set one or more providers; for basic token-based authentication, you only need the webhook URL.- Github
- GitLab
- Bitbucket
- Azure DevOps
MCP Manager Configuration
Only needed if you want to use MCP Manager.