We keep seeing the same pattern in field deployments: once a ROS 2 robot is outside the local network, remote debugging quickly turns into rebuilding transport plumbing every time something goes wrong — SSH, VPNs, port forwarding, fragile tunnels, or asking someone on-site to help.
We’re building RoboTunnel to validate a narrower workflow first: bring one robot online, start one managed debug session, and get to the actual ROS 2 debugging task faster.
We’re especially looking to talk to teams that:
- deploy ROS 2 robots outside the office/lab
- need remote access for debugging or diagnostics
- deal with NAT, customer networks, or weak field links
- currently rely on SSH / VPN / port forwarding / ad-hoc setup
Current beta focus:
- CLI-first workflow
- bringing a robot online
- starting a managed debug session
- validating real debugging/diagnostics workflows
Not trying to be a full fleet platform yet.
We’re looking for 3–5 design partners for a high-touch beta. I’ll personally help with onboarding and aim to get one real robot connected and one real session working.
If this is a live pain point for your team, reply here or reach out privately. If easier, fill out this short beta form: [RoboTunnel Private Beta Interest Form]
Robotunnel official site: https://robotunnel.io