Skip to main content
Registering creates the model record on Reactor. You do it once per model; releases (image and weights pairs) are published against it afterwards. When the model is not registered yet, reactor model publish creates the record from your reactor.yaml and continues with the release. Pass --no-register to make publish stop with an error instead.

Register from your workspace

Run it from inside your workspace:
The CLI walks up from the current directory until it finds your reactor.yaml (stopping at the repository root) and reads your model details from it, so no flags are needed. Those details are the source of truth for everything Reactor knows about your model:
reactor.yaml
The success output prints the canonical model name and points at the next command:
The Name in the output, vendor/my-awesome-model, is your model’s full identifier on Reactor. It is the value commands take in a <model>:<release> argument. Inside a workspace you rarely type it: the commands read it from reactor.yaml for you.

Register without a workspace

For one-off invocations, pass the model name on the command line:
A short slug without the org prefix (--name my-awesome-model) also works; Reactor fills in your org.

Resources and accelerators

The accelerator your model runs on, and any CPU or memory overrides, all live under model.resources in reactor.yaml:
reactor.yaml
CPU and memory quantities follow Kubernetes conventions: The accelerator types Reactor accepts as gpu.type: The platform is authoritative for this list. Print the currently accepted values with reactor gpu ls (pass --refresh to bypass the local cache after a platform release adds a new accelerator). To change these settings on an existing model, edit reactor.yaml and run reactor model update.

Next

Publish a release

Build the image, push it, and upload weights.

Manage the model

Update the spec, list running instances, or delete the model.