Skip to content

Transforming High-Performance Workflows

Orion Logo Orion Logo

Orion is a customer-hosted unified compute plane. It runs GPU and CPU-only workloads, as containers or VMs, from one system, in your own environment: on-premises, in your own cloud account, or air-gapped. You run Orion. Juno never hosts it, and nothing phones home.

Why teams run Orion

Enterprise on-premises GPU utilization sits at 10–15%. The hardware is paid for and the capacity is there. Orion slices GPUs so several workloads share one card, and it schedules containers and VMs from the same cluster, on your own hardware or in your cloud account. Teams typically get 2–4× more capacity from the hardware they already own, and users get an environment in about 60 seconds without filing a ticket.

Built on Orion

  • Kindwell Solutions. Kindwell built a supplier-sourcing Hermes Agent on Orion for Undersun Premium Suppliers. The full engagement took 9 days, down from an estimated 15 to 18.
  • Skid Slayer. Kindwell built a unified business dashboard inside an Orion Workspace. Environment provisioning went from 5 to 8 days to the same day, and the full build took 13 business days instead of 22 to 28.

What you can do with Orion

  • Run containers and VMs side by side. Containers and KubeVirt VMs share one scheduler, one GPU pool, and one set of admin tools. On AWS, Crossplane lets you launch EC2 instances from the same console.
  • Launch Workspaces in a browser. Users pick what they need and get a running environment in about 60 seconds. No YAML, no ticket queue.
  • Slice GPUs. Orion configures GPU slicing so many users share one GPU. See GPU Operator.
  • Install apps from one catalog. Orion Apps powered by Terra has 50+ official plugins, and you can install your own Terra-compatible Helm charts.
  • Run VMs next to containers. KubeVirt is released and managed from the same compute plane.
  • Manage infrastructure with Crossplane. Crossplane keeps your infrastructure configuration enforced continuously, so cloud and on-premises resources are declared and deployed the same way.
  • Bring your own scheduler. Install your own scheduler or another Kubernetes-compatible controller.
  • Automate with the API. Orion is API first, and it has an MCP server so your AI agents can work with Orion. See MCP Server.
  • Sign in with your identity provider. Orion supports Google, AWS Cognito, Microsoft Entra, and LDAP or Active Directory, including LDAPS with your own certificate authority. Groups map to roles, and every workload runs as the user's own UID and GID. See Authentication.

The three layers of Orion

Layer What it does
Orion Admin Run the fleet from one console. Build the menu once: workspaces, nodes, mounts, and identity.
Orion Workspace Launch workstations in a browser. Users get isolated, per-project environments.
Orion Apps Install tools from one catalog. Powered by Terra.

Helios, Juno's containerized workstation, runs on Orion. See the Helios documentation.

Where Orion runs

  • On-premises, bare metal, and air-gapped. Air-gapped installs are supported. There is no separate air-gapped version, so connected and disconnected clusters run the same Orion. See Air-Gapped installation.
  • AWS and CoreWeave. Orion has been deployed on both.
  • Your cloud. Running on Azure, GCP, or another cloud? Feel free to try it. Orion uses standard Kubernetes primitives, so most environments need only minor tweaks. Tell us how it goes at support@juno-innovations.com.

Orion supports clusters that Orion installs.

Who uses Orion

Get started

Want to try Orion on your own hardware first? Start a Proof of Value.

Breakthroughs run on Juno.