Operations DashboardHost control plane

Restricted infrastructure

One view of everything running on the droplet.

Use an authorized administrator account. The dashboard never exposes application secrets or private databases.

Host setup

Prepare this droplet

Run the included setup to install missing build tools, enable project workspaces, add standard deployment presets, and configure routing. Existing projects and their saved settings are preserved.

Hosting address

New projects get <site> under this domain. Existing project addresses stay saved as they are.

GitHub access (optional)

Leave blank to preserve the host's existing credential helper. A supplied token replaces this execution account's GitHub credential settings and is saved only in its private credential store.

New project

Connect, configure, deploy

Connect a GitHub repository using this host's saved access credentials.

Project

Project ID: generated from the name

Private repositories work when the host's GitHub PAT has access. Credentials stay in the host credential store.

Custom domain or existing-site path (optional)
Web address

Additional domains and subdomains (optional)

Add each complete hostname and choose the project service it should reach. A wildcard A record pointing to this server can cover new subdomains. Existing DNS records can override it. Deployment sets up routing and HTTPS and verifies every address.

Choose a destination service, including a backend configured below. Enable Redirect www to this address to include its www version automatically. Verify DNS checks both names; deployment sets up HTTPS and the redirect.

Backend services

The primary site's existing recipe stays in place. Add a backend using a runtime preset and its repository directory. All services build and restart together during the normal project deployment.

Use Environment variables below for the backend's saved credentials and application settings. They remain private and are shared by the project's runtime services. Review every hostname and choose its destination under Additional domains and subdomains.

Environment variables (optional)
Environment variables

Saved values are masked. Use Show to reveal a value, or type a replacement in its field. Save changes, then deploy to apply them. Add variables below using KEY=value. PORT, HOST, and HOSTNAME are assigned automatically. Use single-line values.

Advanced deployment settings

The ID defaults to your project name in lowercase, with dashes for spaces. It stays fixed after creation. Branch auto uses the repository’s default branch.

Automatic detection reads the repository to choose a static Vite, Node.js or Rust preset. The preset tells the host how to install, build and start your app. You can choose a host preset yourself for an unusual repository.

The dashboard checks that your app starts and the domain reaches the correct app. Leave / to check the homepage. A custom health endpoint, such as /health, is optional.

Project isolation

Leave the custom domain blank for an automatic hosted address. Create and deploy checks the repository, builds, configures routing and HTTPS, and verifies the site. Save only keeps deployment separate.

Schedule project deletion

Save these project changes?

Settings are saved now. If you change the domain, configure its DNS at your provider and verify it here before deploying. Deployment configures routing and HTTPS. Environment changes are also picked up if its service restarts.

Owner confirmation

Verify your authenticator

Enter the current six-digit code from your authenticator.

Owner confirmation

Redeploy this version?

Deployed commit

This rebuilds the selected deployed commit. Newer remote commits are not selected by this action.

Safe deployment control

Halt this deployment?

Release target

The controller will stop only before activation. If live files, migrations, or service verification have begun, the request will be refused and the protected rollout will finish normally.