Platform/Under the hood/Compute

Run where the mission requires.

Compute runs every study, twin and test a loop needs on infrastructure you control: cloud, private VPC, your own clusters or air-gapped enclaves. Placement is decided by policy, licences and cost before a job is scheduled, and your existing solvers come with you.

Placement resolutionResolving
Placement is a decision. Classification, licence, hardware and cost narrow the target before anything is scheduled.
What Compute does

One scheduler across the estate you already own.

Elidyne does not ask you to migrate. Placement, entitlement and data residency are resolved per job, across the environments your programme is allowed to use.

#CapabilityWhat it does
01Sovereign computeRun on infrastructure the customer controls, from cloud to classified enclaves.
02Placement by policyJobs placed by data classification, licence, hardware fit, cost and availability.
03Your solversCommercial, open-source and in-house codes under the same orchestration.
04Priced before it runsEach step estimated and reserved in compute units, so spend is visible against the plan.
05Private and air-gappedThe same product inside restricted and disconnected environments.
Placement

Placement is a decision, not a default queue.

Before a job is submitted, Compute resolves where it is permitted to run. Data classification, licence entitlement, hardware, cost and current availability all narrow the target before anything is scheduled.

  • Data classification and residency checked before scheduling
  • Licence entitlement checked against the solver and the environment
  • Cost, queue depth and hardware fit weighed against the deadline
Placement resolution
TargetControlEligible
Managed private / VPCJointYes
On-prem HPC clusterCustomerSelected
Partner GPU poolPartnerLicence gap
Air-gapped enclaveCustomerYes · offline
Solvers

Your solvers. Your licences. Your codes.

Commercial, open-source, in-house and Elidyne-native solvers run side by side. Bring your own containers, your scheduler integration and the decades-old code nobody is going to rewrite.

  • Commercial CAE, open-source and customer-owned codes treated equally
  • Existing containers, modules and job scripts wrapped rather than replaced
  • Licence servers and existing schedulers integrated, not bypassed
Solver ecosystem
Restricted estates

Offline is a first-class deployment, not an exception.

The same governed workflows run inside restricted and air-gapped environments. Models, policy and evidence stay within the boundary, and updates move through a controlled, reviewable channel.

  • Full capability inside disconnected enclaves
  • No outbound telemetry requirement for restricted deployments
  • Controlled update and model-transfer path with an audit record
Enclave status
  • Network postureOffline · no egress
  • Model bundlev7 · signed, verified
  • Solver licencesLocal licence server
  • Evidence storeInside boundary
  • Update windowScheduled · review required
Deployment

The same platform in every boundary.

Cloud, private VPC, customer on-prem and air-gapped or classified. Every loop, and the control pane around it, behaves the same in each; only the boundary changes.

ModeControlConnection
CloudElidyne-managedConnected
Private VPCElidyne + customerControlled
Customer on-premCustomerRestricted
Air-gapped / classifiedCustomerOffline
Deployment boundaries
On a real estate

Why this matters when the estate is messy.

01

Capacity is used, not stranded

On-prem clusters, reserved cloud and burst capacity are visible to one scheduler, so idle capacity stops being invisible.

02

Policy is enforced before submission

A job that may not run somewhere never lands there. The rule is applied at placement, not discovered in an audit.

03

The same product in every environment

Connected, private and air-gapped deployments run identical workflows, so a restricted programme is not a second-class one.

Sovereignty is not a deployment option we bolted on. It is the assumption we designed against.
Programmes in nuclear, defence and space do not get to choose convenience over control. Neither do we.
How it connects

Compute and the other five.

Six products, one control pane. Compute mainly carries Twin and Test; the rest of the loop is already connected when you need it.

  1. 01Measure
  2. 02Twin
  3. 03Test
  4. 04Limits
  5. 05Act
  6. 06Trace

Measure → Twin → Test → Limits → Act → Trace. Every product serves the same six steps, in every loop.

Start a mission

Bring us the system that matters.

Tell us what your estate really looks like: cloud, on-prem, partner capacity, licences and classification boundaries. That is the version we design against.