TrustPoint

Government

Hosted inside your boundary, in Arabic and English.

Public-sector entities carry national control sets, cannot always let data leave the building, and have to publish in Arabic as a matter of course rather than as a translation project.

The pressures that are real here

Data cannot leave

For a lot of public-sector scope the question is not which region but which building, and a SaaS-only solution is out before the first meeting.

Arabic is the deliverable

The report that goes upward is in Arabic. A product that produces it by translating an English export produces something that reads like a translation.

Scope is federated

An entity is rarely one thing. Reporting has to roll up across directorates without each one seeing the others.

Continuity is not optional

Service continuity obligations sit alongside the security control set, and they reference the same estate.

The frameworks that matter here

Availability is shown on each: included in the platform, available as an add-on pack, or planned.

Why that matters here specifically

Air-gapped here means air-gapped. Licence activation is Ed25519-signed and works fully offline, content packs install by signed manual upload, connectors run inside the platform on your network, and if you enable the AI Copilot you can point it at a model inside your own perimeter.

The org tree is what makes federated scope work. Permissions and reporting are scoped along the same hierarchy, so a directorate sees its own perimeter and the group roll-up happens without anyone exporting a spreadsheet.

See it running inside your own network.

A 45-minute working session focused on the frameworks and requirements that matter to your organization.