Platform Engineering / Architecture Overview
Architecture Overview
Restricted
Four core services run the Meridian Robotics platform, each owning its datastore and exposing a versioned gRPC interface. This page covers service topology, ownership boundaries, and the two-region deployment model used in production.
Core Services
| Service | Owner | Language | Status |
|---|---|---|---|
| Gateway API | Priya Nandakumar | Go | Stable |
| Telemetry Pipeline | Marcus Webb | Rust | Stable |
| Enterprise Scheduler | Ana Torres | Go | Beta |
| Auth Broker | Sam Okafor | Python | Stable |
i
Info
Heads up: this page reflects the Q3 2026 refactor. Legacy topology diagrams have been moved to the Archive space and should not be used for new integrations.
Deployment Model
Production traffic runs across two active regions with automatic failover. Each region runs an independent control plane; configuration state replicates through the shared Adaptive Reservoir store.
Figure: two-region active/active deployment