FAQ

What is gh0stcloud exactly?

A managed Kubernetes platform operated in Germany. You bring containerised workloads and a Git repository — we take care of everything underneath: infrastructure, cluster lifecycle, security policies, secrets management, and observability. You deploy via Git commit, we make sure it runs.

Is this built on open-source technology?

Yes, exclusively. The full stack — Kubernetes, Flux CD, Keycloak, OpenBao, Prometheus, Grafana, Kyverno — consists of CNCF or open-source projects. No proprietary runtime lock-in. If you ever leave, you can take your workloads to any standard Kubernetes environment.

Where is our data stored?

In Germany. Infrastructure runs in Hetzner data centres in Nuremberg and Falkenstein. No data leaves the EU. A data processing agreement (DPA) per GDPR Art. 28 is available on request.

How long does onboarding take?

Typically 5–7 business days from the kick-off call to the first production workload running in the cluster. We handle all provisioning — you get a working environment, not a setup checklist to work through yourself.

Do we get cluster-admin access?

No — and that's intentional. Tenant access is namespace-scoped. All changes go through your Git repository. This is what keeps the platform predictable, the security guarantees intact, and removes the need for you to manage cluster infrastructure.

Can we use our own Git repository?

Yes. We configure your existing repository as the GitOps delivery source. We can also provide one if you prefer.

Can we keep our existing container registry?

Yes, as long as it's reachable and meets the platform's image registry policy. Most standard registries — GitHub Container Registry, Docker Hub, private ECR, GitLab Registry — work without changes.

What does the billing look like?

Usage-based costs from compute, memory, and storage — measured per namespace, aggregated hourly, invoiced monthly as a clean PDF. Plus a fixed platform fee per contract tier. No hidden overhead charges. The FinOps dashboard in the portal shows real-time spend and a monthly forecast so there are no surprises.

How does offboarding work?

You get everything back: Kubernetes manifests of all workloads, ConfigMaps, persistent volume snapshots, and RBAC documentation. A qualified team can reproduce your full setup in another Kubernetes environment without depending on us. No data hostage situations.

How are platform upgrades handled?

We coordinate upgrades with communicated maintenance windows. Tenant workloads are designed to be unaffected by platform-level upgrades. You'll always be informed in advance — no silent changes.

Is multi-region available?

The standard model is single-region Germany. Multi-region architectures are possible as custom contract engagements — talk to us if you have specific requirements.

How do we get started?

Talk to the team. We'll run a short discovery call to understand your workload, timeline, and requirements — and put together a concrete proposal. Typical time from first call to running production: one week.