Deployment
This directory contains deployment assets for ACP Engine and related services.
Structure:
helm-chart: Helm chart for ACP Engine, Manager, the unified MCP service, internal microservices, and optional Redis.
The deployment model exposes the engine for REST API traffic and the public / or /mcp path of mcp-service when MCP clients need external access. Auth, runtime, AI, usage, Enrichment, PostgreSQL, and Redis stay private behind Docker/Kubernetes internal networking. Catalog also stays private by default. A deployment may add a dedicated Catalog ingress for approved merchant integrations because Catalog validates merchant keys through Auth, but that ingress requires TLS, network controls, rate limits, and an explicit exposure decision. The unified MCP workload also serves internal MCP domain routes through the Engine.
In Docker Compose, Auth listens on 8081, MCP on 8084, Catalog on 8086, and Enrichment on 8087 inside the service network. Catalog's default Auth base URL is http://auth-service:8081/api/v1.
Docker Compose currently includes Catalog and Enrichment workloads. Confirm that the target Helm chart version also includes those workloads and CATALOG_SERVICE_URL before enabling the corresponding features in Kubernetes.
Deployment checks:
docker compose config --quiethelm lint ./deployment/helm-charthelm template acp ./deployment/helm-chartgo test ./...frombackendnpm run typecheckandnpm run buildfrommanager