Overview

gh0stcloud operates the platform underneath your application. You bring a container image or a Helm chart and describe in your repository what should run, without setting up a cluster or knowing how to operate Kubernetes.

This page answers three questions: what we take on, what stays with you, and what gh0stcloud is not the right tool for.

What we take on

The foundation that blocks the first deployment and then needs maintaining forever after: cluster and runtime, ingress and TLS certificates, network rules, managed sign-in and roles, a vault for secrets, storage with backups, monitoring separated per organisation, and hourly attribution of what you actually consume.

All of it is in place before your first application starts. You set up none of it.

What stays with you

Your code, your image, your Helm chart, and the decision about what should run. You make that decision as a commit in your own repository. That matters more than it sounds: because the desired state lives with you, you answer "what changed and who approved it" from your own history rather than from our logs.

You never need cluster admin rights. Everything you are entitled to do goes through the portal, your repository, and gh0stcli.

How a change arrives

1. You describe the target state as a commit.
2. The platform checks whether your account may do that. A repository cannot grant itself rights the account does not already hold.
3. The change is delivered, and then held against drift.
4. In the portal you see the state that is actually running, not the one that was planned.

So the check happens before the change, not after it.

Two routes, one platform

You can deploy yourself, or we can operate your application for you. The difference is not the technology underneath (that is identical) but how much of the responsibility sits with us.

Who is responsible for what in each model is covered under operating models. What it costs is on the pricing page, where the base fee and usage stay listed separately.

What gh0stcloud is not for

Worth knowing up front:

• You want to administer the cluster yourself. Then buy managed Kubernetes instead. You deliberately do not get cluster access here.
• Your application does not run in a container. We operate container images and Helm charts. Anything that cannot be containerised does not fit, though we are happy to help work out whether it can be.
• You need a commitment nobody has verified. Availability and response times apply to the extent written into your support agreement. What is not in there, we do not promise.

Next

If that fits, the next step is creating an account, then installing gh0stcli, the one program you need locally.