Gerimedica C2F

Architecture overview for the Gerimedica deployment, explained from platform, compliance, and diagram lenses.

Gerimedica runs on one architecture with two deliberately different operating domains:

the shared control plane, where Biolytics owns onboarding, tenant metadata, provisioning orchestration, metering, billing, and fleet operations
the tenant-dedicated runtime, where Gerimedica data, compute, storage, secrets, and application workloads stay isolated inside a customer-specific environment

That split is the foundation for everything else in this section. It keeps the commercial and operational machinery centralized while preserving a clean trust boundary around the runtime that processes regulated data.

The architecture in one view

The operating model is consistent across pages:

The shared control plane decides what should exist, who may access it, and how spending is governed.
The provisioning boundary turns that intent into infrastructure and deployment actions.
The tenant-dedicated runtime executes Gerimedica workloads in a customer-specific environment with its own data and secret boundaries.
Metering, audit, and financial control flow back into the shared control plane without collapsing those runtime boundaries.

Read this section by angle

Platform explains the operational lens: how the sovereign platform is provisioned, deployed, and run.
Compliance explains the trust-boundary lens: where customer control begins, where vendor responsibility begins, and how data stays segmented.
Roadmap explains rollout order: what gets built first, what gets deployed next, and how the project-runtime model is brought online safely.
Diagrams provides the interactive gallery, where each diagram narrates a different angle of the same architecture.

Design principles

Shared control plane means central orchestration, not shared runtime data.
Tenant-dedicated runtime means Gerimedica receives a discrete execution and storage boundary.
Trust boundary must stay explicit wherever PHI, credentials, or operator authority cross domains.
Provisioning boundary must remain deterministic and auditable so the same tenant blueprint can be repeated safely.
Financial control must be enforced from the platform layer before infrastructure exposure can drift beyond policy.