ORBIT and IONA, how they work together

IONext is built around two parts designed as one pair: ORBIT is the workspace where infrastructure, pipelines, and models are built and run. IONA is the layer that reads signals from all of it and explains what to do next.

What is ORBIT?

ORBIT is one canvas for creating VMs, assembling pipelines, and monitoring production health, without moving between pages. It covers:

• VM provisioning and pipeline assembly on the same canvas.
• Real-time production health across all infrastructure.
• Deployed models shown alongside the VMs and pipelines running them.
• Pipeline execution shown step by step, on the same canvas the pipeline was built in.
• Public or private status for every resource visible from the topology view, with firewall rules editable from the same place.

What is IONA?

IONA reads signals from the infrastructure, models, and pipelines running in ORBIT, explains what they mean, and recommends the next action. It covers:

• Recommending VM type and configuration for a given use case.
• Recommending the model that fits the use case, not the most talked-about one.
• Explaining production health changes the moment they happen.
• Flagging when a running model's behavior starts to shift from its baseline.
• Pointing to the failure point in a pipeline that has stalled or slowed down.
• Flagging exposed resources, such as a database reachable over a public IP.

How do the two fit together?

ORBIT without IONA is infrastructure with no layer explaining what it means. IONA without ORBIT has nowhere to run its recommendations. The two are used together: ORBIT displays and runs, IONA reads and recommends.

An example workflow (illustrative)

The scenario below illustrates how the two work together, not a specific client case study.

1. A team describes a use case to IONA, for example running a model for document extraction.
2. IONA recommends a VM configuration and a model that fits that use case.
3. The team builds it in ORBIT, on the same canvas where the recommendation appeared.
4. Once it's running, IONA monitors production health and flags changes as they happen, so the team doesn't need to check a dashboard manually all the time.

Who is ORBIT and IONA built for?

They are most relevant for systems integrators and AI-solution teams whose expertise is in building AI solutions, such as computer vision, document processing, or model fine-tuning, rather than in infrastructure sizing or day-to-day production operations. IONA closes that expertise gap so a smaller team can operate AI in production without hiring a specialist for every layer.

Learn more on the ORBIT and IONA pages. Teams can sign up and try it directly.