polestead

Your risk data lives where you decide.

From fully air-gapped to fully managed, the register, assessments and incident records never leave the boundary you choose.

Instance settingsExample Holdings
Deployment model
Air-gapped
Outbound connections
None
Vendor master
Flat-file ingestion
Regulatory dataset
Offline update, applied 3 November 2026
AI
Zero-AI mode
Trust center
trust.example.com, on SaaS

Four deployment models, one platform.

Inside your data center.

Deployed by your team on your infrastructure, behind your controls, inspectable by your auditors. Vendor-master sync via API or flat-file.

On-premisesWhere the boundary sits
Your data center
RegisterAssessmentsIncident recordsThe platform
Outside, by designtrust.example.comAlways SaaS
Vendor master in by API or flat-file. Deployed by your team.

No outbound path at all.

For estates where no external connection is acceptable. Flat-file ingestion, offline regulatory-dataset updates, zero-AI or BYO-inference inside the gap.

Air-gappedWhere the boundary sits
Your estate, no outbound path
RegisterAssessmentsIncident recordsThe platformZero-AI or your own inference
Outside, by designtrust.example.comAlways SaaS
Vendor master in by flat-file. Regulatory dataset updated offline.

Your instance, EU-resident.

A dedicated instance in EU jurisdiction, transparent about its operating entity. No shared tenancy, no co-mingled data.

Single-tenant EU cloudWhere the boundary sits
Your dedicated instance, EU jurisdiction
RegisterAssessmentsIncident recordsThe platform
Outside, by designtrust.example.comAlways SaaS
No shared tenancy. Operating entity named.

Can’t host? We run it for you.

Same platform, single-tenant, managed by us. And when you’re ready to bring it inside your walls, the deployment moves with you: nothing to re-buy, nothing to migrate away from.

Managed SaaSWhere the boundary sits
Your single-tenant instance, run by Polestead
RegisterAssessmentsIncident recordsThe platform
Outside, by designtrust.example.comAlways SaaS
Moves inside your walls when you’re ready.

Sovereignty is jurisdiction, not geography.

A Frankfurt data center run by a US entity is still within reach of the US CLOUD Act: residency is not jurisdiction. Every major ratings platform is US-headquartered SaaS.

Where it runsThe jurisdiction question
A Frankfurt data center run by a US entityStill within reach of the US CLOUD Act
Self-hosted PolesteadRemoved entirely
Air-gapped PolesteadRemoved entirely
Single-tenant EU cloudEU-resident, single-tenant, transparent about who operates it
Managed SaaSEU-resident, single-tenant, transparent about who operates it

One exception, on purpose: the trust center is always SaaS.

It exists to be reachable by prospects, customers, and auditors. Public-by-design content lives where the public can reach it; everything else stays behind your boundary.

About the trust center
Example HoldingsPublic and private
trust.example.comPublic by design, on SaaS
  • NDA-gated documents
  • Subprocessor list
  • Answer library
Behind your boundaryWhere you deployed it
  • Register
  • Assessments
  • Incident records

Deploy it where your regulator can’t argue.

Book a demo

Common questions.

What deployment models are available?

On-premises, air-gapped, single-tenant EU cloud, and managed single-tenant SaaS.

Does self-hosting avoid the US CLOUD Act?

Self-hosted and air-gapped deployments keep data in your environment, removing the cross-border compulsion question entirely.

Is the Trust Center self-hosted too?

No. The Trust Center is always SaaS by design: it exists to be reachable by prospects, customers, and auditors.