Getting started
1Mira Okafor opens a Starter account.
Mira picks the account type Company and enters company name, name, email and country, plus four consents. Payment details can wait. The link in the first email confirms the address, and starting credit lands on the account, valid for 90 days. A second email lets Mira set her password. The account costs a monthly base fee including VAT, plus the apps' usage and a platform share on top. As long as credit is left, it pays every invoice.
2After the install: two commands, then the assistant.
gh0stcli is gh0stcloud's command-line tool and comes onto the machine with Homebrew. With gh0stcli login, Mira signs in: the sign-in runs in the browser, and the session then sits in the operating system's keychain. gh0stcli setup --agent claude registers two MCP servers with Claude Code, the connections through which an AI assistant uses tools: one for the account and deployments, one for logs and metrics.
3First the setup check, then the work.
Mira gives Claude Code the starting prompt for an existing app. The playbook gh0stcli hands the assistant starts with a setup check: sign-in, local tools and a GitHub account, because the code and the builds live at GitHub. Mira signs in there once with gh, GitHub's command-line tool, and grants every permission the deployment needs: for repositories, workflows and packages, none for billing or payments. The sign-in to OpenBao, the secret store for passwords and keys, comes with the first project, because it holds per project.
From folder to image
4The assistant reads the code.
gh0stcli finds a Nuxt app on port 3000 in the folder, no Dockerfile yet, and an .env file whose secret values will move to OpenBao later. For the database, a PostgreSQL, Mira and Tom choose a Helm chart next to the app, a ready-made package for Kubernetes. That makes the backups theirs as well, because in self-service the customer runs the app and its data. Code and deployment settings go into two separate private repositories.
5Dockerfile and workflow, as a preview first.
gh0stcli proposes three files: a Dockerfile, the build recipe for a container image that runs without root rights, a .dockerignore and a workflow for GitHub Actions, GitHub's build service. Tom reads the preview along, and only after his yes does the assistant write the files. After a second yes the assistant creates the private app repository at GitHub and pushes. GitHub Actions builds the image and stores it privately in ghcr.io, GitHub's container registry.
A home on gh0stcloud
6A project, a role, a namespace.
The assistant creates the project terminfuchs. Only people with a role in a project reach its secrets and delivery, the owner included, so Mira assigns herself the project admin role in the portal. That is a change, and it runs only once Mira consents with her passkey, a sign-in by fingerprint, face or security key. The assistant then creates the namespace web, a space of its own with its own network rules, one app and its database per namespace.
7Secrets that bypass the conversation.
Mira signs in to OpenBao once for the project, again in the browser. gh0stcli then generates the secrets on Mira's machine: the database password, the app's session key and a deploy key, a key for the deployments repository alone. The values go straight to OpenBao, past the conversation with the assistant, and all that comes back is a receipt with path, version and key names. The private half of the deploy key then exists only in OpenBao. The token the platform reads the private image with is one Mira creates at GitHub and hands to OpenBao from a file.
8The project knows its repository.
The assistant creates the second private repository, gh0stcloud-deployments, and adds the public half of the deploy key there as a read-only key. It then connects the project terminfuchs to that repository, in the order project, key, connection. That way Flux, the platform's GitOps tool, can read the repository from the first moment. GitOps means the repository describes what should run, and the platform makes sure exactly that runs.
Going live
9Before the push: one door, one check, one estimate.
Terminfuchs sends booking confirmations through a mail service's HTTPS interface. Outbound traffic on gh0stcloud stays closed until a destination is allowed, so the assistant opens exactly one door: outbound HTTPS for this app. gh0stcli then builds the configuration locally and checks it against the platform's guardrails, such as containers without root rights, resources within the quota and secrets only as references to OpenBao. Finally the assistant estimates the monthly cost from the public price list.
10One push, and the platform follows.
Mira says yes to the push of the deployments repository. Flux fetches the new state and brings it into the namespace web: Terminfuchs from its image in ghcr.io and PostgreSQL from its Helm chart. The assistant compares the commit the platform reports with the one it pushed and checks that everything runs. With a token Mira creates at GitHub for the deployments repository alone, the workflow now records every new image there by itself.
11Live at its own address, with a certificate.
Terminfuchs answers at terminfuchs.k7q2m4xz.gh0stcloud.app, an address of the platform for this organisation. The platform sets up certificate, route and DNS record from the Ingress, the entry rule in the deployments repository, and renews the certificate by itself. Incoming traffic gets through only where a rule allows it, and outbound it stays at the one door. A domain of its own can follow later, after a review by gh0stservice.
12The assistant reads the logs itself.
Because Terminfuchs is here to stay, Mira adds a card as payment method, which lets her order gh0steye, once for the whole organisation: a Grafana of its own, the tool for logs and metrics, where only the organisation's data arrives. The order is a change with a passkey and is billed by usage. gh0stcli setup already registered the second MCP server for it. When Tom wants to know why a booking is stuck, the assistant reads the logs of Terminfuchs through exactly that server.
Part of the environment
13Terminfuchs joins the environment as an own app.
Until now Terminfuchs runs in its namespace, and the organisation's environment does not list it yet. The assistant describes the app in a score.yaml, the open Score format for workloads, and gh0stcli translates it offline into an own app for gh0stcloud. Through gh0stcli the assistant can only propose a change from it, and it runs only once a person consents with their passkey. Mira consents, and Terminfuchs appears in the environment, the map of every app and connection of the organisation.
14One rule for connections across projects.
Tom wrote erinnerung, a service for appointment reminders. It runs the same way in a project of its own, dienste, and offers an endpoint over HTTP on port 8080 that Terminfuchs is to use. Out of the box nothing connects across projects. Mira allows exactly one kind in the organisation's connection rules, web endpoints between own apps, again a change with her passkey.
15Two own apps, one grant between them.
In one change the assistant proposes to list erinnerung as an own app and to connect Terminfuchs to it. The new rule allows that, but projects stay firm boundaries: after Mira consents, the connection waits until project dienste grants it. Mira gives the grant in the portal, another change with her passkey. Only then is the connection ready, and only then does the network path appear, only from Terminfuchs to erinnerung and only on port 8080.
What stays
16What Mira and Tom now hold.
The code sits in their app repositories at GitHub, the deployment settings of both apps in a repository of their own, the secrets in OpenBao. Terminfuchs and erinnerung run as own apps in two projects, connected through a grant, and what both cost is shown in the portal per project. The two operate the apps and their data themselves, database backups included. Anyone who wants to hand that over gets custom operation under an order form. gh0stservice runs the platform underneath.
Okafor & Berg, the company behind the booking app Terminfuchs, is a made-up example.