Dashboard Guide

Everything you do in Cloady — sign in, create a workspace, deploy and manage applications — happens at cloady.com. Each task below is a numbered procedure, with every button, tab and selector you click in bold.

New here? Start with Getting Started, or skim Core Concepts for the vocabulary.

1. Signing in

1. On cloady.com, click Sign in to open the sign-in page. There are no passwords, and signing in and signing up are the same form.
2. To use a social identity, click Continue with GitHub or Continue with Google.
3. If your company has set up single sign-on, click Continue with SSO, type your Work email and click Continue with SSO. You sign in at your company's identity provider and join its workspace as a developer.
4. Otherwise type your Email and click Email me a code, then type the 6-digit code from that email (pasting it works too). It works once and expires after 15 minutes; after 5 wrong tries, wait 15 minutes or use another way. An email Cloady hasn't seen before gets a new account.
5. If you turned on two-factor sign-in, enter the 6-digit code we text you and click Verify & continue. This happens however you signed in.
6. Every account needs a verified phone. If yours isn't verified, the sign-in page asks for it next: enter your number, click Text me a code, type the 6-digit code, click Verify & continue. One account per number, and nothing else in Cloady works until this is done.
7. You then land on your workspace list, or your last workspace.

You can also start from the deploy field on cloady.com before signing in: pick a template, a repository, an image or a folder and configure it there. Deploy turns the card into the sign-in form without leaving the page — GitHub, Google and SSO open in a small window that closes itself, and the email code is typed right in — and once you're in, the deploy carries on with everything you set, in a new workspace named like the one shown in the app's address.

2. Creating a workspace

A workspace holds your applications, your team and one subscription. It lives at cloady.com/w/{slug}.

1. Click the WORKSPACE button in the top-left of the TopBar, then + New workspace.
2. Type a Name (e.g. Acme Inc). The URL preview updates below the field; if that name is already taken, Cloady adds a suffix and tells you.
3. Optionally upload an Icon in the modal header. Colors aren't chosen by hand — the gradient comes from the icon, or from the name if you don't upload one.
4. Click Create workspace. Creating one costs nothing; the modal shows the free allowance every workspace gets.

One subscription covers the whole workspace, and you can deploy to any region straight away. What it pays follows what its apps declare — see Capacity and price — and a workspace whose apps fit inside 0.5 vCPU, 1 GB of RAM and 5 GB of SSD pays nothing.

3. Touring the dashboard

The dashboard is one screen: a TopBar, the workspace header with pool stats, and the Applications grid below.

1. The TopBar, left to right: the cloady logo (home), the WORKSPACE switcher with your monthly price on a badge, the region selector (globe + region code), and the environment selector (colored dot + PRODUCTION / PREVIEW / DEVELOPMENT).
2. Click the region selector to switch regions: Deployed groups the ones you already run something in, Available the rest. Every region listed is deployable.
3. Click the environment selector to switch environment. It filters the grid and scopes the next install. Both selectors live in the URL, so dashboard links are shareable: /w/{slug}/{region}/{env}.
4. Use the Search applications… box (or press ⌘K) to filter the grid by name.
5. Also on the right: the Terminal, Files, Database and Git tool buttons, the Settings gear, New application, and your account avatar menu.
6. In the workspace header, read the live pool meters — cpu, ram, disk — and the apps / running counts. Quick links Invite, Billing and Settings sit to the right.
7. Below, Applications lists every app in the selected region and environment. Filter with All / Running / Stopped, reorder by Name, Status, CPU or Memory, and toggle Expand for cards with live detail. The dashed Add application card is a second way in.

4. Installing an app

1. Check that the environment selector points where you want to deploy. An app runs in exactly one region and one environment, and both are fixed once it exists.
2. Click New application in the TopBar, or the Add application card in the grid.
3. Use the field at the top of the modal. Paste a GitHub repository URL, type an image name such as nginx or ghcr.io/acme/api:1.4, type a registry such as docker.io/ to browse popular images, or type to search the templates (WordPress, Postgres, …) listed below it; you can also drop a folder or a docker-compose.yml onto it. Click a row, or press Enter for the highlighted one.
4. The field turns into the app's card. At the top: the app's name (edit it there — the address beside it follows), its monthly price, and the deploy button. Below it, Source and Services show what Cloady read from your source, and Settings lists what you can change before deploying. Click a row to open it, and press Esc or Done to come back:
   • Resources — scale CPU and memory above or below the template's defaults.
   • Payment method — shown when this app takes the workspace past its free allowance. It names the card that will be charged. The workspace owner can add a card right there; it becomes their account's default card, or replaces the workspace's own card if it has one. If there's no card on file, Deploy asks for one as an extra step and carries on by itself once you save it.
   • Region — where the app runs. Every region costs the same.
   • Domains — the app's own cloady.io address is always on. Add your own domain here exactly as in app settings; Check DNS tells you whether its records already point at Cloady.
   • Managed backups — daily snapshots with 7 restore points, for 20% on top of this app's share of the bill. Shown when the app has volumes.
   • Environment — the app's variables. Templates list the ones they need and generate passwords for you.
   • Build — for repositories and uploaded code: branch, root directory, redeploy on push, and the build and start commands (leave those empty and Cloady detects them).
5. Press Enter or click Deploy. Cloady builds the app, gives it a hostname with HTTPS already working, and boots it.
6. The card shows the deploy as it happens, and any generated passwords or keys stay available under app Settings → Environment.

Your app's address is the app name, a short code, and the workspace name:

my-blog-k7q2v9ze-acme.cloady.io

