Nashville, TennesseeEst. 2016
Presence is a
technical problem.
615io builds immersive systems — AR, VR, and spatial computing for medicine, industry, and training — engineered on the agentic software and data pipelines that hold them up under real traffic.
Five practices,
one room
Most of this work arrives tangled: a headset build that needs an interface, an agent that needs clean data, a launch that needs film. Nothing is lost in a handoff that never happens.
Why immersivethe case for scale
A thirteen-foot tire will not fit in a classroom.
So we moved the classroom. Bridgestone's commercial group trains on product that cannot be shipped to a training room, on a calendar set by freight. We rebuilt the scenario in augmented reality: full-scale product placed in the room in front of you, walked around, cut into, inspected at any point in a sales conversation.
Immersive work earns its budget when physical scale, spatial understanding, or presence is the actual lesson. When it isn't, we say so and build you a web page.
Proof, not
promises
Vanderbilt Children's · Paradym2020
Big Hearts
A CT volume a surgeon can stand inside, scale up, and open to a cutaway plane before the day of surgery.
Bridgestone2021
Dirt Not Included
Thirteen-foot mining tires placed at full scale in any room, cut open and inspected on demand.
615ioLive
ShareXR
A WebXR training platform: interactive 3D modules delivered in the browser, behind an organisation's own sign-in.
Field notes
What we learned building the last one. Written by the people who shipped it.
- Evals are the deliverable, not the modelWhy we hand over a regression suite before we hand over an agent — and what goes in it.Draft / Agentic / 9 min
- Comfort budgets in industrial ARFrame time, occlusion, and the physical constraints of a shop floor at 40°C.Draft / Immersive / 12 min
- Your pilot stalled on data, not AIThe four failures we find in every stalled AI pilot, in the order we find them.Draft / Data / 7 min
- Designing for experts who are already fastDense interfaces for people who do not want to be onboarded, and what that costs.Draft / UX / UI / 10 min
Reach outMatthew
Prove the
hard part first.
The fastest way through an unproven idea is to build the smallest version of it that can fail. A prototype settles in weeks what a specification argues about for months.
Bring the riskiest part — the agent loop, the data join, the headset interaction — and it is the first thing we build, on real data. If it doesn't hold, you found that out for the price of a prototype instead of a build. Either way, you are talking to the person who writes the code.