Overview

The Space CLI builds your application into a signed SpaceOS image and runs that image on your computer. space deploy then ships the same image to a machine you connect, and SpaceOS on that machine checks the image before it runs it.

No installable release today

The Homebrew tap serves no working bottle yet, so these commands need a Space CLI you already have.

Updates on a payload computer

A payload computer runs your application for months with no one at the console. It reaches the ground only during a pass, which lasts about ten minutes at most in low Earth orbit.

An update that fails to boot therefore cannot be fixed by hand. The software has to arrive signed, and the board has to fall back on its own when a release is bad. Each boot stage checks the next before it runs it, as boot verification shows.

Build and run on your computer

space init writes a new project from a template. space build combines the project's services with the SpaceOS runtime image and signs the result. space run boots that image in a local VM, and builds it first when the project changed. The quickstart walks through all three.

Deliver a build

A target is a machine you deploy to, recorded on your computer by space target connect. Today a target is a VM on your Mac, a Raspberry Pi CM5 board or an arm64 Linux host, as supported targets lists. A payload computer in orbit is the target SpaceOS is built for, and the platform has not flown yet.

space build leaves every board-specific piece out of the image, so one built image serves every target. space deploy adds the board kernel and the device tree (the file that tells the kernel which devices the board has) for one connected target. It also adds the boot image signed with the target's secure-boot key, and it records the release.

space publish lists a signed build in the marketplace, the Space Store catalog at run.space where other teams can order it. The publishing chapter explains what a listing pins. space image verify checks the signed evidence on an image you received.

Observe a run

space status shows what is running, one row per service. space logs shows what a run printed.

Inspect what goes into a build

space show --sbom prints the software bill of materials for a project before it is built. Add --osv, as in space show --sbom --osv, to scan the same dependency closure against the OSV vulnerability database and print that report instead.

Where to go next

• The quickstart scaffolds a project and boots it.
• SpaceOS for Docker users maps what you know about images and containers onto SpaceOS.
• The CLI reference lists every command, option, and exit status. space COMMAND --help prints the same text for one command.