Outside production the environment is part of it too: my-blog-k7q2v9ze-acme.preview.cloady.io.

If the workspace stays inside its free allowance, the app launches with no charge. Beyond it, the card on file is charged for the rest of the month. With no card on file, Deploy asks for one first in Payment method; a declined card fails the launch with payment_required, and Use another card takes you back there. Or make the app smaller.

5. Managing an app

1. Click an app card in the grid to open its detail view, or use the inline controls on the card.
2. Use the lifecycle buttons in the header: Start boots a stopped app, Stop shuts its containers down and keeps the data, Restart restarts them, Open opens the public URL in a new tab.
3. Click Settings for the App settings modal:
   • General — Name, Slug (lowercase letters, numbers and dashes, up to 24 characters), the fixed Region, and for repo-backed apps the branch selector, the Auto-deploy toggle and preview-branch tracking.
   • Services — the containers this app runs, each with a terminal button.
   • Volumes — persistent storage. It survives restarts, redeploys and stops; only deleting the app removes it.
   • Resources — current CPU / memory / disk usage, CPU and MEMORY scale sliders (0.25× to 4×), and per-volume growth. Volumes can grow but never shrink. A change that needs more than the workspace subscribes to shows what it adds per month and a Review price button; Save unblocks once the capacity is bought.
   • Environment — the app's variables. Secrets stay hidden until you reveal them, and you can drop a .env file onto the panel to import many at once. Changes take effect on the next deploy.
   • Deployments — every deploy with its build logs, a deploy button, and rollback on earlier successful ones.
   • Domains — the built-in hostname and any custom ones (next section).
   • Backups — the automatic emergency snapshot, plus daily snapshots with 7 restore points on any workspace with paid capacity. Each has a Restore button, and restoring replaces the current data with the snapshot.
   • Logs — a live tail of your containers' output.
   • Danger zone — Stop application, Transfer application to another workspace in the same region (data kept, about 30 seconds of downtime), and Delete application.

Renaming is safe; deleting is not. Change Name in General whenever you like — the address follows the name, and custom domains keep working. Editing Slug yourself stops it following the name from then on. Deleting an app permanently destroys its services, storage, variables, domains and deploy history — never delete one in order to rename it. Deletion makes you type the app's slug to confirm.

6. Adding a custom domain

1. Open the app, click Settings, then the Domains tab.
2. The BUILT-IN hostname at the top is the cloady.io address the app already answers on, with HTTPS.
3. Type your hostname (e.g. app.yourdomain.com) in the add row and click Add domain. To send visitors somewhere else instead, tick Redirect to another host (308) and fill in the target first.
4. Under DNS configuration, pick a method with the toggle:
   • CNAME — the default for subdomains. Add the single shown CNAME record at your DNS provider.
   • A / AAAA — for an apex/root domain, which cannot be a CNAME. Add the shown A (IPv4) and AAAA (IPv6) records.
5. Use the copy buttons to grab exact values, then create the records at your registrar.
6. Once DNS resolves, Cloady gets the certificate for you; the per-domain status moves queued → pending → issued. Still not issued after a few minutes means the record isn't pointing at Cloady — recheck it at your registrar.

7. Workspace settings & changing capacity

1. Click Settings (the gear in the TopBar, or the header quick link) to open the workspace Settings modal. Tabs: General, Members, Single sign-on, Billing, Integrations, Import, Danger zone.
2. Open Billing. The cards at the top show THIS MONTH (what has been invoiced this period), DUE TODAY (anything still outstanding) and NEXT MONTH (what renewal will cost). One subscription covers the whole workspace — there is no per-region billing.
3. Subscribed capacity lists CPU, RAM and SSD with the free allowance applied to each and the monthly total. When your apps need more or less than you subscribe to, a row appears with Add capacity or Reduce.
4. Either button opens a confirmation showing the old and new monthly totals, the amount due today and the card that will be charged. Increases are charged immediately and only take effect once payment succeeds. Decreases start at your next renewal, so you keep the capacity you already paid for.
5. Workspace card overrides your account default for this workspace alone. Leave it empty to use the account default, shown underneath.
6. To invite teammates, open Members and add them by email, or use the Invite quick link in the workspace header.
7. To let your company sign in through its identity provider, open Single sign-on (workspace admins only). Create an OpenID Connect app at your provider (Okta, Microsoft Entra ID, Google Workspace, Auth0, Keycloak…) with the Redirect URI shown, then fill Email domain, Issuer URL, Client ID and Client secret and click Save. Add the DNS record it shows as a TXT record at your DNS provider and click Check DNS. Once it reads ACTIVE, anyone your provider signs in with an email at that domain joins the workspace as a developer.
8. Integrations connects GitHub so you can deploy private repos. Danger zone holds Delete workspace: you type the workspace slug to confirm, and every application in it, all their data and all their domains are permanently destroyed.

8. Account & API tokens

Personal access tokens authenticate the CLI, the API, the Terraform provider and the MCP server as you, across all your workspaces.

1. Click your account avatar in the top-right of the TopBar, then Account settings. Tabs: Profile, Security, Notifications, API tokens, Billing, Danger zone.
2. Open the API tokens tab and click + New token.
3. Give it a Name (e.g. CLI · macbook), choose a Scope (Full access, Deploy only or Read only) and an Expiry (No expiry, 30 days, 90 days or 1 year). Click Create token.
4. The cldy_ secret is shown once — click the copy button to save it, then click Done. It cannot be retrieved again.
5. Use the token as a bearer credential for the CLI / API / MCP. To kill a token, click Revoke on its row.