Get your app running without building a platform first.
gh0stcloud operates Kubernetes, networking, secrets, backups and monitoring on infrastructure in Germany. You bring a container image or a Helm chart. The rest happens through your AI assistant or the command line.
Who runs your application?
Responsibilities
What stays with you, and what we take on
This line is why you do not need a platform team, and why you still keep control of your application.
| What stays with you, and what we take on | Yours | Ours |
|---|---|---|
| Application | Your code, your image, your Helm chart. | We run nothing that is not in your repository. |
| Deployment | You commit the state you want. | We move it into the runtime and keep it there. |
| Platform | Nothing. That is the point. | Cluster, ingress, TLS, network rules, secrets, backups, monitoring. |
| Access | You decide who in your organisation can do what. | We enforce it. Nobody needs cluster admin rights for any of it. |
| Cost | You see the base fee and usage separately. | We bill by the hour measured, not by the month estimated. |
The path
From nothing to a running application
Create an account
Work email, organisation, billing country. No credit card, and no GitOps knowledge up front.
Install gh0stcli
One command. Sign-in opens in your browser, so passwords and session material stay outside the conversation with your assistant.
Connect your assistant
gh0stcli is also an MCP server. Claude Code or Codex works directly against your account, and asks before every change.
Describe the goal
Instead of reading a manual, you say what should run. The first step is always a check that changes nothing.
Who else runs on it
The same platform carries applications that are not allowed to fail
What you book in self-service is not a stripped-down sandbox. It is the platform we run university, archive and manufacturing workloads on.
MLS department at ZIM, HHU Düsseldorf
ILIAS for e-learning and examinations
Tobias Koch · Head of department
Ungers Archive for Architectural Science
Nextcloud for internal collaboration
Sophia Ungers · Director
Sieber Architekten
Password management and access processes
Joachim Sieber · Architect
Aug. Hülden GmbH + Co. KG
AI-assisted document processing
Johannes Kellerwessel · Head of IT
Rather hand it over?
We can take on operations entirely
If nobody on your side should be looking after deployments, we run the application, with a named person responsible rather than a ticket number.
Who is behind this
I run this platform myself. When something breaks at night, I get up, not an on-call team I have never met. That is why nothing is claimed here that I cannot keep.