Your named POCs
Three people. Three lanes. Direct lines.
Every Perception Studio question routes to one of us. Match your question to a lane below, or send to the team alias and we’ll triage internally.
Alon Zehngut
Director of Product
Runs Perception Studio go-to-market — program strategy, customer feedback architecture, release narratives. Owns the launch plan, the licensing model, and the Design Partner program.
Best for
Program strategy · business model · licensing · Design Partner inquiries · co-marketing
Chris Matthieu
Engineering / Perception
Engineering lead for Perception Studio. Owns the technical integration between RealSense cameras and the NVIDIA cuVSLAM stack. Hosts most of the monthly office-hours deep dives. The person to ask “how does it actually work?”
Best for
Technical depth · integration questions · benchmarks · calibration · debugging
Roi Ziss
Product & Strategy
Drives the Perception Studio product strategy and OEM partnerships. Sits at the intersection of RealSense, NVIDIA Isaac, and the humanoid / AMR OEM landscape. The person to ask about roadmap direction or where the industry is going.
Best for
Roadmap · OEM & NVIDIA partnerships · strategic discussions · industry trends
Other ways to reach us
Pick the channel that fits the question.
Email if it’s specific to your project. Discord if it’s a general question. GitHub if it’s a bug.
Discord community
Real-time help from RealSense engineers and other Studio members. Per-feature channels keep conversations focused.
GitHub Issues & Discussions
Bug reports, feature requests, public technical discussions. Per-feature issue templates in the realsense-ai org.
Team alias
For everything else, or when you don’t know who to ask. Triaged within one business day.