Airliner wake lattice-Boltzmann LES
Data infrastructure for the physical world
The place where agents work on simulation, scan, and sensor data. Compute runs next to the data, and results stream to your engineers and your product.
Agents that answer engineering questions
On its own, an agent has to pull down hundreds of gigabytes before it can ask one question of a transient run or a lidar scan. On CoDim it inspects, probes, and compares the full data where it lives, then posts the answer to your team's scene.
How agents connect →
Where does wall shear peak in Run 42, and how does it compare with Run 41?
I'll look at both runs in the Mirror study project.
codim dataset_describe(Run 42)
8.2M cells, wall_shear up to 42.9 Pa on the front tires
codim filter_apply(wall_shear, region = mirrors)
Run 42 mirror peak 14.3 Pa, Run 41 16.5 Pa
codim scene_actor_set(Run 42)
Colored by wall shear, 0 to 8 Pa
codim view_camera_set
Camera on the left mirror
codim annotation_create(mirror peak)
Pinned at 14.3 Pa for the team
On the body, wall shear peaks on the outer face of the mirror housing at 14.3 Pa, 13% below Run 41. The scene is colored by it and the peak is annotated.
A cloud backend for 3D data
CoDim works with simulation, scan, and sensor data at full resolution, runs filters and analysis next to the data on cloud GPUs, and streams results to agents, browsers, Python, and your product.
Any physical world data
CFD and FEA solvers, AI surrogates, lidar and photogrammetry scans, and robot fleets.
Processed in CoDim
Filtered, probed, compared, and rendered on cloud compute, next to the data. The work runs once and every agent and person reuses it.
Delivered where you need it
Agents over MCP, engineers in a browser, ML pipelines in Python, and the users of your product.
One core for simulation, physics AI, geoscience, and robotics
Carotid artery blood flow, with particles advected through a 3D vector field.
Simulation and CAE
CFD, crash, and structural results post-processed and reviewed at full resolution by everyone on the program.
Physics AI
Surrogate predictions next to solver ground truth, at the scale of the training data.
Geoscience
Ensembles, drillholes, and uncertainty volumes for geologists, engineers, and partners.
Robotics and digital twins
Scans, toolpaths, and sensor data streamed into one scene, inside the tools operators already use.
Live solver streams
A running solver can send its output at each step. CoDim can host your solver or it can connect securely across VPCs.
Analysis
Clip, slice, threshold, contour, gradients, vorticity, and more run next to the data, chained into pipelines that update when an input changes.
Storage built for the cloud
Cloud native data standards for arbitrary 3D data structures with efficient streaming and distributed compute.
Build CoDim into your product
All of the streaming, compute, and analysis behind CoDim comes with a TypeScript SDK you embed, so you can focus on your product.
For developers →import { createClient } from '@codimensional/client'import { CoDimView } from '@codimensional/react'// Your backend issues the session. Users sign in to your app.const client = createClient({ embed: { acquire: acquireSession } })const workspace = await client.viewer.workspaces.open({})await workspace.addDataset(run.datasetId)export function Results() {return <CoDimView client={workspace.allocation.primaryView} />} Works with PyVista out of the box
Install the codim Python client and any PyVista dataset or plotter goes to a shared scene in one
line, from the scripts and notebooks you already run.
- Send solver output to CoDim from any Python script
- Pull CoDim datasets back into Python for analysis
import codimimport pyvista as pvmesh = solver.result() # any PyVista datasetmesh.codim.upload("Run 42", project="Wing study")mesh.codim.show()baseline = pv.DataSet.codim.load("Run 41") Nothing to deploy
CoDim runs the GPUs, render servers, and job queues and scales them with your users and jobs. Your team installs a Python package or the SDK.
Jobs and pipelines
Chain filters, inference, and post-processing into jobs. Each step runs on the hardware it needs, and results stream back into the scene.
One backend, every interface
Start a job from Python, review it in the app, embed it with the SDK, or hand it to an agent. Each one works on the same compute and the same results.
Every answer has a record
Each agent call is logged, and a result traces back to the data and the operations that produced it, so a person or an agent can check it.
Point an agent at the dataset that breaks your stack.
Send us the run or scan your team cannot open, and we will connect your agent to it.