Skip to main content

Documentation Index

Fetch the complete documentation index at: https://inorbitinc.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

InOrbit uses a declarative configuration model where you define what your robots should do, not how. Each configuration kind represents a specific aspect of your fleet setup—from data ingestion to incident alerts to custom dashboards. Configuration objects follow a consistent structure: 
apiVersion: v0.1
kind: <KindName>
metadata:
  scope: account/<accountId>  # or robot/<accountId>/<robotId>
  id: my-config-id
spec:
  # Kind-specific fields
Use the InOrbit CLI to apply, list, and manage configurations.

​
Data & Monitoring

Data Sources

Extract robot data from ROS topics, key-value stores, or computed expressions into queryable attributes

Status Definitions

Define robot health status rules that flag problems based on data source values

Incident Definitions

Configure when to create incidents and how to notify operators

KPI Definitions

Aggregate fleet metrics for performance analysis and reporting

​
Robot Control

Action Definitions

Define commands that operators can trigger on robots

Mission Definitions

Create reusable mission sequences with waypoints, actions, and conditions

Mission Tracking

Configure how mission progress and performance are monitored

Traffic Management

Define traffic zones and rules for safe multi-robot navigation

​
User Interface

Dashboards

Build custom monitoring interfaces with widgets and layouts

Preferences

Configure UI defaults and widget behavior settings

​
Robot Configuration

Robot Footprint

Define the physical footprint shown on maps for collision visualization

Robot Camera

Configure camera feeds displayed in the UI

Spatial Annotations

Define named waypoints and map markers that missions can reference