How the platform is built
The layers underneath your application, and who operates each one.
This page is for readers who want to know what sits under their application before they trust it with something important. Nothing here is required reading to deploy, Start here covers that.
gh0stcloud is built so that three things stay separate: what you ask for, what is allowed, and what is actually running. Keeping them apart is what lets us operate the platform without taking control of your application, and lets you change your application without being able to destabilise the platform.
The four layers
| Layer | What it does | Who operates it |
|---|---|---|
| Portal | Where you see your applications, costs, and status, and where you request changes. | gh0stservice |
| Platform API | Decides what your account is allowed to do, and records the answer. Every change is checked here. | gh0stservice |
| Git | Holds the desired state of your application. Your commits are the record of what you asked for. | You |
| Runtime | Your running workloads, their namespaces, network rules, storage, and monitoring. | gh0stservice operates it; your application defines it |
Why it is arranged this way
You never need cluster admin. Everything you can legitimately do is reachable through the portal, Git, and gh0stcli. That means a mistake in your application cannot reach anyone else's, and a compromised laptop cannot become a compromised cluster.
Git is the audit trail. Because your application's desired state lives in your repository, "what changed and who approved it" is answerable from your own history rather than from our logs.
Checks happen before changes apply, not after. A commit describes what you want. The platform decides whether your account may have it, and only then does the runtime change. A repository cannot grant itself more than your account already has.
The portal shows state; it does not hold it. What you see is a view of what the platform actually decided and what is actually running.
What this page does not promise
This describes the shape of the product, not its internals. Component versions, internal service boundaries, and API details change as we operate the platform, and that is normal. It does not change what you can do or what you pay.
For anything you need to rely on commercially, your contract and your current support agreement are what count, not this page.