Skip to content

Launch your first machine

This page takes you from nothing to a shell on a machine that stops itself when nobody is using it.

Sign in to the console and open your account.

In Machinery, open Machines and choose Add, or press A. New Machine lists what the launch will use as rows: Kind, Worker pool, Place, Region, Zone, Size, Auto-stop and Name. Give the machine’s assistant a first task in the prompt and choose Launch.

The machine shows in the list at once, launching, as a worker in the account’s default worker pool.

Open the machine from the list. Its page shows the ways in, and the ssh command to copy names the host the machine answers on.

Terminal window
deployport machinery list

If everything worked, the machine’s id is on its own row, and the console’s Machines list shows the same machine reading Online:

ID NAME HOSTNAME SUBSCRIPTION KIND AUTO-STOP
mach_kxpkzlq4qf dev-box ip-172-31-4-8 wpool_k3jx9q2m worker off

The ID is the machine’s id. Save it. SUBSCRIPTION is the worker pool it runs in, or - when its vCPU, memory and disk are its own. KIND is what it is for. AUTO-STOP reads on, off, or waiting for the AI harness to finish a task while Mecha is working.

Auto-stop ships off, so a new account pays for a machine that sits idle. Turn it on for every machine in the account, once:

In Machinery, open Settings, then the Power section, and turn on the idle alarm and auto-stop.

A machine with auto-stop on stops itself when it has been idle, and the bill stops with it. It warns you first, so you get a chance to keep it running:

Terminal window
deployport machinery autostop suppress <machine-id> 4h

An ssh session counts as use, so a machine you are working on is never stopped under you. Let a machine stop itself explains the timings, how to turn it on for one machine rather than the account, and how to give the machine back.

A stop keeps the disk and the next start brings the machine back:

Terminal window
deployport machinery stop <machine-id>
deployport machinery start <machine-id>

A terminate destroys the cloud instance. Nothing brings it back, so the command asks you to accept that:

Terminal window
deployport machinery terminate <machine-id> --yes

New Machine has a Place row. Choose it and pick Deployport Compute or UCE, then a region and a zone inside it.

If the launch or the shell did not work, Machine and ssh failures names the cause.