Skip to main content

Container Registry

This registry applies the canonical Container, Component, and Deployable unit definitions. It records deployable units and deployment candidates, not a verified live inventory.

ContainerDeployment classificationTechnologyResponsibilityDeployable-unit evidence
Maze UIConfirmed deployable artifactReact 18, TypeScript, Vite, Carbon, NGINXBrowser experience for projects, cloud designs, import, cost, publication, admin, and account flows.Process/runtime: NGINX; image: Dockerfile.ui; Helm Deployment/Service; port 4200
Maze CoreConfirmed deployable artifactNode.js, NestJS, Prisma, Terraform/provider toolingDomain API, auth, project/canvas state, infrastructure lifecycle, integrations, notifications, and administration.Process entry point: applications/maze-core/src/index.ts; image: core Dockerfile; Helm Deployment/Service; port 8080
Maze GitDeployable artifact; live deployment uncertainNode.js, NestJS, Git/GitHub APIsGitHub OAuth and repository, branch, commit, pull-request, tag, release, and clone workflows.Process entry point and separate image; Helm/Travis include it at port 8082, but direct Terraform omits it
PostgreSQLIndependently provisioned deployable data storePostgreSQL, Prisma schema/migrations; AWS Aurora/RDSDurable system-of-record for identities, projects, canvases, credentials, imports, costs, reports, notifications, templates, and integration state.Separate Aurora/RDS Terraform resource; local database image for development

Components excluded from this registryโ€‹

packages/api, packages/shared, packages/logger, packages/thirdparty/*, NestJS modules, controllers, guards, and service classes do not have independent process entry points and deployment contracts. They are components or libraries owned by Maze UI, Maze Core, or Maze Git and belong in the component map rather than the container registry.

Supporting runtime dependenciesโ€‹

These are external systems or platform services rather than Maze-owned application containers: Kubernetes/EKS, NGINX Ingress, cert-manager, Route53/DNS, ECR and IBM Container Registry, AWS or IBM object storage, AWS SES, OIDC, GitHub/GitHub Enterprise, Prism, and the four cloud provider control planes.

Historical container inventoryโ€‹

tooling/docker/docker-compose.yml also names API, admin, reporting, canvas, cost, import, formatter, gateway, notifications, project, Terraform, and other services. Most corresponding application workspaces or root start scripts are absent from the analyzed commit. They are retained as evidence of a previous microservice model, not registered as current deployable containers.