# Private URDF/Xacro validation (no storage, CI-ready)

**URL:** https://discourse.openrobotics.org/t/private-urdf-xacro-validation-no-storage-ci-ready/54314
**Category:** ros-controls General
**Tags:** ros2, urdf
**Created:** [April 26, 2026, 3:12pm UTC](https://discourse.openrobotics.org/t/private-urdf-xacro-validation-no-storage-ci-ready/54314 "2026-04-26T15:12:02Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Robotic](https://avatars.discourse-cdn.com/v4/letter/r/c6cbf5/32.png) [@Robotic](https://discourse.openrobotics.org/u/Robotic)
#### Post date: [April 26, 2026, 3:12pm UTC](https://discourse.openrobotics.org/t/private-urdf-xacro-validation-no-storage-ci-ready/54314/1 "2026-04-26T15:12:03Z")

</div>

Hi,

I reached out after hearing a common concern from robotics engineers:

“ **Why would I upload my URDF/Xacro to an external service**?”

That hesitation makes complete sense especially with proprietary robot models.

So just to clarify how RoboInfraapi is designed:

- Files are processed in-memory and never stored

- No training or reuse of uploaded data

- No persistence of URDF/Xacro/3D files

- Requests are isolated via API keys

The goal is simple:  
👉 add CI/CD-style validation for robot models without exposing your data

To give a concrete example, I tested RoboInfraapi with a public **NASA humanoid model Robonaut 2** :

[https://github.com/gkjohnson/nasa-urdf-robots/blob/master/r2\_description/robots/r2c6.urdf](https://github.com/gkjohnson/nasa-urdf-robots/blob/master/r2_description/robots/r2c6.urdf)

It validates structure, detects issues, and analyzes kinematics instantly the same pipeline teams can run in CI.

Why teams use it:

- Catch URDF issues before simulation/debugging

- Standardize Xacro → URDF across environments

- Validate models automatically in GitHub Actions

- Avoid “works on my machine” ROS inconsistencies

You can try the public validator here (no signup required):  
[https://roboinfra-dashboard.azurewebsites.net/validator](https://roboinfra-dashboard.azurewebsites.net/validator)

🤝If you’re open to it, 💕I’m happy to:

- walk through the architecture

- or help test it on one of your models (privately)
