# AcaysiaCORE > For the complete documentation index, see [llms.txt](https://acaysia.com/llms.txt); a single-file corpus of every page is at [llms-full.txt](https://acaysia.com/llms-full.txt). Every page in that index is served as Markdown: append `.md` to its URL or send `Accept: text/markdown`. Canonical: https://acaysia.com/core Simulation as a service. Coming soon. Part of the [Acaysia platform](https://acaysia.com/platform.md). 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. [Request early access](https://acaysia.com/contact.md) or email [aias@acaysia.com](mailto:aias@acaysia.com). ## One surface, one login ### Everything, from one tab. No install, no CUDA toolchain. 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. CORE is the thing that gets you to them without an install. - **Interactive session — [AcaysiaRT](https://acaysia.com/engines/acaysia-rt.md). 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. - **Flowsheet — [Rete](https://acaysia.com/engines/acaysia-rt.md#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. (Example: feed, reactor, decanter, product at 70% recycle; overall conversion 0.4623 → 0.5961.) - **Batch job, 3D — [AcaysiaDRT](https://acaysia.com/engines/acaysia-drt.md). 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. - **Parametric vessel — [AcaysiaGEM](https://acaysia.com/engines/acaysia-gem.md). 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 license or a meshing step in between. ## Analysis only ### CORE is not a control tool. 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 distinction is a safety boundary, not a positioning choice. - **Desktop connector (planned)**: Read-only data acquisition: connect, browse, subscribe. Lay real plant behavior over a simulation and see where they diverge. - **Write surface**: None. Its absence is enforced by test rather than by policy. - **Closed-loop control**: [The Acaysia control system](https://acaysia.com/index.md): a separate product with a separate safety architecture. Footage: refinery, aerial, day. Plant data, read-only. ## 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 side** — your browser: charts, flowsheets, 3D. - **Our side of the wire** — the control plane (auth, jobs, session hub), the data plane (specs, artifacts), and the workers: GPU workers for AcaysiaRT and AcaysiaDRT, a worker for AcaysiaGEM. ## 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](https://acaysia.com/engines/acaysia-rt.md) 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 and archived batch results share one shape, which is why the same chart component renders both. ## Audience ### Who it's for. Built for process engineers, control engineers, plant operators and academics who want to run these models, not build them. - **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. ## The platform 1. [AcaysiaRT](https://acaysia.com/engines/acaysia-rt.md) — Simulation runtime. 127 registered process models. 2. [Rete](https://acaysia.com/engines/acaysia-rt.md#rete) — Whole-plant flowsheets. Recycle included. 3. [AcaysiaDRT](https://acaysia.com/engines/acaysia-drt.md) — Spatial simulation. Lattice Boltzmann, full 3D. 4. [AcaysiaGEM](https://acaysia.com/engines/acaysia-gem.md) — Geometry. 18 parametric geometries. 5. [AcaysiaCORE](https://acaysia.com/core.md) — Simulation in the browser. Coming soon. ## Want in early? If you have a process you would want to run through CORE — or a workflow it should support — we would like to hear about it while the shape is still being decided. [Request early access](https://acaysia.com/contact.md) or email [aias@acaysia.com](mailto:aias@acaysia.com).