Dashboard Guide

Everything you do in the Cloady control plane — sign in, create a workspace, deploy and manage apps — happens at cloady.com. This guide walks each task as a numbered procedure, with every button, tab, and selector you click in bold.

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

1. Signing in

1. Go to cloady.com/login.
2. To use a social identity, click Google or GitHub at the top of the form.
3. To use a password instead, fill Email and Password, optionally tick Keep me signed in for 30 days, then click Sign in.
4. No account yet? Click Create an account and register, or follow a magic-link / invite email if a teammate added you.
5. After auth you land on your workspace list (or straight into your last workspace).

Screenshot coming soon.

2. Creating a workspace

A workspace is your tenancy unit — identity, members, and a resource pool. It lives at cloady.com/w/{slug} and carries a gradient identity.

1. Open the workspace switcher: click the WORKSPACE button in the top-left of the TopBar, then click + New workspace (or use the create entry on an empty workspace list).
2. In the Create workspace modal, type a Name (e.g. Acme Labs). The Slug preview updates live below the field; if it’s taken, Cloady auto-suffixes it.
3. Optionally upload an Icon, or set the two-color Gradient with the COLOR A / COLOR B hue sliders.
4. Under Plan · resource pool, pick a tier — the free Hobby tier or a paid plan. The pool sizes (vCPU / RAM / disk) shown are what every app in the workspace draws from.
5. Click Create workspace. If the plan needs payment, you’re redirected to Stripe Checkout; on a free or pre-configured plan you land directly in the new workspace.

Creating a workspace also activates its first region — that’s where your apps will run.

Screenshot coming soon.

3. Touring the dashboard

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

1. Read the TopBar left-to-right — the cloady logo (home), the WORKSPACE switcher, the region selector (globe icon + region code + your tier badge), and the environment selector (colored dot + PROD / STAGING / DEV).
2. Click the region selector to switch regions. Active regions (ones this workspace pays for) sit at the top; Inactive ones show an activate badge — picking one opens the activation flow.
3. Click the environment selector to switch between prod, staging, and dev. This filters the app grid and scopes new installs — the URL carries both, so dashboard links are deep-linkable: /w/{slug}/{region}/{env}.
4. Use the Search applications… box on the right (or press ⌘K) to filter the grid by name, slug, or kind.
5. On the right of the TopBar: the Console button, the Settings (gear) button for workspace settings, the New application button, and your account avatar menu.
6. In the workspace header, scan the live pool meters — cpu, ram, disk, net — and the apps / running counts. Quick links Invite, Billing, and Settings sit to the right.
7. Below, the Applications section lists every app in the current region + environment. The dashed Add application card at the end of the grid is a second entry point for installing.

Screenshot coming soon.

4. Installing an app

In the UI you create an “application”; under the hood that’s an instance of a catalog Application or your own repo. See Core Concepts for the split.

1. Confirm the region and environment selectors in the TopBar point where you want to deploy — the install is scoped to both.
2. Click New application in the TopBar (or the Add application card in the grid). If the current region isn’t active yet, you’ll be prompted to activate it first.
3. At the top of the modal pick a source tab: From catalog, From GitHub, or Drop folder.
   • From catalog — search Search application types… and click an application type (WordPress, Postgres, …).
   • From GitHub — paste a repo URL and let Cloady inspect it (it auto-detects branch, build/start commands, and framework).
   • Drop folder — drag and drop a built folder to deploy a static site.
4. Click Continue (catalog) or Review (GitHub / upload) to advance.
5. On the Configure step, set a Display name (the public URL preview updates live), tick any Components checkboxes, and fill the required Settings prompts. Click Review.
6. On Review & launch, check the summary — TYPE, NAME, ENVIRONMENT, REGION, PUBLIC URL, and the USAGE footprint it reserves from the pool.
7. Click Launch application. Cloady builds, wires TLS, and boots the app.
8. The post-install view surfaces any install-time credentials once — copy them, then click Done — I’ve saved them. You can also find them later under app Settings → Credentials.

Screenshot coming soon.

5. Managing an app

1. In the Applications grid, click an app card to open its detail view (or use the inline controls on the card itself).
2. Use the lifecycle buttons in the detail header:
   • Start — boots a stopped app.
   • Stop — scales it to zero (data is preserved).
   • Restart — rolls the running pods.
   • Open — opens the app’s primary public URL in a new tab.
3. For deeper changes, click Settings to open the App settings modal. Its tabs:
   • General — display name and basics.
   • Services — per-container status and controls.
   • Resources — tune per-container CPU / RAM limits against the pool.
   • Environment — manage the app’s env vars (secrets are encrypted at rest).
   • Credentials — re-read install-time credentials.
   • Deployments — deploy history, build logs, and redeploys.
   • Domains — built-in and custom hostnames (see next section).
   • Logs — live log tail.
   • Danger zone — delete the app (purges its data).

Screenshot coming soon.

6. Adding a custom domain

1. Open the app, click Settings, then the Domains tab.
2. Note the BUILT-IN hostname at the top — that’s the auto cloady.io URL, always served on the wildcard TLS cert.
3. In the add row, type your hostname (e.g. app.yourdomain.com) and click Add domain. To 308-redirect to another host, tick Redirect to another host and fill the target before adding.
4. Under DNS configuration, pick a method with the toggle:
   • CNAME — the default for subdomains. Add the single shown CNAME record (@ → the built-in host) at your DNS provider.
   • A / AAAA — for an apex/root domain that can’t be a CNAME. Add the shown A (IPv4) and AAAA (IPv6) records.
5. Use the copy buttons next to each record to grab exact values, then create them at your registrar.
6. Once DNS resolves, Cloady provisions a Let’s Encrypt certificate automatically. Watch the per-domain TLS status — it moves queued → pending → issued.

Screenshot coming soon.

7. Workspace settings & changing plan

1. Click Settings (the gear in the TopBar, or the header quick link) to open the workspace Settings modal. Tabs: General, Members, Environments, Domains, Billing, Integrations, Danger zone.
2. To change plan, open the Billing tab. The cards at the top show your current PLAN, MONTHLY cost, and STATUS. Billing is per-region — switch the region selector first to bill the right slice.
3. Under Change plan, pick a tier in the picker, then click the Switch to … button (it’s labelled with the tier you chose, e.g. Switch to Team). Changes are prorated and billed to your card on file; a paid upgrade may redirect you to Checkout.
4. To invite teammates, open the Members tab and add them by email (or use the Invite quick link in the workspace header).
5. Domains lists every hostname across the workspace; Integrations connects GitHub; Danger zone holds workspace transfer and deletion.

Screenshot coming soon.

8. Account & API tokens

Personal access tokens authenticate the CLI, the API, 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 in the green panel — click the copy button to save it, then click Done. It can’t 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.

Screenshot coming soon.