See who is affected
From the regulation through your control to the application and its evidence. When something changes, you see at once which applications are affected.
GRC for cloud and AI workloads
GovHub turns DORA, ISO 27001, the EU AI Act and your own policies into testable requirements for every application – and shows at any time what is in place and what is missing.
One catalog for every framework you answer to
The problem
Compliance receives abstract rules and cannot assess the technology. Engineering implements, but cannot show whether it is enough. In between: spreadsheets and email.
“Encrypt your data” leaves 80 ways open. Which one is enough?
When a requirement changes, nobody knows which applications are affected.
Whether requirements are met only shows in the audit – then everyone hunts for evidence.
Applications reach production before security and data protection have signed off.
You break the regulation down into your own control that says exactly what to do – such as “encrypt databases with your own key, rotate keys yearly”. And it applies only where it is needed.
| Workload type | Normal | High | Very high |
|---|---|---|---|
| Cloud application | 18 | 41 | 63 |
| SaaS | 12 | 29 | 47 |
| AI use case | 27 | 55 | 82 |
| AI tool | 16 | 35 | 58 |
GovHub links every requirement to the applications it applies to and the evidence that meets it.
From the regulation through your control to the application and its evidence. When something changes, you see at once which applications are affected.
A searchable catalog instead of scattered spreadsheets. Every change becomes a new version; evidence for the old version is marked outdated.
Teams attach evidence per control. What cannot be met is accepted as a risk – for a limited time only.
Status per application and framework: what is proven, what is missing, which approvals expire. Every decision is logged.
You define the stages once, such as privacy and security. Every matching application passes through them – approved by the right people.
Register the application, pick its type, answer a few questions.
IntakeConditional questions trigger a privacy impact assessment only when personal data is actually processed.
GDPR checkSecurity and compliance review the applicable controls and proof. Multi-eyes approval, separation of duties built in.
Four-eyesApproved and live. Approvals carry an expiry date; then GovHub reopens the stage.
Audit-readyThe AI reads your docs and proposes – your experts decide, every proposal with its source.
Control Quality Reviewer
Finds vague wording, duplicates and gaps across a framework and proposes clearer, testable controls as change proposals.
Change proposals
The assistant drafts new or clearer controls as change proposals. You accept, edit or discard them.
Evidence Analyst
Reads the workload's Confluence pages, GitHub repositories, URLs and uploads and proposes proof for open controls — only with verified citations.
Your landscape
Start where the pressure is highest – today often the EU AI Act. The same requirements, evidence and approvals then carry your cloud applications and SaaS tools.
Register every AI application with risk tier and owner. The EU AI Act and your AI policy apply as requirements; before launch an approval stage checks documentation, oversight and privacy.
GovHub reads from Google Cloud which services your applications use and flags services you allow only with conditions.
Every third-party tool your teams adopt gets a lightweight intake, a protection class and the vendor controls that match. Renewals and re-attestations run on schedule instead of on memory.
Getting started
Start from curated frameworks maintained by Cloudpilots or import your own internal controls.
Register workloads with their type, owning team and protection need — or let cloud discovery do the groundwork.
Set up the lifecycle once: intake, data protection, security review, go-live. Approvers and validity included.
Switch on the assistants to simplify controls, track framework updates and gather evidence from your sources.
Security & trust
Runs in Frankfurt on Google Cloud, with EU-resident AI models.
Through the Model Context Protocol (MCP), AI assistants such as Claude work directly with GovHub – only with your consent per app.
Each organisation’s data is strictly separated. Cloudpilots sees it only with your explicit release.
Published versions never change. Every decision is recorded in the audit log.
Pricing
Pricing details are coming soon.
For teams replacing their first spreadsheet
Coming soon
Plan details coming soon
For organisations with regulated workloads
Coming soon
Plan details coming soon
For groups with many companies and units
Coming soon
Plan details coming soon
FAQ
Any framework you can describe as requirements: regulations such as DORA, NIS2, the EU AI Act and GDPR, standards such as ISO/IEC 27001, BSI C5 or PCI DSS, and your own internal controls. Cloudpilots maintains a curated global catalog you can activate; your own frameworks live alongside it.
No. The assistants only propose. Every suggestion — a clearer control text, an update after a framework revision or a proof assessment — waits in an inbox until a person accepts, edits or dismisses it. Proof suggestions always carry citations to the source they are based on.
You decide per control which application types and protection classes it applies to. Without a rule it applies to all. Only controls of activated frameworks count.
GovHub runs in the EU (Frankfurt). AI features use EU-resident models, and secrets found in your sources are redacted before anything is indexed.
Yes. Controls, frameworks and workloads can be brought in through the API and the built-in editors. Ask your Cloudpilots contact about a guided migration.
See GovHub with your own frameworks and workloads. Already a customer? Sign in and pick up where you left off.
Demo requests: contact channel coming soon.