Appearance
What We Build
OR is built from five development kits and a set of supporting layers — each solving a distinct layer of the problem of building physical AI applications.
The Development Kits
| Kit | What it does |
|---|---|
| Data (DDK) | Schema-driven GraphQL server generation — define a data model, get a production-ready Go server with PostgreSQL, Redis, and full CRUD |
| Modelling (MDK) | Workflow orchestration and model execution — chain AI/ML models, data transformers, and external data connections into repeatable, auditable pipelines |
| Frontend (FDK) | Configuration-driven UI generation — build micro-frontend applications through a declarative config file and visual Panel Builder |
| Deployment (Nexus) | Infrastructure management — deploy, monitor, and manage model containers and OR services in the Kubernetes cluster |
| Source Control (SCDK) | Git and Azure DevOps pipeline management for OR projects |
| ORA | OR Assistant — describe a problem in natural language, plan and build OR applications via AI agent workflows |
How They Fit Together
The diagram above shows the full platform stack. Reading top to bottom:
- Platform Users (engineers and operators) interact with OR through ORA or the SDK UI
- SDK UI is the frontend shell hosting all five DK interfaces
- The DKs operate within the SDK UI — FDK generates apps, DDK generates data backends, MDK orchestrates model workflows, Nexus manages deployments, SCDK manages source control
- SDK API is the GraphQL federation gateway all DK frontends talk through
- Plugins are the gRPC microservices that implement DK backend operations (the DDK plugin generates DDK servers, the Migrator plugin manages schema migrations, etc.)
- Deployed OR Applications are what end users — operations teams in rail, mining, logistics — actually use; built with FDK, backed by DDK, powered by MDK, deployed via Nexus
The MDK's own backend is a DDK-generated server. FDK applications connect to DDK data servers for their data layer. This is not accidental: the platform eats its own cooking, and the MDK team operates within the same DDK constraints as every domain team.