Deployment
Gazebo Sim at San Francisco
Open-source 3D robotics simulator with physics, sensors, and plugins. Part of ROS ecosystem.
Gazebo Sim by Gazebo · Catalog entry · 1 source · not yet field-verified
Machine-readable surfaces
- Markdown mirror: /deployments/gazebo-sf.md
- JSON-LD: embedded in this page’s head
- REST API: /v1/robots/3e99c452-4da0-41e5-a6b4-55e7ed2f704f
- Data documentation: /data
- Query this programmatically: Deploy MCP
Gazebo Sim deployed in ROS ecosystem for robot development and testing globally.
- Trust tier
- Catalog entry · 1 source · not yet field-verified
- Last updated
- 2026-06-08
- Model
- Gazebo Sim
- Company
- Gazebo
- Location
- San Francisco
- Status
- operational
- ID
3e99c452-4da0-41e5-a6b4-55e7ed2f704f
Sources (1)
Methodology: Verified · 1 source (no primary) · last reviewed 2026-06-08
Verification posture
Verified
Low confidence
Review state
Stable
Last reviewed 2026-06-08
Maturity + lifecycle
Lifecycle: active
Architectural position
Cohort: software
Sources by quality tier
- 1
- unclassified
- Unclassified source
The framework is documented at /methodology. Corrections at /corrections. Reviewer: DEPLOY editorial team.
Methodology surface for Gazebo Sim at San Francisco.Common questions
- What is the Gazebo Sim deployment at San Francisco?
- Gazebo Sim, built by Gazebo, is recorded as a deployment at San Francisco on the DEPLOY registry. Gazebo operates the deployment directly.
- Who operates Gazebo Sim at San Francisco?
- Gazebo, the manufacturer of Gazebo Sim, operates this deployment directly. This is a maker-deploys-its-own-product arrangement rather than a customer pilot.
- Have there been incidents at the Gazebo Sim deployment at San Francisco?
- No active incidents affecting this deployment are recorded on the DEPLOY registry. Absence of recorded incidents is not a guarantee no incident occurred; DEPLOY records only sourced incidents and suppresses retracted ones.
Deploy Watch
Track this deployment.
We notify you when status changes against primary-source evidence, contract events surface, or a related incident is filed.