About

Collaboration is the bottleneck.
Not the compute.

CoDim is the missing collaboration layer for 3D data, built by the maintainers of the open-source tools your team already runs.

From the PyVista community

1M+ downloads / month
4K+ dependent projects

Why we started CoDimensional

Compute and data moved to the cloud, and AI has cut simulation time from days to hours. The volume of 3D output has grown to match. The 3D artifact that drives decisions is still a screenshot pasted into chat, or a 40 GB mesh sent over file share so a colleague can spin it up locally. The reviewer asks for a different slice, the engineer re-renders, exports, pastes. A two-hour run turns into a two-day decision. Some teams skip the viz entirely.

It takes longer to see the result than to compute it.

We believe 3D visualization is the most powerful way to understand and communicate complex results — and the most underserved. We are building CoDim to change that: one link to the live scene, the source data in your cloud, so experts can focus on the science, not the setup.

Who we are

Bane Sullivan CEO · Co-founder

Creator and lead maintainer of PyVista. Built countless 3D platforms for enterprise engineering teams. PyVista users have been asking him to build the rest for years. @banesullivan

Julius Busecke CPTO · Co-founder

Climate-physics PhD, Columbia. Core contributor to Pangeo. Built cloud-native data infrastructure for petabyte-scale climate workflows. Now he's bringing that cloud-native scale to 3D. @jbusecke

What we believe

Sharing 3D should feel like sharing a doc.

The dataset may be 80 GB. Sharing it should be one link that anyone on the team can open, in any browser. No exports, no installs, no waiting on the colleague with the right workstation. The conversation moves to where the data lives.

Visualization belongs in the pipeline.

3D viz lives at the end of the workflow today: an export, a screenshot, a slide. It should live throughout: continuous, versioned, automatic. Every run produces a live scene, not another PNG to paste into a deck.

The viewer is a function of the data.

Every 3D scene resolves directly from the source data. JPEG screenshots cut off from the source are unacceptable. There can never be drift between what you computed and what your team sees.

The data stays where it lives.