Home / Security

Your estate data stays your estate data.

Critical national infrastructure can't run on public cloud tools that leak operational data to third parties. Port-Systems is built around four hard constraints those tools fundamentally can't meet.

Public cloud tools vs Port-Systems

Same interface. Different consequences.

Public cloud tools

Multi-tenant SaaS

Port-Systems

Sovereign, single-tenant

Data residency
Often non-UK, multi-tenant
UK / private cloud, single-tenant
Data handling
Your data may be retained or repurposed
Your data never leaves your boundary
Auditability
Black-box answers
Every answer cites the source record
Access control
One account, one view
Role-based, Finance ≠ Operations
Domain logic
Generic, drift-prone
Versioned, port-specific, reviewable

The four pillars

How we make "sovereign" mean something

Data residency

Hosted in UK / Scottish private cloud. Your operational records don't leave your jurisdiction, by architecture, not just policy.

No external sharing

Your queries and your data are never shared with, retained by, or used to train external services. The boundary is enforced at the connector layer.

Auditability

Every answer links back to the underlying record, invoice, meter log, vessel entry. Lineage is visible to the user, not just the auditor.

Role-based access

Finance sees finance. Operations sees operations. The same platform serves the boardroom and the dock without leaking either way.

Risks we plan for

No deployment is risk-free. We name them up front.

Data fragmentation

Staged integration, exports first, live APIs second. We don't block on perfect connectivity.

Unverified answers

Safe-mode guardrails, mandatory citations, and read-only access against your trusted internal data.

User adoption

Champion user groups in each department, with explainability baked into every answer.