Introduction

Cloady runs your apps so you don't have to run servers. Sign up, create a workspace, and deploy — a WordPress site, a Node API, a Postgres database. Builds, networking, HTTPS, logs and metrics come with it: the simplicity of a VPS with the convenience of managed deploys.

The mental model

A workspace holds your members, integrations and billing. Each app in it declares the vCPU, RAM and disk it needs — the limits in its compose file, multiplied by the scale you choose — and what the workspace pays follows the total.

You never pick a plan. The total is priced on four plans, and anything between two plans costs in between — see Capacity and price. Prices are the same in every region, and a workspace whose apps fit inside 0.5 vCPU, 1 GB of RAM and 5 GB of SSD pays nothing. Nothing is metered: you pay for what your apps declare, not for what they happen to use.

A new workspace can deploy to any region — Hillsboro, Nuremberg, Singapore or New York. A region is just where an app runs, chosen when you deploy that app; there is nothing to switch on first.

Workspace  —  members, integrations, one resource pool, one bill
 └─ Application  —  runs in one region, in one environment
     └─ Services  —  the containers the app is made of

Each application runs in one region and one environment — production, preview or development — and its name is unique within a workspace and environment. An app is made of one or more services (containers): a WordPress app bundles a wordpress service and a mysql service, and you can restart, scale or inspect each on its own. Every app gets HTTPS, a live log tail, metrics and a URL the moment it boots.

Renaming an app changes its URL, because the address follows the name. Renaming is also the safe move — never delete an app to rename it, because deleting an app deletes its data permanently.

One thing can stop a deploy, and the error says so:

• payment_required — the app would take the workspace past its free allowance and there is no card on file, or the card was declined. Add one under workspace Settings → Billing, or make the app smaller.

Three ways to deploy

• GitHub repo — connect a repo and Cloady builds and deploys your branch on every push.
• Drag-and-drop folder — drop a project folder from your machine; it's built the same way.
• Catalog — pick a ready-made application (WordPress, Postgres, n8n, Supabase and more) and install it.

All three work from the dashboard, or from your terminal with cloady deploy.

Two domains

• cloady.com — the dashboard: your workspaces, apps, logs, metrics, team and billing. A workspace lives at cloady.com/w/acme.
• cloady.io — where your apps are served. Every app gets a hostname there:

my-blog-k7q2v9ze-acme.cloady.io

That's the app name, a short unique code, and the workspace name. Apps outside production add their environment (my-blog-k7q2v9ze-acme.preview.cloady.io), and apps in some regions add the region the same way. You can also attach your own domain to an app — HTTPS is set up either way.

Where to go next

• Getting Started — create your first workspace and ship an app.
• Core Concepts — workspaces, plans and the pool, applications, regions and environments.
• Dashboard Guide — find your way around and manage your apps.
• API Reference — every endpoint, with a request playground.
• CLI Reference — deploy, tail logs and manage apps from your terminal.
• Terraform Provider — declare workspaces, apps, variables and domains as code.
• MCP Server — drive Cloady from an AI agent.