Quickstart
Sign up, put a site online, add a database and your own domain, invite someone.
What it is
From a new account to a website with a database and its own domain, in the console, in about fifteen minutes. The steps are the ones the Get started list on Console home shows. Every step has the same thing as a command at the end of this page, for when you would rather type.
Sign up
Open the console and choose Register under the sign-in form, or go to /register. Two short steps:
- About you: whether you sign up as a company or as a private person or sole trader, your name, your email address and a password. A company gives its name; a private person's organization carries their own name. The Organization address is the part of your web addresses that names you, for example
hello.pixel-pi.apps.platform-development.deutschecloud.app. It is filled in from the name, you can change it, and it cannot be changed later. - Billing details: the name and address that go on your invoices, and the country. A company can add an EU VAT ID; without one, German VAT is charged.
Nothing is charged when you sign up. You pay for what you use, by the hour; the invoice comes at the start of each month and is paid by bank transfer. Prices are net, VAT is added on the invoice. See Billing.
Create account sends a six-digit code to your address. Type it on the same page; it is valid for 10 minutes, Send another mails a new one, and Wrong address? Change it sends it to the right one. You land on Console home, signed in.
Put a site online
On Console home, Put a site online, or Apps → Create app:
- Choose A container image, then From somewhere else, and enter
docker.io/traefik/whoami:v1.10. That is a tiny test site; your own image works the same way. - Give it a name, such as
hello, and set Container port to80, the port the image listens on. - Create and deploy. The summary on the right shows what it will cost per month at most, before you press it.
The first deployment creates the machine the site runs on, so it takes a minute or two. The app's page shows each step. When it says Running, the site answers at its address with HTTPS:
https://hello.<your organization address>.apps.platform-development.deutschecloud.appA compose file, or a Git repository the platform builds for you, works the same way; see Apps.
Add a database
On Console home, Add a database, or Postgres → Create database. Pick a name and the smallest size; the summary shows the monthly price. A single database is ready in about two minutes. It is private: your apps reach it, the internet does not.
Connect it to the site: open the app, Environment → Database, choose the database and Redeploy. The app then gets DATABASE_URL and the usual PG… variables with its own user and password. See Managed DATABASE_URL.
Use your own domain
Open the app, Domains → Add a domain you own, and enter it, for example www.example.com. Then make the name point at the site, in one of two ways:
- Your DNS stays where it is. At your DNS provider, create the record the Domains panel names: a
CNAMEfromwww.example.comto the app's address. A bare domain (example.com) gets anArecord to the address the panel shows. - Your DNS moves here. Create a hosted zone (DNS → Create hosted zone) and set the domain's nameservers at your registrar to the two the zone shows. See Delegate a domain.
The certificate is made as soon as the name points at the site, usually within a minute. The Domains panel says what DNS answers and why a certificate is still missing.
Set a budget and a way to pay
Billing → Budgets → Create budget: an amount per month, and an email when spending is about to pass it. Billing → Payment methods holds your bank details for paying invoices. See Billing.
Invite someone
Settings → Members → Invite member: their email address and a role. Viewer sees everything and changes nothing; Member creates and manages resources; Admin does everything except billing ownership; Billing sees costs and invoices only. They get an email with a link; each person signs in as themselves. Finer permissions: IAM.
Clean up
Everything in this guide is billed while it exists. Delete the app (its machine goes with it), then the database and the zone, each from its own page. To leave altogether: Settings → Danger zone → Close this organization; an organization with nothing left in it closes at once.
From the command line
The console serves a CLI made for its own API. On Linux or macOS:
curl -fsSL https://console.platform-development.deutschecloud.app/api/cli/install.sh | sh
dcloud logindcloud login prints an eight-character code and opens /activate in your browser; check the code and press Approve. The CLI then acts as you for 90 days (dcloud whoami shows who). The steps above, as commands:
# Put a site online
dcloud deploy apps create --name hello --builder image \
--image-ref docker.io/traefik/whoami:v1.10 --port 80
dcloud deploy apps deploy hello --wait
# Add a database and connect it (ids from `dcloud deploy apps list` and `dcloud rds instances list`)
dcloud rds server-types list
dcloud rds instances create --identifier hello-db --instance-class <a size from the list> --db-name hello
dcloud deploy database bind <app id> --db-instance-id <database id> --redeploy
# Use your own domain
dcloud deploy domains add <app id> --domain www.example.com
# Clean up
dcloud deploy apps delete <app id>
dcloud rds instances delete <database id>For a script or a CI job, give it an access key of its own: Identity → Access keys → Create access key. The secret is shown once; pass it as EWS_ACCESS_KEY=EWS1…:<secret> with EWS_API_URL=https://console.platform-development.deutschecloud.app. See Deploy from GitHub Actions.
Connect an AI assistant
Claude, Cursor, VS Code and ChatGPT can use Deutsche Cloud through MCP, with your permissions. In Claude Code:
claude mcp add --transport http dcloud https://console.platform-development.deutschecloud.app/api/mcpThen run /mcp, pick dcloud and sign in on the Deutsche Cloud consent screen. Other clients: Connect an AI assistant.
Next
- Words you will meet: Glossary.
- Keep what belongs together in a project, label it with tags, and see what it costs: Tags, saved views & topology.
- Deploy on every push: Deploy from GitHub Actions.
- Every command: CLI command reference.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| The code is not accepted | It expired after 10 minutes, or three wrong guesses used it | Send another, and type the newest code |
| The organization address is taken | Another organization has it | Choose another; it is checked as you leave the field |
| The app never becomes Running | The container port is not the one the image listens on | Set Container port to the image's port (80 for the test image) and redeploy |
ews: command not found after installing |
~/.local/bin is not on your PATH |
Add the line the installer printed to ~/.profile or your shell's rc file |
| The database cannot be connected to the app | The database is in another private network than the app | Create the database in the default network, which the app shares |
| The domain shows No record or Delegation not confirmed | DNS does not point at the site yet | Create the record the panel names, or finish the nameserver change at the registrar, then Re-check |