MRPX helps research teams, startups, and medical robotics groups test teleoperation, training, and custom robot workflows using ROS-based simulation environments — with optional Bullet-powered physics and CHAI3D-based interaction support where applicable for selected workflows.
ROS 2–oriented builds: coming soon — we’ll scope compatibility with your stack before kickoff.
Get started — tell us what you need
A straightforward path from browser access to a structured custom-robot engagement when you need it.
Queue, connect, and run ROS-based simulation in the browser.
URDF/meshes, CAD, configs, or notes — we tell you what’s missing.
Paid projects get a dedicated private route for your team while we attach simulators later.
Status updates, notes, and revision rounds — no vague handoffs.
Labs validating teleoperation UX, startups proving a hardware concept, and teams that need a credible browser-based sim without standing up ROS, rendering, and hosting themselves. Not a substitute for clinical systems — see FAQ.
Common inputs include URDF/XACRO, meshes (STL/OBJ/DAE), STEP exports, ROS packages (ZIP), YAML/JSON configs, documentation (PDF/README), textures, and optional video. We’ll confirm categories if something is ambiguous.
We review completeness, log intake status, and run placeholder validation/scan hooks on files (production scan integration is pluggable). You track progress in your account; admins can request missing files. When the build milestone is reached, we publish a private premium demo URL — full container/simulator automation hooks in separately.
Honest stack framing: ROS-forward workflows in simulation, optional Bullet-backed physics where it fits your scene, and CHAI3D-style interaction patterns where we enable them for your use case. Private demo environments for premium projects. ROS 2: coming soon — call it out in intake so we plan accordingly.
Tell us about your robot or request the $2000 premium intake (log in to create a project and upload files securely).
What files should I upload? URDF/XACRO when you have them; meshes (STL/OBJ/DAE); STEP if CAD-only; ROS package ZIP; YAML/JSON; PDF/README; textures; optional MP4.
Do I need a URDF? No, but it speeds things up. We can start from CAD and agreed conventions if needed.
Can MRPX work from CAD files? Yes, as a starting point — we’ll agree on frames, scale, and what’s feasible for sim.
What happens after I upload my robot? Engineering review, status updates in your account, possible “missing files” state, then build prep and a private demo page when ready.
Will I get a private demo page? Yes for the premium path — a gated /demo/customer/… route; full simulator attach is a follow-on integration step.
Is ROS required? Our workflows are ROS-oriented today; we’ll document what runs where for your project.
Do you support ROS 2? Coming soon — select “ROS 2” in intake and we’ll align scope.
Joystick or browser teleoperation? Yes, where supported for your scene — state your preference in intake.
Haptics or CHAI3D-style interaction? Available for selected workflows where we enable them — not universal.
How long does review take? Typically a few business days for first pass; complex packages take longer.
Is this for clinical use? No. Research, training, and demonstration only — not for diagnosing or treating patients.
Email manuel.retana@mrpxtech.com with your goals and timeline. For structured intake and payment, start at Custom robot or create a project (account required).
For research, training, and demonstration purposes only. This simulation is not medical advice and is not intended for clinical use. The system is provided as-is for educational and research purposes.
Try the browser demo today, or follow the premium path for secure uploads and a private demo page.
Get demo access Custom robot project