Skip to content

Security & Control

Execution boundaries, stated plainly.

ORIQX keeps operational boundaries explicit: you choose where workloads execute, who approves each run, and which schedulers stay in control.

01 · Execution location

Fully managed vs self-managed

Choose whether ORIQX runs workloads on compute ORIQX provides and operates (fully managed), or whether the ORIQX platform runs inside your data centre, HPC cluster, or own cloud accounts (self-managed).

  • Fully managed: send workloads, collect results; ORIQX manages chips
  • Self-managed: deploy within your existing infrastructure and cloud accounts

02 · Pre-execution control

Preflight approval before spend

Preflight lays out candidate chip combinations with predicted time, cost, energy, and accuracy before dispatching anything.

  • Human teams choose manually or configure automated policy bounds
  • Nothing runs and nothing is spent until a plan is selected

03 · Zero-run pricing & stack fit

Estimate and existing orchestrators

Estimate inspects program math across chip profiles without hardware access, and Workload Optimization sits beneath existing schedulers and queues.

  • Estimate scores chip classes with zero execution
  • Existing identity, queue, and cluster policies remain yours

Boundary overview

Operational responsibilities side by side.

Control boundaryFully managedSelf-managed
Execution computeORIQX-operated CPU, GPU, TPU, NPU, and QPU infrastructureYour own data centre, HPC cluster, or cloud accounts
Pre-run approvalPreflight options reviewed before launchPreflight options reviewed under your internal policy gates
Queues & credentialsJob submission interface with managed chip allocationCredentials, queues, and orchestrators stay in your accounts
Unowned chip scoring (Estimate)Zero execution on candidate hardwareZero execution and zero access to external candidate hardware

Control checklist

Plain answers on control and approval.

Who starts a run, who approves the spend, and what stays under your control.

Who triggers and approves autonomous agent compute?

Your team sets the goal and budget boundaries; Preflight prices each spawned branch before child jobs launch.

Do we need to rewrite code or change cluster queues?

No. Applications stay unchanged and ORIQX works underneath your existing schedulers and orchestrators.

Does Estimate require credentials to hardware we are evaluating?

No. Estimate scores your program across ORIQX chip-class profiles with zero cluster access and nothing executed.

Do all ORIQX platform features work both fully managed and self-managed?

Yes. Workload Optimization, Preflight, Estimate, and Agent controls apply across both buying options.