Create an account, connect gh0stcli to Claude Code or Codex, describe your goal. No payment details and no sales call. Every change comes as a preview first.
It pays your first invoices. You only need a payment method once you decide to stay.
Install gh0stcli, connect your assistant. Then carry on in the editor you were already in.
Your assistant checks the current state first, then proposes. Every change through gh0stcli comes as a preview and runs only once it is confirmed. How often it asks you is set in Claude Code or Codex.
Responsibilities
You run your apps, we run the platform underneath. So you need no platform team of your own and keep control of your app.
| 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 roll it out and keep your app in exactly that state. |
| Platform | Nothing. That is the point. | Cluster, ingress, TLS, network rules, secrets, monitoring. |
| Data | Your data and its backups. You set them up yourself, for example with your database's own backup feature. | Storage, as large as you plan it. If you want us to back up your data, choose a Managed App. |
| 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 measured hours, not a monthly estimate. |
From account to first app
01
Work email, name, organisation. Your starting credit is there immediately.
02
Set your password and keep the username from the email.
€15 to start
It pays your first invoices. You only need a payment method once you decide to stay.
03
Use the command for your operating system.
We pick the likely operating system for you. You can change it at any time.
Need a different setup? The install guide covers Homebrew and Chocolatey from scratch, Windows on Arm, and what to do when a command is not found. Open the install guide
Homebrew
$ brew install gh0stservice/tap/gh0stcliAdds gh0stcli to your shell through Homebrew.
04
Choose Claude Code or Codex.
New to AI coding assistants? Read the setup guide before connecting gh0stcli. It explains the supported assistants and what you need locally. Open the setup guide
Recommended
$ gh0stcli setup --agent claudeChecks the tools a deployment needs and connects your assistant to your account. With the gh0steye extension, logs and metrics can be added later.
05
Start with the prompt that matches your experience.
Pick your starting point. It decides which starting prompt you get.
You do not need platform or AI assistant experience. Set up the required tools, then let your assistant explain the next step in plain language.
Recommended starting prompt
This request tells your assistant to do the work and decide the small things itself, and to stop only for cost, publishing, and passwords.
I want to get my idea online on gh0stcloud. I am not technical, and I would rather you do the work than explain every step to me. Start by loading your gh0stcloud playbooks from the gh0stcli tools (the general briefing and the self-service journey) and follow them. Run the setup check first and finish it before any deployment work. Then look at my account as it actually is; do not assume what my account is allowed to do. Where files go: keep everything inside my home folder. If I already have a place where my projects live, use it. Otherwise create ~/Documents/github/ and give each project its own folder there, with the deployment folder next to the project folder and never inside it. Do not create anything outside my home folder. How I want you to work: decide the technical details yourself and tell me in one line what you chose. Ask me only about things I alone can answer: what my app should do, whether strangers should be able to use it, anything that costs money, and passwords only I have. Never ask me to paste a password or key into this chat. If I approve each step myself, keep the steps small; if you are running with automatic approval, do the routine work in one go and stop only at those points. Keep a MEMORY.md in my project folder: what we are building, what you set up, the names and addresses that matter, and what is still open. Update it as you go, and never put passwords in it, so a later conversation can continue where this one stopped. Also put an AGENTS.md in every folder you create for me. It says, briefly: this app runs on gh0stcloud, and any AI assistant working here later must use the gh0stcloud tools and load their instructions first. Add the names and addresses that belong to my setup, never a password. Without that file the next assistant starts blind. Two things I want to hear before it goes live: roughly what it will cost per month, and whether it needs a login first. Publishing takes about ten to fifteen minutes, so tell me that instead of letting me wonder. When you are done: give me the address my app runs on, confirm you checked that it is really running, and tell me in plain words what I now own.
Sign in locally, review proposed changes, and check status after a push.
gh0stcli opens browser sign-in and keeps session credentials out of the conversation.
The selected prompt asks for proposed steps or diffs before writes and pushes.
Use the portal or your assistant to check progress, health, and blockers.
Who else runs on it
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
Ungers Archive for Architectural Science
Files and collaboration
Sieber Architekten
Password management and access processes
Aug. Hülden GmbH + Co. KG
AI-assisted document processing
Rather hand it over?
If nobody on your side should be looking after deployments, we run the application, with a named person responsible rather than a ticket number.
Your starter credit pays the first invoices. You only need a payment method once you decide to stay.