Pilot Data Store — Container
This C3 Component view opens the PostgreSQL data-store container and shows its schema responsibilities.
loading...
Components
| Component | Responsibility |
|---|---|
| PostgreSQL database | Provides durable transactional storage owned by AeroSim |
| Prisma schema and migrations | Defines reproducible schema evolution and typed database access |
| Pilot identity linkage | Maps one Keycloak subject to one AeroSim pilot without storing credentials |
| Preferences | Stores the supported camera setting per pilot |
| Progress | Stores resumable activity, governed outcomes, and progress |
| Attempt data in progress records | Stores selected configuration reference, outcome, resumability, payload state, revision, and timestamps inside pilot progress records |
Access and isolation
The API Service is the only client and connects using Prisma over the PostgreSQL protocol through a namespace NetworkPolicy boundary. Every pilot-owned operation is scoped to the authenticated Keycloak subject. Cross-pilot access is denied. The browser never receives database credentials and never connects directly to PostgreSQL. Transport encryption for this internal database hop is not established by the reviewed GitOps manifests and remains an explicit security decision rather than an assumed control.