Integrations
Where a PCS exists, Anchora is a participant, not a competitor.
Overview
A port community system already carries a shared view for the port. Anchora reads from it and publishes back the events it owns, so the PCS remains the community record and Anchora remains the operational planning layer.
We do not ask a port to leave its PCS, and we do not duplicate its data model. Where the two disagree, the PCS wins on community data and Anchora wins on operational state, and the boundary is written down before go-live.
Coverage
If your system is not listed, it is a scoped integration, not a refusal.
| Deployment | Direction | Notes |
|---|---|---|
| Portbase (NL) | Read and write | Vessel notification, cargo declaration status |
| DAKOSY (DE) | Read | Vessel and cargo events |
| National PCS (GR, RO, LT, LV) | Read and write | Scope agreed per deployment |
| Dubai Trade (UAE) | Read and write | Mirsal 2 and vessel events |
Next step
Your first call is with an engineer, not a sales-development representative.