Three specialties. One team that owns the whole build.

Spatial software for work and play: training, field guidance, visualization and entertainment, built for today’s headsets and the glasses coming next.

• Business tools for people who work with their hands: procedures anchored to the equipment, safe rehearsal of risky tasks, and sites you can walk around on a table.
• Entertainment and learning on the same foundation: VR games, sports and skills training that run on standalone headsets.
• Mixed reality on Quest and Apple Vision Pro: passthrough, spatial anchors and hand tracking when the room makes the experience better.
• Comfort as a specification. Locomotion, vergence and frame pacing tested on real headsets every week.
• Shared sessions and host-authoritative networking where more than one person needs to be in the space.
• Integrations with the systems you already run, so the headset is a window onto your data, not a silo.

VR, desktop and mobile titles, from paper prototype to store page.

• Quest, PC VR and mixed reality with comfort-first interaction and frame times that hold at 90 Hz.
• Windows, macOS and Linux on Steam. Controller and Steam Deck support as a default, modding hooks where the design wants a community.
• iPhone and iPad with short sessions, honest monetization and live operations you can run yourself.
• Store submission, certification and the first month of fixes included in every scope.

Add assistants, automation and grounded search to the software you already run. A person approves every action.

• Assistants inside your product that answer from your own documents, tickets and data, and cite where each answer came from.
• Workflow automation that drafts the message, the ticket or the configuration change, then waits for approval.
• Grounded search across the knowledge your team already has, in the app, in Slack or Teams, or in the headset.
• On Azure, AWS or your own servers, in the language your system is already written in. C# and .NET, Python, TypeScript and Node, Java, Go, Swift, C++ and other well-documented stacks.
• On-device and private-cloud models where latency, cost or privacy demand it. Evidence of what changed, kept with the system.