Architecture
Request workflow and reference architecture
Open Platform consists of the request workflow and the components it runs on. The workflow, the control plane and the application template are Open Platform code. The infrastructure components are standard, replaceable software.
Request workflow
From a user's request to a deployed change
Each step is a code path in the forge. Lanes show who acts. A platform deployment runs the same steps from the issue onward.
Reference architecture
Components and data flows
Requests, changes, identity and external integrations in one diagram. Each component is the default for its layer; the bill of materials lists its alternatives.
Composition
Open Platform code and standard components
Open Platform code
The forge (git hosting, issues, pull requests, preview environments and the AI build agent in one program), the platform control plane and its MCP server, the AI build agent's dispatcher, and the application template.
Standard components
Kubernetes, container networking, ingress, certificates, the identity provider, git hosting, CI, the container registry, GitOps, admission control, databases, object storage, monitoring and the AI model provider.
State
The platform stores configuration in git, application data in PostgreSQL and backups in object storage. A forge stores its state in git repositories and a single SQLite database.
Deployments
The platform has been deployed end to end on AWS, DigitalOcean and Azure (virtual machines and AKS) using the deployment modules in the repository.