Kuiper¶
Kuiper is Orion's workload orchestration service. Each workspace runs its own Kuiper alongside Hubble as part of Orion Workspaces, and Kuiper handles launching, managing, and shutting down the workloads in that workspace's namespace.
How Kuiper Works¶
Admins create workload templates in Orion Admin, built on plugins installed through Orion Apps. Kuiper reads those templates as its workload catalog. When a user launches a workload from Hubble, Kuiper deploys it into the workspace and tracks it through its lifecycle.
| Responsibility | Description |
|---|---|
| Launch | Deploys a workload from a template, applying the user's identity and any launch-time values. |
| Track | Reports each workload's resources and status, including Job phases and advertised interconnects. |
| Lifecycle | Handles shutdown, hibernation, auto shutdown, locking, and in-place upgrades. See Hubble workloads. |
| Actions | Runs resource actions such as restart and logs. See Resource Actions. |
| Sharing | Shares workload access with other users. |
Permissions¶
Anyone added to the kuiper group in Titan has access to:
| Access | Where |
|---|---|
| The Kuiper API | The Development page in Orion Workspaces. |
| Custom environment variables | The Advanced Settings when requesting a workload in Orion Workspaces. |
| Creating and editing workload templates | The workload templates page in Orion Admin. |
Managing Kuiper¶
- Restart: restart a workspace's Kuiper from its manage page. See Restart Workspace Services.
- Logs: read a workspace's Kuiper logs from the Orion Admin logs console. Kuiper only produces logs while the workspace is active.
API¶
Kuiper's endpoints are served under /kuiper in each workspace, including request to launch a workload and all to
list running workloads. See our API Getting Started guide and the
environment variables example. Kuiper also
provides an MCP server for managing workloads from AI agents.