Skip to content
cloud
Sign in Start deploying

Self-hosted deployment control

Your servers. One clean control plane.

Cloud turns server setup, site installs, deployments, commands, and logs into one focused workflow—without taking ownership of your infrastructure.

01

Bring a server. Connect a repository. Ship.

cloud / production

live

Sites / api.cloud.test

Production

Status Healthy
Branch main
Last deploy 2m ago
Deployment finished

9f3c21a · Tighten health checks

18s

01:42:08 Fetching origin/main

01:42:10 Installing dependencies

01:42:18 Running deployment script

01:42:26 ✓ Deployment complete

CONTROL PLANE 01—05
SERVER PROVISIONING ZERO-FUSS DEPLOYS LIVE LOGS SITE COMMANDS API ACCESS

02 / PRODUCT

The useful parts.
Nothing between them.

Every screen is built around the next operational decision, from authorizing a server to reading the output of a deploy.

01

BRING YOUR OWN SERVER

Your infrastructure stays yours.

Authorize Cloud over SSH, then manage sites and access from one place.

02

DEPLOY WITH CONTEXT

See what shipped, when, and why.

Commit details, status, trigger, timing, and complete output stay together.

03

RUN THE WORK

Commands without the tab sprawl.

Run site commands and keep their output attached to the right site.

04

TRACE THE SIGNAL

Logs that stay close to the action.

Move from server health to application output without rebuilding the context in your head.

03 / WORKFLOW

From bare server
to a repeatable release.

  1. 01

    Connect

    Add a server and authorize its generated public key.

  2. 02

    Install

    Choose the repository, branch, domain, and deployment script.

  3. 03

    Ship

    Trigger a release and follow every step through to completion.

04 / PRINCIPLES

Less platform.
More control.

01

Clear ownership

Your servers, sites, and deployment records are scoped to your account.

02

Operational visibility

Status, output, logs, and history are designed to answer what happened next.

03

Useful escape hatches

API tokens and deploy webhooks keep Cloud part of your workflow—not the whole workflow.

05 / READY

Keep the server.
Lose the busywork.

Create your workspace and make the next deployment the calm one.

Start deploying