Creating an account

From creating the account to your first running application.

Getting started takes no sales call and no payment method. You create an account, receive EUR 15 in starting credit, and deploy your first application with it.

The five steps

  1. Create the account. Work email, name, organisation, billing country. No credit card, and no prior knowledge of Kubernetes or GitOps.
  2. Confirm your email. You get a mail, confirm your address and set your password. Your account is then active and the starting credit is there.
  3. Install gh0stcli. One command. See installing gh0stcli. Then you sign in through your browser.
  4. Connect your assistant. gh0stcli setup connects Claude Code or Codex to your account.
  5. Describe the goal. Tell your assistant what should run. There is an example repository to start from; if you want to use your own, it walks you through connecting it.

Getting from step 1 to a running application is usually a matter of minutes rather than days.

What the starting credit covers

EUR 15 pays your first invoices. That is enough to try the platform with a small application and take your time working out whether it suits you.

The portal shows your balance and what has accrued at any point. What happens as the balance runs low (and why nothing happens at all once a payment method is on file) is on what gh0stcloud costs. Where the account stands at any moment (trial, full account, attention) is one line on the dashboard and is explained on account phases.

Once the first application is running

After that, day-to-day is manageable. New versions ship through Git. The portal shows state, cost and your balance. You add domains, network access, storage and databases when you need them.

You are responsible for your application and for what gets released. We operate the platform underneath, keep it current, and make sure environments stay properly separated.

If you would rather not do this yourself

Then we take on an agreed part of it. What that includes (which applications, how releases are approved, what is covered for updates and incidents, which response times apply) is settled in advance and written down.

The comparison of both routes is under operating models.