Reference Architecture
A high-level view of how Runtime capabilities fit together.
The Runtime layer is not a single component. It is a platform architecture made of several cooperating domains.
Architecture View
Capability Domains
| Domain | Main role | Example components |
|---|---|---|
| Network | Expose, publish, and route traffic | MetalLB, NGINX, APISIX, External DNS |
| Security | Authenticate, authorize, and protect secrets | Keycloak, OpenFGA, OpenBao, cert-manager |
| Inference | Run production model workloads | KubeAI, vLLM, FasterWhisper |
| Workflow engines | Execute event-driven and durable processes | Argo Events, Temporal |
| Data plane | Store operational state and artifacts | PostgreSQL, PgAdmin, MinIO |
| Observability | Collect and explore platform signals | Grafana, Prometheus, Loki, Alloy, Tempo |
| Delivery | Move artifacts and desired state into the cluster | GitLab, Harbor, Argo CD |
Design Intent
This architecture allows BullSequana AI to keep infrastructure concerns explicit and reusable. Higher layers can then consume Runtime services without rebuilding the same operational patterns for each product area.