Patch Candidate
Preview snippet. Full diff generation and export are protected.
- FollowPath safety_margin_m="0.30"
+ RecoveryFallback enabled="true"
+ FollowPath safety_margin_m="0.45"
+ RequireHumanReview gate="canary"
Public preview, paid portal protected
Robot failure evidence, patch proof, and rollout gates in one command center.
SimPatch adds the post-failure decision layer for robotics teams. The paid dashboard is built around the chain after a field failure: incident evidence, replay readiness, neural-adaptive trace classification, patch candidate, safety case, human review, and supervised fleet rollout.
1
Evidence stays connected. ROS 2 bag context, sensor anomaly, patch candidate, sim replay, and safety-case notes remain tied to the same incident record.
2
The output is a buyer-ready packet. A customer receives dashboard access, protected APIs, neural-adaptive evidence, CSV/XLSX trace ledger, PDF safety case, and documented rollout decision support while the key is active.
3
The public preview is intentionally static. Live APIs, exports, customer documentation, and working dashboard functions require an active paid access key.
Already paid?
Paste the access key from the payment confirmation page. When the access window expires, the dashboard, docs, exports, and paid APIs stop accepting that key.
Active incident workbench
AMR-17 reflective pallet anomaly
Sample customer record showing how SimPatch ties field failure evidence to a patch, replay, safety case, and rollout decision.
Canary Hold
IntakeIncident capturedOperator note and sensor alarm attached.
ROS 2Bag indexedOdometry, LiDAR, and behavior state packet.
ReplayScenario packetGazebo or customer Isaac runtime contract.
NeuralAdaptive evidenceAnomaly class, patch parameters, and regression risk scored.
SafetyReview neededResidual risk and human gate required.
RolloutFleet heldCanary blocked until proof clears.
Simulation Confidence
Replay evidence supports human review. It does not replace safety engineers.
0.81
Threshold: 0.72 for review eligibility.
Safety and rollout gate
Fleet rollout remains blocked until evidence and review are complete.
Safety case: draft packet ready
Residual risk: reflective obstacle recurrence
Next action: human reviewer approval
OTA: webhook required per customer
TimeEvidence EventArtifactStatus
07:42ROS 2 anomaly packet indexedtrace ledgerAttached
07:46Replay scenario generated for simulator runnerscenario JSONReady
07:51Safety packet queued for human reviewPDF exportLocked
Protected APIIncident evidence
Protected ExportTrace CSV/XLSX
Protected ExportPDF safety case
Protected PortalCustomer docs
Where SimPatch is different
Designed around the post-failure decision, not just the data view.
Competitor dashboards are strong at visualization, fleet operations, or data infrastructure. SimPatch should win by packaging the evidence needed to approve, reject, or hold a robotics patch after a field failure.
Failure to patch record
Turns raw robotics evidence into a connected incident, patch, replay, safety, and rollout record.
Safety-case packet
Exports a buyer-readable safety packet with claim boundaries, provenance, and human-review status.
Access-controlled outputs
Paid APIs, docs, dashboard, and exports require active access and expire with the purchase window.
Access paths
Choose the proof package that matches the buyer risk.
These cards explain what the customer receives. Checkout opens the live Polar payment flow when served from the SimPatch app.
Per Incident Proof
$5,000For one field failure review.
- 30-day dashboard access
- Evidence packet and trace ledger
- Patch and safety-case review surface
90-Day Pilot
$25,000For a focused robotics safety sprint.
- 90-day access key
- Multiple incident records
- Proof workflow delivery sprint
Annual Fleet License
$40,000/yearFor recurring incident and rollout governance.
- 365-day access key
- Fleet rollout decision support
- Protected docs, exports, and APIs