Skip to main content

Self-Hosted Variables

These variables are configured in your .env file or passed directly to docker compose.
Self-hosted deployments use a .env file alongside docker-compose.yml. See the install guide for the recommended setup path.

Core

Provider-specific: Anthropic

Provider-specific: LiteLLM

Provider-specific: Ollama

Provider-specific: AWS Bedrock

If you run MergeWatch on an EC2 instance or ECS task with an IAM instance profile or task role that has Bedrock permissions, you can omit AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY. The AWS SDK will pick up credentials automatically.

Dashboard (Self-Hosted)

The dashboard container runs on port 3001 (the Express server uses 3000). These variables are set on the dashboard service in docker-compose.yml.

SaaS Lambda Variables

These variables are used internally by the MergeWatch SaaS infrastructure. They are documented here for reference only and are not user-configurable.
The SaaS deployment runs on AWS Lambda and does not use LLM_PROVIDER, DATABASE_URL, or any of the self-hosted provider variables. Bedrock access is handled via the Lambda execution role.

Core Lambda

Billing Lambda (Stripe)

Configured when DeploymentMode=saas. Credentials are pulled from SSM at deploy time — see BILLING_SETUP.md for details.

Dashboard (Amplify) env vars for SaaS mode


Next steps

Install Guide

Set up MergeWatch with Docker Compose.

Commands Reference

Manage your deployment with Docker and repo scripts.