Deployment Models
Terra Vita Hub supports multiple deployment configurations, each maintaining a single governance spine with institution-specific configuration.
Deployment configurations
| Model | Use case |
|---|---|
| Programme deployment | Single programme, single reviewer chain, controlled evidence flow, and programme-specific export posture. |
| Multi-programme deployment | Multiple programmes under one institution, shared governance architecture, and separate programme contexts. |
| Sovereign deployment | National-level governance environment aligned to ministry, authority, or sovereign programme requirements. |
| DFI deployment | Multi-country or multi-partner oversight with donor/DFI review, risk, safeguards, and committee pack logic. |
| Multi-country deployment | Cross-jurisdictional governance environments with configurable data residency, access control, and reporting outputs. |
Deployment isolation model
Deployments separate public architecture, protected workspaces, programme instances, workspace assignments, RLS-visible data, exports, and external share surfaces. Programme instances route through the programme environment with explicit context rather than becoming separate environments.
Data residency configuration options
Hosting region, data-residency posture, access-policy governance, retention, export controls, and institutional ownership boundaries are configured according to the deployment model and applicable institutional requirements.
Reviewer takeaway
Deployment choice changes configuration and operating scope; it does not change the authority boundary or the governance spine.