Skip to Content
Introduction

Introduction

Cloady is a multi-tenant cloud PaaS. Sign up, create a workspace, and deploy containerized applications into one of several regions — each region is its own Kubernetes (k3s) cluster, provisioned and reconciled for you. The simplicity of a VPS with the convenience of managed deploys.

The mental model

A workspace is your tenancy unit — identity, members, integrations, and a single fixed resource pool (vCPU, RAM, disk, network) sized by your plan. Inside a workspace you activate Regions; activating one subscribes the workspace to a plan there and provisions a cluster slice. Then you deploy Applications into a region — each deployed copy is an instance that draws from the pool. Fill the pool with as many apps as you like, with no per-container math.

Workspace  (global: identity, members, pool, integrations)
 └─ Region  (activated by a per-region plan)
     └─ Application instances  (WordPress, a Postgres-backed API, a static site…)

An application is made of one or more services (containers). A WordPress app, for example, bundles a wordpress service plus a mysql service — you can restart, scale, or inspect each independently. Every service gets automatic TLS, a live log tail, and a URL the moment it boots.

Three ways to deploy

  • GitHub repo — connect a repo for build-and-deploy from your source, with one-click deploys.
  • Drag-and-drop folder — drop a build folder for instant static hosting.
  • Catalog — pick a ready-made application (WordPress, Postgres, and more) and install it.

Two domains

Cloady splits its surfaces across two TLDs (the Vercel vercel.com + vercel.app pattern):

  • cloady.com — the control plane. Marketing site, dashboard, auth, status — everything about managing Cloady. Your workspace dashboard lives at a path: cloady.com/w/{slug}.
  • cloady.io — where your apps are served. Customer apps get a dashed, single-label hostname:
<component>-<svcId>-<workspaceSlug>.cloady.io

So a WordPress instance named DailyFrog in workspace neptolab is reachable at wordpress-dailyfrog-neptolab.cloady.io. The pattern is single-label deep by design, so a single *.cloady.io wildcard certificate covers every workspace and app.

Where to go next

  • Getting Started — create your first workspace and ship an app.
  • Core Concepts — workspaces, regions, applications, instances, and the pool model.
  • Dashboard Guide — navigate the control plane and manage your apps.
  • API Reference — every endpoint, for the CLI and your own tooling.
  • MCP Server — drive Cloady from an AI agent.
Last updated on
Getting Started