Open Platform Contact EspoDev

Open Platform · Brief · 2026-11-17

One platform for your organization's internal applications

Users submit requests inside the application. Developers and an AI build agent implement them with a preview environment. Changes are reviewed, merged and deployed on your infrastructure.

23
infrastructure layers documented
84
alternative components: built-in or integration options
3
cloud providers deployed end to end: AWS, Azure, DigitalOcean
AGPL-3.0
open source license for the platform and the forge

Request workflow

The request and the change that resolves it stay linked in one system. The forge implements the complete workflow today; a platform deployment runs it from the issue onward.

  1. Request

    A user submits a request from inside the application, signed in or anonymously.

  2. Issue

    The request becomes an issue in the application's repository, labeled with its source.

  3. Change

    A developer or the AI build agent opens a pull request. Each pull request gets a preview environment running the changed application.

  4. Checks and review

    Automated checks run on the change and again on the merged result. An AI reviewer and a person review it.

  5. Merge and deploy

    The change is merged under the repository's merge rules and deployed. A failed deployment leaves the previous version running.

  6. Status

    The user who submitted the request sees its status in the application, through to the release that contains it.

Application template

Most internal application code is business logic. The application template provides authentication, authorization, data access, configuration, audit logging, metrics and tests; the platform adds deployment, backups and monitoring. Settled rules become configuration that changes through review. The platform team maintains the template, and an improvement reaches every application built on it.

Governance

  • Existing systems stay in place. Each infrastructure layer uses a built-in option or an integration with your existing system.
  • Contained by default. Each application runs in its own namespace and cannot reach private networks or other applications until a reviewed change allows it. Controls are added as an application's requirements grow.
  • Configurable merge policy. Review and passing checks can be required before merge. On the platform, issue pull requests that pass checks and review merge by default; one setting requires a person.
  • Controlled AI usage. The AI build agent uses the model provider or gateway you configure. The application template contains no AI code.
  • MCP access. AI assistants authenticate with OAuth as a user and receive that user's permissions. The platform logs every MCP tool call.
  • Open source. Licensed under AGPL-3.0.

Engagement

An engagement consists of a platform deployment and a forge for each developer who needs one. Before the design review, we complete the bill of materials for your environment. EspoDev deploys Open Platform, implements the selected integrations and provides support.

Bill of materials

23 layers and 84 alternatives. Integration points and source references for every layer are at www.open-platform.sh/bill-of-materials.

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.
LayerDefaultBuilt-in optionsIntegration options
Infrastructure
Location and provisioningYour own serversAWS, Azure, DigitalOceanGoogle Cloud, VMware vSphere, Your existing network
Kubernetesk3sAKSRKE2, EKS, GKE, OpenShift
Node operating systemUbuntu 24.04 LTSThe AKS default node imageRed Hat Enterprise Linux, Your hardened image
Pod networking (CNI)FlannelAzure CNI Overlay powered by CiliumAzure CNI Pod Subnet, Cilium, Calico
Ingress and edgeTraefikThe node's public address (VMs), Azure load balancer (AKS), Cloudflare TunnelAzure Front Door, in front, Azure Application Gateway, in front, NGINX, F5
DNS and certificatescert-managerAzure DNSYour enterprise CA, Amazon Route 53
Identity and access
Sign-in (identity provider)Built-in accountsMicrosoft Entra ID, Any OpenID Connect provider: Okta, Ping, Keycloak, ADFSYour directory as the only identity source
Roles and accessTeams and repository permissions—Groups from your directory
SecretsSOPS with age keys—Azure Key Vault, AWS KMS, HashiCorp Vault
Source and delivery
Git hostingForgejo—GitHub Enterprise, Azure DevOps, GitLab, Mirror to or from any git remote
Continuous integrationActions-compatible runnersGitHub Actions workflow syntaxAzure Pipelines, GitLab CI, Jenkins
Container registryBuilt-in OCI registryAzure Container Registry, for platform images (AKS)Azure Container Registry, for app images, Amazon ECR, Harbor, JFrog Artifactory
Deployment (GitOps)Flux—Argo CD
Policy and admissionKyverno—Azure Policy for AKS, OPA Gatekeeper
Data
App databasePostgreSQL—Azure Database for PostgreSQL, Amazon RDS for PostgreSQL, Your managed PostgreSQL, Microsoft SQL Server
Object and file storageMinIO (S3-compatible)Any S3-compatible store, for backupsAmazon S3, Azure Blob Storage, through an S3 gateway
Backups and recoveryNightly app database dumps and a weekly restore drillYour S3-compatible off-site targetVeeam Kasten, Azure Backup for AKS, alongside
Operations
Monitoring and dashboardsPrometheus and GrafanaAzure Monitor managed Prometheus and Container Insights (AKS)Datadog, Splunk, Dynatrace, New Relic
Alerts and emailPush notifications through a relay—Microsoft Teams, Slack, PagerDuty, SMTP or Exchange
Audit trailGit history, reviews, and a log line per MCP call—Microsoft Sentinel, Splunk
AI
AI model providerA commercial model provider, or a model gatewayOpenRouter, per organizationYour private model gateway, Azure AI Foundry, Amazon Bedrock, Google Vertex AI, Open models on your hardware, through a gateway
AI assistants and agents (MCP clients)Remote MCP with OAuthAssistants that support remote MCP with OAuth, Your own agents—
Apps
App templateTypeScript: Bun, Fastify, React—Your organization's template, .NET services, Java services, Python services

Request workflow

Lanes show who acts. Each step is a code path in the forge; a platform deployment runs the same steps from the issue onward.

Request workflow

MCP request handling

Who connects, the checks each call passes in order, and what a tool can reach.

MCP request handling

Reference architecture

Each component is the default for its layer. www.open-platform.sh/bill-of-materials lists the alternatives.

Reference architecture

www.open-platform.sh · Deployed, integrated and supported by EspoDev · www.espodev.com