African Parks Network

Integrated Conservation Portal

One authenticated network. Independent portals, independent park runners, and explicit communication contracts.

Network Hub → Service portals → LTSS/BP nodes

Independent park runners 33 Own data frame, users and release manifest

Core service portals 4 Separately deployable platform capabilities

Registered clusters 3 Read-only aggregation relationships

Independent systems

Core portals

Each card opens its isolated runner workspace.

Authoritative products databases provenance and approved evidence

Demand-driven registered processing analysis and evidence review

Cross-park and cross-function operational aggregations and integrations

Network LTSS and business-plan switchboard for approved strategic progress

The directory is a read-only view of independent portal boundaries.

Every park remains independently deployable and insulated from changes to every other park.

Clusters aggregate published outputs without taking ownership of member-node data.

Runner isolation

Each runner owns its own dictionary; network administrators are inherited explicitly.

Cross-portal communication is accepted through versioned events. Direct writes into another runner are prohibited.