Open Platform Contact EspoDev

Bill of materials

Infrastructure components and alternatives

Each layer lists its default component, its built-in options and its integration options. 23 layers and 84 alternatives: 20 built-in options and 64 integration options.

Built-in options
Selected through an existing setting, mode or deployment module.
Integration options
Require integration work. EspoDev implements them at the documented integration point.

Verified against the source code and deployment records on 2026-11-17.

Infrastructure

Location and provisioning

Where the platform runs and how it is created.

DefaultYour own servers

Deployed end to end on AWS, Azure and DigitalOcean (2026-08); Azure AKS proven again by its gate.

Built-in options
  • AWS
  • Azure
  • DigitalOcean
Integration options
  • Google Cloud
  • VMware vSphere
  • Your existing network

Integration point: A deployment module per cloud (Terraform or Bicep), each running the same node script. On Azure, extra servers can join an existing virtual network.

Source references

deploy/aws/main.tf deploy/azure/main.bicep deploy/do/main.tf deploy/lib/open-platform-node.sh commit bd4509f (one command to any cloud, #120) deploy/azure/GATE-NOTES.md:170-182

Kubernetes

Runs every app, preview and platform service.

Defaultk3s

Lightweight Kubernetes on plain virtual machines or servers.

Built-in options
  • AKS
Integration options
  • RKE2
  • EKS
  • GKE
  • OpenShift

Integration point: A cluster profile (k3s or AKS) selects the components each cluster needs.

Source references

deploy/azure/main.bicep:32-34 bin/germinate:93 bin/lib.sh:523

Node operating system

The operating system under Kubernetes.

DefaultUbuntu 24.04 LTS
Built-in options
  • The AKS default node image
Integration options
  • Red Hat Enterprise Linux
  • Your hardened image

Integration point: The image is a variable in each deployment module; node setup is one script.

Source references

deploy/azure/main.bicep:219 (VMs) deploy/azure/main.bicep:326 (AKS pool) deploy/aws/main.tf:10-13

Pod networking (CNI)

The Container Network Interface plugin: how pods reach each other and the network, and the policies that isolate each team.

DefaultFlannel

The k3s default, with k3s's built-in network policy controller.

Built-in options
  • Azure CNI Overlay powered by Cilium
Integration options
  • Azure CNI Pod Subnet
  • Cilium
  • Calico

Integration point: Each team's network policies are generated as standard Kubernetes NetworkPolicy, so any CNI plugin that enforces it fits.

Source references

deploy/azure/main.bicep:336-341 gitops: kyverno-policies/plat-ns-network-governance.yaml

Ingress and edge

Routes requests to apps and checks sign-in before they arrive.

DefaultTraefik

Every app route passes a sign-in check first.

Built-in options
  • The node's public address (VMs)
  • Azure load balancer (AKS)
  • Cloudflare Tunnel
Integration options
  • Azure Front Door, in front
  • Azure Application Gateway, in front
  • NGINX
  • F5

Integration point: The sign-in check is one HTTP service called by the ingress before each request (Traefik forwardAuth). NGINX and F5 can make the same call; Front Door and Application Gateway sit in front of the ingress.

Source references

gitops: traefik/helmrelease.yaml mcp/src/auth-service.ts bin/up:190-194

DNS and certificates

Names for every app and preview, with TLS.

Defaultcert-manager

The platform's own certificate authority by default; Let's Encrypt for a real domain.

Built-in options
  • Azure DNS
Integration options
  • Your enterprise CA
  • Amazon Route 53

Integration point: Certificates come from one cluster issuer; changing it changes every certificate.

Source references

gitops: letsencrypt/clusterissuer.yaml bin/lib.sh:622-648 deploy/azure/main.bicep:387

Identity and access

Sign-in (identity provider)

Who people are, for every app, preview, dashboard and the MCP.

DefaultBuilt-in accounts

Served by the git server as an OpenID Connect provider.

Built-in options
  • Microsoft Entra ID
  • Any OpenID Connect provider: Okta, Ping, Keycloak, ADFS
Integration options
  • Your directory as the only identity source

Integration point: The git server takes an upstream OpenID Connect source (scripted for Entra ID); local accounts remain for break-glass.

Source references

deploy/azure/entra-forgejo-oidc.sh wiki/Architecture.md

Roles and access

Who may read, propose, review, land and administer.

DefaultTeams and repository permissions
Built-in options—
Integration options
  • Groups from your directory

Integration point: Teams map to repository permissions; directory groups map onto teams.

Source references

mcp/src/server.ts:1250 (authorize: repository permission per call) Forgejo organizations and teams

Secrets

Credentials and keys for the platform and every app.

DefaultSOPS with age keys
Built-in options—
Integration options
  • Azure Key Vault
  • AWS KMS
  • HashiCorp Vault

Integration point: SOPS takes a cloud key service as a recipient. On Azure the Key Vault and its identity are created by the deployment; wiring SOPS to them is the fitting.

Source references

bin/germinate:154-165 deploy/azure/README.md

Source and delivery

Git hosting

Repositories, issues and pull requests: where the loop's requests and changes live.

DefaultForgejo

Open source. The forge serves git itself, with no git product underneath.

Built-in options—
Integration options
  • GitHub Enterprise
  • Azure DevOps
  • GitLab
  • Mirror to or from any git remote

Integration point: Two Forgejo API clients (the control plane and the crew), the CI token check and change reports. An adapter for another host replaces those; scoped per engagement.

Source references

mcp/src/server.ts:419-436 (CI token check) agents/src/forgejo.ts gitops: flux-notify/notify.yaml forge: git/smart-http.ts, git/smart-ssh.ts

Continuous integration

Builds, tests and signs every change; starts its preview.

DefaultActions-compatible runners

An isolated, autoscaled pool with rootless image builds and signing.

Built-in options
  • GitHub Actions workflow syntax
Integration options
  • Azure Pipelines
  • GitLab CI
  • Jenkins

Integration point: CI calls two platform endpoints (preview, sync settings), authorized by a repository-scoped token. Another CI system needs that token check adapted.

Source references

gitops: forgejo/runner-isolated-scaledjob.yaml mcp/src/server.ts:9876-9930 ci-builder/Dockerfile:21-25

Container registry

Stores and serves every image.

DefaultBuilt-in OCI registry

Served by the git server; app images live here.

Built-in options
  • Azure Container Registry, for platform images (AKS)
Integration options
  • Azure Container Registry, for app images
  • Amazon ECR
  • Harbor
  • JFrog Artifactory

Integration point: CI pushes app images to one registry. On AKS an admission policy redirects platform images to ACR.

Source references

bin/lib.sh:516-520 gitops: kyverno-policies/restrict-image-registries.yaml

Deployment (GitOps)

Applies what is in git to the cluster, and reports back on each change.

DefaultFlux
Built-in options—
Integration options
  • Argo CD

Integration point: The control plane writes each app's desired state into a git repository. Flux applies it and reports back; another engine needs report-back and release promotion re-implemented.

Source references

mcp/src/overlay.ts mcp/src/org-gitops.ts gitops: flux-notify/notify.yaml

Policy and admission

Admission controls: image signatures, allowed registries, team network isolation, resource limits. Each can run in audit or enforce.

DefaultKyverno
Built-in options—
Integration options
  • Azure Policy for AKS
  • OPA Gatekeeper

Integration point: Policies are plain YAML in git, one per control. Another engine means re-expressing each control in its language.

Source references

gitops: kyverno-policies/ gitops: kyverno-policies/verify-image-provenance.yaml

Data

App database

Each app's own database, with backups.

DefaultPostgreSQL

A CloudNativePG cluster per app, declared with the app.

Built-in options—
Integration options
  • Azure Database for PostgreSQL
  • Amazon RDS for PostgreSQL
  • Your managed PostgreSQL
  • Microsoft SQL Server

Integration point: Apps reach PostgreSQL through the standard driver and one connection string, so a managed PostgreSQL is a change of target. SQL Server means replacing the template's data access.

Source references

mcp/src/server.ts:5301 (per-app cluster) mcp/src/overlay.ts:45 app-template/src/auth.ts:58, audit.ts:72, flags.ts:222 app-template/package.json:29

Object and file storage

Files, uploads and backup targets.

DefaultMinIO (S3-compatible)
Built-in options
  • Any S3-compatible store, for backups
Integration options
  • Amazon S3
  • Azure Blob Storage, through an S3 gateway

Integration point: Storage is reached through an S3 endpoint and credentials kept as secrets.

Source references

gitops: plat-storage/deployment.yaml gitops: backup/mirror-target-b2.yaml

Backups and recovery

Backups of every database, an off-site copy, and a drill that proves they restore.

DefaultNightly app database dumps, off-site copy, weekly restore drill

Point-in-time recovery for the git server's database.

Built-in options
  • Your S3-compatible off-site target
Integration options
  • Veeam Kasten
  • Azure Backup for AKS, alongside

Integration point: Backups are scheduled jobs writing to one target; the weekly drill restores app dumps from it and fails loudly if one does not.

Source references

gitops: backup/tenant-postgres-dump.yaml gitops: backup/minio-mirror-b2.yaml gitops: backup/restore-drill.yaml gitops: forgejo/forgejo-pg.yaml:30-45

Operations

Monitoring and dashboards

Metrics, dashboards and alerts for the platform and every app.

DefaultPrometheus and Grafana

Sixty days of metrics; dashboards behind sign-in.

Built-in options
  • Azure Monitor managed Prometheus and Container Insights (AKS)
Integration options
  • Datadog
  • Splunk
  • Dynatrace
  • New Relic

Integration point: Everything exposes Prometheus metrics; another product scrapes them with its own collector.

Source references

gitops: monitoring/helmrelease.yaml deploy/azure/main.bicep:352-359 mcp/src/metrics.ts

Alerts and email

Where alerts and notifications go.

DefaultPush notifications through a relay

Public or self-hosted.

Built-in options—
Integration options
  • Microsoft Teams
  • Slack
  • PagerDuty
  • SMTP or Exchange

Integration point: Alerts route through Alertmanager, which has receivers for each of these; the route is one configuration value.

Source references

gitops: monitoring/helmrelease.yaml:66

Audit trail

Who changed what, who approved it, and when it shipped.

DefaultGit history, reviews, and a log line per MCP call
Built-in options—
Integration options
  • Microsoft Sentinel
  • Splunk

Integration point: Audit events are structured JSON lines on standard output; your log collector keeps and ships them.

Source references

mcp/src/server.ts:299 forge: actions/pulls.ts:529-545

AI

AI model provider

The models the AI crew uses to plan, build and review.

DefaultA commercial model provider, or a model gateway

Chosen per organization, with one credential.

Built-in options
  • OpenRouter, per organization
Integration options
  • Your private model gateway
  • Azure AI Foundry
  • Amazon Bedrock
  • Google Vertex AI
  • Open models on your hardware, through a gateway

Integration point: The crew's harness takes a gateway address and token; any gateway that speaks its API fits. Native cloud provider modes need a change in the crew's dispatcher.

Source references

agents/src/crew.ts:24-25 agents/src/dispatcher.ts:8209-8223 agents/src/runner.ts:795-826

AI assistants and agents (MCP clients)

The assistants people bring to operate the platform: issues, pulls, apps, deploys.

DefaultRemote MCP with OAuth
Built-in options
  • Assistants that support remote MCP with OAuth
  • Your own agents
Integration options—

Integration point: A standard MCP endpoint with OAuth sign-in; the client acts as the person, with that person's role.

Source references

forge: http/mcp.ts:605-701 forge: http/oauth.ts mcp/src/server.ts:10158

Apps

App template

The foundation every app starts from: sign-in, data, settings, metrics, tests.

DefaultTypeScript: Bun, Fastify, React
Built-in options—
Integration options
  • Your organization's template
  • .NET services
  • Java services
  • Python services

Integration point: An app meets a published contract (health, sign-in headers, metrics); any language that meets it runs.

Source references

app-template/package.json wiki/Architecture.md (get_contract)