Deployment Overview
Deployment runs a model version in the cloud or on an on-site edge inference node to control a real robot. Each deployment creates a deployment record, and a running deployment is called a deployment instance.
Where: Model Deployment → Inference Deployment in the left navigation.
Deployment Types
| Type | Runs on | Best for | Prerequisites |
|---|---|---|---|
| Cloud inference | Platform compute | Quick validation and demos, with no local hardware | Target device is online |
| Edge deployment | On-site edge inference node | Long-term production and on-site operation with real-time requirements | All four pre-deployment checks pass |
Network and latency
Cloud inference depends on the network between the device and the platform, and latency affects control quality. Use edge deployment for latency-sensitive scenarios.
Deployment Workflow
Select model version → Select target → Pre-deployment checks → Submit → Instance running → Safety confirmation → Start inference → On-site validation1. Select a Model Version and Target
- Click New Deployment and select a model version. You can choose a model from completed training or a checkpoint model.
- Choose a deployment type:
- Cloud inference: select the inference device and compute tier.
- Edge deployment: select the edge node and the robot connected to it.
- Once you select a device, the page shows its name, model, SN, online status, and last heartbeat.
2. Pre-Deployment Checks (Edge)
| Check | Requirement |
|---|---|
| Hardware compatibility | The node's GPU memory and compute meet the model's requirements |
| Approved client | The NexCore edge client is installed and signed in on the node |
| Matching inference code | The client has synced the inference code for the model family |
| Disk space and network authorization | There is enough disk space for the model, and the node is authorized for network access |
If any check is missing, Submit Deployment is disabled and the missing items are listed.
Station Lite requires an external inference node
Station Lite doesn't include inference compute by default. Edge deployment requires an external inference node that meets the requirements.
3. Submit the Deployment
- Turn on NexBench evaluation if needed (off by default). The setting is saved in the deployment record.
- Click Submit Deployment. The platform validates the configuration, then sends the model and inference code to the node.
- Once the client finishes pulling them, the instance status changes to Running.
4. Safety Confirmation and Starting Inference
Before every inference run, the platform requires a safety confirmation:
- [ ] No one is within 1 m of the robot
- [ ] The robot's motion path is clear of obstacles
- [ ] The emergency stop is within reach and working
- [ ] The current model version matches the task
Inference starts only after every item is confirmed; cancelling means nothing starts. You can interrupt execution at any time with the emergency stop.
Deployment Instances
| State | Meaning | Available actions |
|---|---|---|
| Checking | The four edge checks are running | Wait |
| Deploying | The client is pulling the model and inference code | Wait, view logs |
| Running | Ready for inference | Inference test, view logs, restart, stop |
| Stopped | Stopped manually | Start again |
| Failed | The deployment failed; the existing stable version is unaffected | View logs, roll back, redeploy |
View logs: Instance details show recent log output, 200 lines by default and up to 5,000.
Restart: If the inference code or client misbehaves, click Restart to relaunch the instance with the same model version.
Failures and Rollback
- A failed deployment never replaces the current stable version, which keeps running.
- You can roll back to any earlier version in the deployment history.
- Failure records are kept for troubleshooting.
Inference Tests
Click Inference Test on a deployment instance or in Model Management, then select a model, device, test scenario, and number of trials (for example, 10) to evaluate the model quickly. Tests also require a safety confirmation.
Deployment Records
| Field | Description |
|---|---|
| Deployment ID | Generated by the platform |
| Model version | The deployed model, linked to its training job and dataset versions |
| Deployment type | Cloud / edge |
| Target device | Device name · SN, or edge node ID |
| NexBench | On / off |
| Status and timestamps | — |

