Cloud
An ODE cloud drive window over a cloud-pattern backdrop: a sidebar with Cloud selected, a file grid of project models and studies, and three recent documents. A fifth file, trajectory.study, is dragged in from outside, dropped into the grid, uploads, and the storage meter at the bottom ticks from 55 to 60 percent before the loop restarts.
What Cloud can do
Every engineering organisation eventually builds the same broken system: a network drive, a naming convention nobody follows, and a spreadsheet tracking which result belongs to which model. Cloud removes the category — models, runs, results and documents are addressable records in a project, not files in a folder.
What it replaces
A simulation result is not a file. It is a model revision, a parameter set, a solver configuration and an output trace — four things that only mean something together. Store them as files and the relationship lives in a filename. Store them as records and the relationship is queryable, diffable, and impossible to break by renaming.
Traditional
pack_v3.mo on a shared drive
ODE Cloud
A model record with version history, and every revision referenceable
Traditional
A results CSV, next to a spreadsheet that remembers the parameters
ODE Cloud
A run record carrying its parameters, its solver configuration and a pointer to the model version
Traditional
Models handed around as email attachments
ODE Cloud
Shared inside the project, with permissions and no copies
Traditional
“Which version produced this plot?”
ODE Cloud
Every plot points at the run that made it, so provenance cannot be lost
Capabilities
01
Addressable records
Models, runs, datasets and documents each carry a stable identifier — cite one from a Paper, and the link stays valid.
An ODE cloud window holding a short engineering document. A run is cited mid-sentence by its identifier, run/8f21c4; the citation lights, and the record it names resolves into a card over the page — the same run, the model revision it ran and the result it produced.
02
Version history
Every edit is a revision. Diff two model versions structurally, not as text, and see which equations actually changed.
An ODE cloud window listing a model's revisions. The second-newest joins the selection so two revisions are compared, and the structural difference between them arrives underneath: one component added, one removed, and two parameters moved from their previous values.
03
Shared workspaces
Real-time collaboration on one source of truth, with roles and review — no one works from a stale copy.
An ODE cloud window open on one drivetrain model. An editor moves onto a block and takes hold of it, a reviewer joins the canvas from outside, both appear in the window header, and a chip records three proposals already applied.
