Who decides
1Jonas takes over IT administration.
Svenja Hartmann registered Nordlicht Digital and is its owner. Jonas Petersen, her technical lead, gets the IT administrator role, invited by his e-mail address. That is a change: a proposal the portal lays out in full beforehand and that an entitled person consents to. Here that is Svenja, with her passkey, a sign-in by fingerprint, face or security key. Jonas sets up his own first passkey through an invitation. So that Jonas may also consent to orders that cost money, Svenja accepts the delegation framework once.
2The outside accountant joins by invitation.
Nordlicht's books are kept by Ingrid Lorenzen, from outside, in an office of her own. Svenja appoints her to the Finance role by her e-mail address, again as a change with a passkey. A time-limited invitation then waits for Ingrid, with a secret, a kind of one-time code. The portal shows it to Svenja exactly once, and Svenja passes it on to Ingrid by phone.
3Ingrid redeems the invitation.
Ingrid opens the invitation page, enters the username and the secret and sets up her passkey. The first passkey created in the invitation counts as confirmed, and only now does her role take effect. Finance on gh0stcloud means credit, payment, invoices, monthly limits and approving costs. Apps, data and roles are not part of it.
One project per client
4One project for the agency, one per client.
The agency and each client have a project of their own: nordlicht for the agency itself, moewe for the Mรถwe coffee roastery and brise for the Brise sailing school. For the Theater am Fleet, Jonas now creates fleet. A project is a firm boundary: a connection between two projects exists only with a grant, the permission of the project that offers something. Merle Hansen runs the client work and becomes project admin in the three client projects by invitation, one change per project, each consented to by Jonas.
5Every client project has a monthly limit.
Ingrid keeps an eye on costs, with a monthly limit per project: a ceiling for the month's net cost. The agency's limit only notifies; the clients' limits hold new orders that cost money from 100%. Whatever already runs keeps running. Setting or changing a limit is itself a change that only finance or an owner consents to.
6The apps of the agency and of its running clients.
Jonas orders the Managed Apps from the catalog, apps that gh0stservice runs for the agency: design and prototyping, customer relationships (CRM), project management and Share notes securely. The client projects get web analytics for the coffee roastery and two apps for the sailing school: status pages and monitoring, plus web analytics. Each order is a change of its own with a passkey. A new account has room for three Managed Apps, so Jonas asks for a higher limit, and gh0stservice decides the request.
7Malte works in the theatre's project only.
The theatre's new website is built by Malte Johannsen, a freelancer. Jonas gives him the Developer role by his e-mail address, in the fleet project only. There Malte connects his Git repository, where the code lives, and the platform delivers the website from it. He also gets at the project's secrets, its passwords and keys: his role reaches exactly to the edge of this project.
Proposal and consent
8Jonas's AI assistant proposes a change.
Jonas works with an AI assistant such as Claude Code. It uses gh0stcli, gh0stcloud's command-line tool, through MCP, an interface made for such assistants. Jonas asks it for a status page and web analytics for the theatre's new website, and the assistant turns that into a change and hands Jonas its link. It cannot apply the change: only a person consents, with their passkey in the portal.
9Over the limit, the change waits for finance.
The change's page shows everything before anyone consents: the two apps in the fleet project, the monthly cost and the theatre's monthly limit, which would then be exceeded. At the top it says that an agent proposed the change for Jonas. Jonas consents with his passkey. Because the limit holds orders, approval by finance is still needed, and until then the change waits.
10Ingrid approves, then it is applied.
Ingrid sees the waiting change, checks the cost and the limit and confirms the approval by finance with her own passkey. The approval covers exactly this change; the limit stays as it is. Only now does the platform apply the change, step by step. Each app is handed over only after its first backup and a restore test, in which a backup is actually played back.
Sharing and project end
11Credentials for clients: a link that expires.
Credentials, meaning sign-ins and passwords, that the theatre needs from Nordlicht go out through the app Share notes securely. It is a pastebin based on PrivateBin: a note goes out as a link. The link expires after the time Merle picks when she creates it.
12Project end: deleting needs IT administration.
The sailing school's season is over, and the brise project ends. Merle proposes removing its two apps, each as a change of its own. Removing deletes an app with its data, so only an IT administrator or an owner consents to such a change. Project admin is not enough for that, so Jonas consents to both with his passkey.
13Every client project on one map.
In the environment, Jonas sees on one map, per project, the apps, their connections and the grants between projects. Nordlicht's client projects sit side by side, each on its own, with no connection or grant. The brise project has no app left.
Nordlicht Digital is a made-up example.