Supported targets

A target profile records the facts needed to assemble and run a release on one class of computer. The target record adds the node identity, signing key, and ground route.

Target matrix

Target	Architecture	Integration	Isolation and acceleration
Development VM	arm64 or amd64	System image	hvt, runc, spt, qemu, firecracker, host
Raspberry Pi CM5	arm64	System image	KVM, hvt, runc
Raspberry Pi 4B	arm64	Daemon	KVM, hvt, runc
Xilinx VCK190	arm64	Daemon	spt, runc, Vitis AI, FPGA
NXP LX2160A	arm64	Daemon	KVM, hvt, runc, DPAA2
NVIDIA Jetson TX2i	arm64	Daemon	spt, runc, CUDA, TensorRT
Kalray Coolidge V1	amd64 host	Daemon	runc, MPPA, AccessCore, OpenCL
Innoflight CFC-400	arm64	Daemon	Profile-defined KVM and container backends

Inspect connected targets

List the targets available in the current context:

space target ls

Inspect the immutable profile and node-specific settings before deployment:

space target show <target>

The output includes the profile digest, architecture, available backends, reachability, node identity, and boot-signing custody. space deploy --plan copies those resolved facts into the release descriptor.

Connect an existing target

space target connect cm5-demo --profile cm5-dev \
  --signing-key keys/cm5-demo.pem \
  --operator-ca operator.pem \
  --deploy-cert payload.pem \
  --endpoint ipn:7.1 \
  --cla-address cm5-demo.local:4556 \
  --always-reachable

Use --tle with --station, or a fixed --contact-start and --contact-stop, for a target reached over scheduled contacts.

space target connect adopts an existing provider VM, Linux host, edge computer, or satellite. It binds the resource to an exact target profile, identity, signing custody, and transport without allocating infrastructure.

Use space target provision when Space should create or reconcile the resource and connect it in one operation.