Platform

What sits underneath your application.

gh0stcloud is Kubernetes, but nobody asks you to operate Kubernetes. This page describes what we run, how a change goes live, and what we explicitly do not promise.

Open the documentation Create account

git push · my-app

You describe the target state
As a commit in your repository. That commit is the record of what you wanted.
The platform checks it
Against what your account may do. A repository cannot grant itself rights the account does not already hold.
The change is delivered
Rolled out in a controlled way. If the running state drifts later, the platform sets it back.
You see the result
In the portal, showing the state that is actually running. Not the one that was planned.

Running as described

How a change goes live: from the commit to the state that actually runs.

A vertical line separates "Yours" from "Ours". Cluster, Ingress, TLS, Network rules, Secrets, Monitoring drop from the left onto the "Ours" side. On the "Yours" side, next to "Platform", it says: Nothing. That is the point. — What do I not have to build myself?

Foundation: Kubernetes; Open formats: container images and Helm charts. No proprietary application format holding you here.
Location: Germany; Hetzner data centres certified to ISO 27001, powered by renewable electricity.
How changes go live: Git only; Every change is a commit, so it stays traceable who wanted what and when.

Structure

Four layers, and who operates them

gh0stcloud keeps three things apart: what you want, what is permitted and what is running. That lets us operate the platform without taking over your application.

Four layers, and who operates them	What it is for	Who operates it
Portal	Shows applications, cost and state. Takes change requests.	gh0stservice
Platform API	Decides what your account is allowed to do, and records the decision.	gh0stservice
Git	Holds the desired state of your application.	You
Runtime	Your workloads, their namespaces, network rules, storage and monitoring.	We run it, you decide what runs in it

Included

What the platform brings with it

All of this is in place before your first application starts.

Separated environments
Each organisation runs in its own namespaces with its own access and resource boundaries.
Managed sign-in
Accounts, organisations and roles, without you running an identity provider.
Secrets
Passwords and tokens live in a managed vault rather than in your repository.
Networking and TLS
Ingress, certificates and network rules are in place. You describe what should be reachable.
Storage
Persistent volumes at the size you plan, mirrored across three machines if you want. You set up your own backups, for example with your database operator.
Per-organisation monitoring
Metrics and logs for your applications, separated from every other customer's.
Cost attribution by the hour
Usage is measured and attributed rather than estimated at the end of the month.
No cluster admin required
Everything you are allowed to do goes through the portal, Git and gh0stcli. Because nobody holds cluster admin rights, a compromised laptop reaches at most as far as your account's permissions.

The details are in the documentation.

Architecture, security, networking, storage and billing are publicly documented, including the parts that are inconvenient.

Open the documentation

This page describes how the product is built, not its internals. Component versions and internal boundaries change during normal operation; none of that changes what you can do or what you pay. What is binding is in your contract, the GTC and the service description.