Contact

How can we help?

How can we help?

Whether you're evaluating Orion, troubleshooting a deployment, or just have questions — we're here. Pick the right path below.

A work team around the desk

Quick links

⚡ Quick Install Guide →

📖 Browse Documentation →

🌍 Terra Docs →

🎫 Support

Fill out our form or email us at

support@juno-innovations.com

with your question.

Submit a ticket

Submit a ticket

Submit a ticket

🚀 Sales

See Orion in action with a personalized demo, or talk through how Juno fits your infrastructure — no pressure, no generic pitch.

Book a demo

Book a demo

Book a demo

Frequently asked questions

What are the minimum requirements to deploy Orion?
icon

Orion requires a minimum of 3 nodes for a development or POC environment, and 10 nodes for production. It's Kubernetes-native and runs on your existing infrastructure — on-premises, in a VPC, or hybrid.

How long does a typical Orion deployment take?
icon

Most environments are up and running within a single business day. Our professional services team offers installation packages if you'd prefer guided onboarding. Once deployed, workloads can be launched in under 60 seconds.

Does Orion work with our existing Kubernetes clusters?
icon

Yes. Orion is Kubernetes-native and sits above your existing clusters as an orchestration layer — it doesn't replace them. It works with standard K8s primitives and integrates without requiring changes to your existing workload definitions.

Can Orion run in an air-gapped or disconnected environment?
icon

Yes. Orion is designed for deployment in fully disconnected, air-gapped environments — including classified and government networks. This is one of Orion's core architectural differentiators. Contact our team for air-gapped deployment documentation and perpetual licensing options.

How does Orion handle Windows VM workloads?
icon

Orion supports Windows and Linux VMs through its KubeVirt adapter, enabling VM orchestration alongside containers through the same control plane.

Where does my data live? Does any of it leave my environment?
icon

Your data never leaves your environment. Orion is customer-hosted — the control plane runs entirely within your infrastructure, whether that's your data center or your own cloud VPC. Juno has no access to your workloads or data.

What are the minimum requirements to deploy Orion?
icon

Orion requires a minimum of 3 nodes for a development or POC environment, and 10 nodes for production. It's Kubernetes-native and runs on your existing infrastructure — on-premises, in a VPC, or hybrid.

How long does a typical Orion deployment take?
icon

Most environments are up and running within a single business day. Our professional services team offers installation packages if you'd prefer guided onboarding. Once deployed, workloads can be launched in under 60 seconds.

Does Orion work with our existing Kubernetes clusters?
icon

Yes. Orion is Kubernetes-native and sits above your existing clusters as an orchestration layer — it doesn't replace them. It works with standard K8s primitives and integrates without requiring changes to your existing workload definitions.

Can Orion run in an air-gapped or disconnected environment?
icon

Yes. Orion is designed for deployment in fully disconnected, air-gapped environments — including classified and government networks. This is one of Orion's core architectural differentiators. Contact our team for air-gapped deployment documentation and perpetual licensing options.

How does Orion handle Windows VM workloads?
icon

Orion supports Windows and Linux VMs through its KubeVirt adapter, enabling VM orchestration alongside containers through the same control plane.

Where does my data live? Does any of it leave my environment?
icon

Your data never leaves your environment. Orion is customer-hosted — the control plane runs entirely within your infrastructure, whether that's your data center or your own cloud VPC. Juno has no access to your workloads or data.