Coming Soon

AcaysiaCORE

Simulation as a service. Four engines that today need a CUDA toolchain, a GPU and a working knowledge of each one's API — brought into a single browser application, with the hardware on our side of the wire.

Built for process engineers, control engineers, plant operators, and academics who want to run these models, not build them.

Request Early Access

AcaysiaRT 127 process models Rete plants with recycle AcaysiaDRT 3D spatial fields AcaysiaGEM vessel geometry one contract family AcaysiaCORE one surface, one login your browser
Four engines, four very different kinds of compute — a batched GPU runtime, a flowsheet marcher, a lattice-Boltzmann solver and a CAD kernel — behind one API, one job format and one set of charts.
The Engines

Everything, From One Tab

Each of these is real output from the engine that produces it — not a mockup of an interface. CORE is the thing that gets you to them without an install.

thousands of futures, one tick
AcaysiaRT — move a slider, watch an ensemble. Results are reduced to quantile envelopes on the GPU before they cross the network, so the interactive path stays fast without shipping raw tensors to a browser.
feed REACTOR DECANTER product 70% recycle overall conversion 0.4623 → 0.5961
Rete — wire a plant, turn its knobs. Build a flowsheet on a canvas, inspect the definition as plain JSON, then watch per-unit responses and steady-state settle as you change a duty.
every cell, its own state
AcaysiaDRT — submit a 3D run, get fields back. Where the other engines treat a vessel as one well-mixed point, DRT resolves it as a grid and marches every cell. Jobs are rendered on the GPU box and come back as fields and frames rather than a file you have to post-process.
Photoreal render of a process plant authored parametrically by AcaysiaGEM
AcaysiaGEM — shape the vessel, export it to the solver. Set the parameters, see the geometry in 3D, check the boundary regions, and send it to a DRT run — without a CAD licence or a meshing step in between.
Architecture

Where the GPUs Actually Sit

The browser talks to a control plane; the control plane mediates work through storage. The compute tier is egress-only — workers dial outward and nothing ever connects to a GPU box.

YOUR BROWSER charts · flowsheets · 3D CONTROL PLANE auth · jobs · session hub DATA PLANE specs · artifacts GPU worker · RT GPU worker · DRT worker · GEM HTTPS / WSS workers dial outward — nothing connects to a compute box
Batch work is claimed atomically from storage, so a worker dying mid-run means a peer takes over rather than a job lost. Interactive sessions hold an outbound socket and are stateless-recoverable — reconnect and re-run.
Read This First

CORE Is Not a Control Tool

This is worth stating before anything else, because the distinction is a safety boundary rather than a positioning choice. AcaysiaCORE is an analysis and exploration application. It runs simulations, shows you what they did, and lets you compare them. It does not touch a plant.

The planned desktop connector is read-only data acquisition — connect, browse, subscribe — so you can lay real plant behavior over a simulation and see where they diverge. There is no write surface, and its absence is enforced by test rather than by policy. Closed-loop control is the Acaysia control system, which is a separate product with a separate safety architecture.

Design Principles

How It's Built

Provenance

Trust tiers come from the engine

Every model in the catalog carries its validation standing — emitted directly from AcaysiaRT's own registry and T0–T5 scorecard, never hand-copied into a marketing table. If a model's evidence changes in the engine, it changes in the app.

Isolation

Compute never accepts connections

GPU workers dial outward to the control plane and claim batch work from storage. Nothing ever connects inbound to a compute box, and job artifacts are tenant-isolated structurally rather than by convention.

Durability

Crash anywhere, resume

Batch jobs are claimed atomically, with queue pointers that live until the job reaches a terminal state — so a worker dying mid-run means a peer takes over, not a job lost. Interactive sessions are stateless-recoverable: reconnect and re-run.

Contracts

Versioned schemas, drift-tested

The wire contracts are the source of truth, with JSON Schemas emitted from them and tested against drift. Interactive results and archived batch results share one shape, which is why the same chart component renders both.

Audience

Who It's For

Process engineers

Ask harder questions

Sweep an operating envelope instead of running one case at a time, and see whether a lumped assumption survives contact with a spatially resolved model.

Control engineers

Test against a fast plant

A model fast enough to sample thousands of futures per tick is a model fast enough to develop a controller against, long before anything touches hardware.

Operators

Compare plant to model

Overlay recorded plant behavior on a simulated run — read-only — and see where the real unit has drifted from the one on paper.

Academics

Reproducible by construction

A scenario is a versioned artifact. Runs carry the engine build they executed on, so a result is something a reader can re-run rather than take on faith.

Early Access

Want In Early?

AcaysiaCORE is in build and not yet generally available. If you have a process you would want to run through it — or a workflow it should support — we would like to hear about it while the shape is still being decided.

Email aias@acaysia.com, or use the contact form.

Contact Us