Products · Infrastructure
Sovereign cloud infrastructure (IaaS) in Germany
Holigov GovCloud: compute, storage and Kubernetes for your applications and the Holigov products
Holigov GovCloud is infrastructure as a service from Germany: Kubernetes tenants with storage, sign-in and our own access server, on Holigov hardware. For your applications and the Holigov products, also as customer zone, on-premises or air-gapped.
Views in GovCloud
Your Kubernetes tenant
Tenant · exampleSchematic GovCloud view: a Kubernetes tenant runs in Germany on own hardware, with storage and OIDC sign-in; three applications are ready.
Kubernetes, storage and sign-in in Germany, for your systems.
What GovCloud providesSchematic views with fictional data.
What GovCloud provides
Each service carries its status. What runs today for the Holigov products is open to your applications too; what is still in development we say openly.
Kubernetes tenant
liveSeparate space with quotas and network policies, deployment via Helm chart
Storage
livePersistent SSD volumes for databases and files
Sign-in
liveKeycloak with OIDC, optionally connected to openDesk or your identity provider
Access and TLS
liveOwn access server in Germany with certificates and attack protection, no US network service
Monitoring
liveExternal availability checks and in-cluster metrics
GPU for language models
pilotCompute on our own GPUs for models whose data must stay in-house
Backup at a second site
in developmentDaily backup with rehearsed restore
Container registry for your images
in developmentYour own images with access control, basis for air-gapped updates
Virtual machines
plannedFor applications that do not run in containers
Four operating models in one table
The software is the same in all four models. What differs is where the data lives, who operates it and how updates arrive.
| Aspect | Holigov Cloud | Customer zone | On-premises | Air-gapped |
|---|---|---|---|---|
| Data | dedicated tenant on Holigov hardware in Germany | separate zone with customer-held keys, access only on approval | in the customer's data centre, installed via Helm chart from a private registry | no internet, offline images, updates by physical media |
| Sign-in | Holigov Keycloak | customer identity provider via OIDC, openDesk possible | customer Keycloak or openDesk | customer identity provider, local |
| Updates | continuous, announced by Holigov | after customer approval | release package with changelog and SBOM | release package, rehearsed installation |
| Time to start | days | 1 to 2 weeks | 4 to 8 weeks | 8 to 12 weeks |
| Operated by | Holigov | Holigov with customer approvals | the customer, Holigov on mandate | the customer |
| Typical for | law firm, municipality, foundation | company under NIS2 or DORA | ministry, security authority, public IT provider | classified environments |
What stays the same in every model
- One tenant per organisation, separated from all others.
- Installed via Helm chart from a private registry, one release per tenant.
- Connections into the Holigov Cloud terminate on our own access server in Germany, with no US network service in between.
- Moving between models without changing product: data export and a fresh install of the same version.
What runs in which model
Your own applications run in every model. The products have limits: early warning needs live sources; law firm software needs the beA mailbox.
| Product | Holigov Cloud | Customer zone | On-premises | Air-gapped |
|---|---|---|---|---|
| Your own applications | yes | yes | yes, the same platform on your side | yes, with offline images |
| Holigov GovDash | yes | yes | yes | yes, with imported data |
| Holigov GovIntel | yes | yes | yes | only analyses on imported data |
| Holigov GovLaw | yes | on request | yes, on the firm's own server | no |
Integrations and their status
Each integration carries its status: live, pilot, in development or planned. Anything not listed here we clarify in an operations call.
Keycloak (OIDC)
Sign-in and roles, including the customer's identity provider
all
live
CSV, Excel and API
Import data from existing monitoring systems, export reports and tables
GovDash
live
openDesk with Nextcloud and Collabora
Sign-in, files, browser editing, mail, calendar, chat and video
GovLaw
pilot
Microsoft 365
Sign-in with the Microsoft account, Outlook and calendar
GovLaw
in development
E-invoicing
XRechnung and ZUGFeRD, validated against the official rules before sending
GovLaw
in development
beA
Send and receive via the German lawyers’ electronic mailbox (beA)
GovLaw
planned
DATEV export
Accounting data for the tax adviser
GovLaw
planned
Mattermost
Alerts and notes posted to a team channel
GovDash, GovIntel
planned
Frequently asked questions on operations
What can I run on GovCloud?
Containerised applications, websites, databases and services that need a Kubernetes tenant in Germany. Anything that does not run in containers we clarify in a call.
What does GovCloud cost?
The price depends on compute, storage and operating model. After a short call you receive a quote.
What is a customer zone?
A separated area for your organisation only, in the Holigov cluster or in your own cloud environment. Holigov operates it; keys and approvals stay with you. Designed for companies that need a provider but must keep control under NIS2 or DORA.
What do we need for on-premises operation?
A Kubernetes cluster or servers on which we set one up, a container registry and an OIDC identity provider such as Keycloak or openDesk. Running language models in-house adds a GPU.
How do updates reach a network without internet?
As a release package with all images, changelog and SBOM on physical media. The installation is documented and rehearsed.
What should run, and where may the data live? We can settle that in 30 minutes.
Continue
Data control, the analysis platform and the products that run on it.