Skip to content

Ways to buy & adoption

Two buying paths. One unified platform.

Every evaluation starts with a single scoped workload, clear Preflight options, and a direct comparison against your baseline—no long migration required.

Ways to buy

Choose fully managed or self-managed.

The full ORIQX platform—Workload Optimization, Preflight, Estimate, and Agent controls—is available through both buying options. Contact our team for a demo or to discuss pricing.

Option 01 · Operated by ORIQX

Full ORIQX platform

Fully managed

Use ORIQX as a fully managed service, running workloads on compute ORIQX provides and operates for you. You send workloads and get results; ORIQX chooses and manages the chips.

Who it suits

Teams that want optimized execution and pre-run visibility without provisioning or operating underlying hardware clusters.

What is included

  • Workload Optimization across ORIQX-managed CPU, GPU, TPU, NPU, and QPU capacity
  • Preflight run options before execution, Agent controls, and Estimate hardware-free scoring
  • Zero code rewrites; submit jobs directly and collect results

How it starts

Bring one workload and goal, review Preflight options, and run directly against your current baseline.

Option 02 · Inside your infrastructure

Full ORIQX platform

Self-managed

Deploy the ORIQX platform inside your own infrastructure: your data centre, HPC cluster, or your own cloud accounts.

Who it suits

Organizations running owned clusters, existing cloud commitments, or workloads governed by internal infrastructure boundaries.

What is included

  • Workload Optimization sitting cleanly beneath your existing queues and orchestrators
  • Preflight planning and Agent controls across your own pools, plus Estimate for capacity upgrades
  • Keeps scheduling policies, resource credentials, and execution within your accounts

How it starts

Start with one representative job in your cluster or cloud account, inspect Preflight plans, and verify against baseline.

Commercial scoping

How pricing is scoped without guesswork

Scoped to one representative job first

Start with a single bounded workload so time, cost, energy, and utilization gains are measured against your baseline before broader rollout.

Clean separation of compute spend

When self-managed, infrastructure execution stays directly under your own cloud and cluster billing; when fully managed, managed execution is bundled transparently.

Custom terms shared on contact

Speak with engineering to review node count, workload profile, self-managed licensing, or fully managed capacity options.

Explore full adoption phases and security control boundaries across both options.

Adoption path

Four deliverables from first job to rollout.

Evaluations start on one bounded workload with explicit deliverables agreed alongside your engineering team.

01Deliverable: Scoped brief

Workload brief

  • Representative workload & compute shape
  • Primary goal (time, cost, energy, or accuracy)
  • Agreed current baseline for comparison
02Deliverable: Options matrix

Preflight review

  • Predicted time, cost, energy & accuracy
  • Reachable CPU, GPU, TPU, NPU & QPU splits
  • Nothing runs until plan approval
03Deliverable: Verified run

Baseline comparison

  • Run it fully managed or self-managed
  • Observed elapsed runtime vs baseline
  • Utilization & data-transfer inspection
04Deliverable: Ownership guide

Rollout plan

  • Integration points with queues & agents
  • Goal thresholds & FinOps budget bounds
  • Next workload classes to expand into