Custom Robot Simulation

Built for teams that need their own robot in software first

This program is a strong fit if you are not looking for a generic toy demo—you want your geometry, your joints, and your training story inside MRPX’s hosted environment.

Robotics startups showing investors and design partners a credible browser experience
Research labs standardizing rehearsal and data collection before hardware changes land
Training and demo teams that need a repeatable narrative without shipping a robot
Institutions evaluating workflows and ergonomics before deeper hardware integration

Core MRPX remains focused on surgical robotics training; custom robot simulations are a separate, scoped commercial program with its own statement of work.

Two phases: simulation first, twin modeling when you need hardware alignment

Setup fees and subscription are separate: the one-time setup covers the agreed build for that phase; the monthly subscription is required for ongoing hosted access to your private simulation in MRPX. Extra users, unsupported hardware, and work outside the signed scope are quoted separately.

Phase 1: Custom Robot Simulation

$2,000 one-time setup + $200/month subscription

Who it’s for: Teams that need a simulation-only private environment for one user—demos, training, and research—without connecting to a physical robot.

What it includes

1 user at Pro-tier access to MRPX
120 minutes per day of simulation time in your private environment
Up to 2 user-defined control methods, agreed in writing (for example browser controls and joystick mapping)
A hosted private simulation built on our CHAI3D / AMBF-style stack, reachable from the browser
Scoped validation against acceptance criteria agreed at kickoff

What it does not include

No physical robot integration, drivers, field commissioning, or production control paths
Not a digital twin—no commitment that the sim matches real hardware states or interfaces
Not unlimited engineering; changes beyond the signed scope are quoted separately

Phase 2: Digital Twin Modeling

$6,000 one-time setup + subscription (continues)

Who it’s for: Teams that need the hosted simulation aligned with a physical robot—interfaces, state mapping, calibration context, and scoped validation—not ad-hoc open-ended support.

What it includes

Everything in Phase 1 as the foundation
Scoped modeling and integration work to move the simulation toward a digital twin workflow for your hardware
Work is delivered against a defined statement of work, not unlimited engineering time

What it does not include

Not open-ended “make it match everything” without a written scope
Unsupported devices, extra users, and integration beyond the agreement are quoted separately
Not clinical care, regulatory submission, or production safety certification

What you provide

The clearer your package, the faster we can deliver. Plan to share:

CAD, meshes, or dimensions — visual geometry, collision geometry when separated, or STEP/STP when meshes are not yet split
Joint definitions and limits — ideally via .urdf / .xacro; otherwise a short written table (names, axes, limits, home pose)
Desired controls — which two scoped control methods you want and how inputs should map to motion for training use
Task goals — what “done” means for the first release (poses, sequences, tolerances, review checkpoints)
For Phase 2 only: physical robot interface context—APIs/SDKs, state and command mappings, calibration references, validation criteria you care about

What MRPX delivers

A private hosted simulation inside MRPX, available in the browser
Account-based access for the included user, with subscription-gated hosted availability
Scoped control setup for the two approved methods on our CHAI3D / AMBF-style stack
Validation against the acceptance criteria captured at kickoff
For Phase 2, integration and modeling work explicitly listed in your statement of work

Best fit / not a fit

Best for

Custom simulation demos you can share in a browser
Training workflows and rehearsal before hardware is ready
Early product visualization for stakeholders
Pre-integration feasibility work in software

Not for

Instant hardware integration or turnkey production deployment
Unlimited engineering requests without a written scope
Unsupported control devices brought in without scope review
Production safety certification or regulated clinical claims

Billing & scope at a glance: Setup pays for the agreed build for that phase. Subscription pays for hosted access to your private simulation and must stay active for that access. Phase 1 is simulation-only. Phase 2 is for digital twin modeling and hardware alignment within a defined scope. Unless we agree otherwise in writing, deliverables are for research, training, and demonstration—not clinical care, regulatory submission, or production safety certification.

Frequently asked questions

Is Phase 1 a digital twin?

No. Phase 1 is a simulation-only build inside MRPX. It does not include physical robot connection, drivers, or a guarantee that simulated state matches real hardware. Phase 2 is the path for scoped digital twin modeling toward your robot.

Why are setup and subscription separate?

The one-time setup funds the agreed engineering and integration for that phase. The monthly subscription covers ongoing hosted access to your private simulation in MRPX. They are billed separately by design so the scope of the build stays explicit.

What does “two user-defined control methods” mean?

We implement up to two control approaches you choose with us in writing—commonly browser controls plus joystick mapping, or another approved path that fits the CHAI3D / AMBF-style stack. Additional methods or unsupported devices require a separate quote.

How much simulation time do I get?

Phase 1 includes 120 minutes per day in your private environment for the included Pro-tier user, subject to fair use and operational limits we communicate in your agreement.

When should we choose Phase 2?

Choose Phase 2 when your goal is to align the hosted simulation with a physical robot—for example mirroring interfaces, mapping states and commands, and running scoped validation. It is sold as a defined scope, not unlimited engineering.

How do we get started after we say yes?

Use Request a Custom Robot Quote below, or create a project under your account to upload categorized files and track status. We review completeness before scheduling build time.

Files, uploads, and workflow

After you have a project in your account, use the Upload tab and assign each file to the closest category—visual mesh versus collision mesh, URDF, calibration, and so on. Starting a project first keeps everything organized.

Start Phase 1 in your account Open your projects Email about Phase 2

Upload Robot Files opens your project list. Pick a project, then upload with categories. If required items are missing after review, we may pause until the package is complete enough to schedule engineering time.

Upload categories (dashboard)

Category	What to put here
Visual meshes	Appearance geometry (`.stl` `.obj` `.dae`) for rendering
Collision meshes	Simplified or dedicated collision bodies
URDF / XACRO	Robot structure (`.urdf` `.xacro`)
CAD	STEP/STP when meshes are not yet split
Config files	`.yaml` `.yml` `.json`
Dynamics data	Mass, COM, inertia tables or notes (often PDF + data)
Control mappings	Notes for the two scoped control paths
Interface / API docs	SDKs, protocols, message contracts (Phase 2–heavy)
Calibration references	Transforms, reports, checkerboard results
Videos / images	`.mp4`; `.png` / `.jpg`
General documentation	README context in PDF/JSON/YAML as supported; acceptance criteria

Allowed extensions on the server today: .urdf .xacro .stl .obj .dae .step .stp .zip .yaml .yml .json .pdf PNG/JPEG images .mp4. Other formats require a separate quote.

Common delays we see: one heavy CAD file with no separate visual/collision meshes, missing joint axes or limits, unclear frame conventions, vague control mapping, or no clear definition of done. Front-loading these details keeps your project moving.