01 ROBOTICS
⬡
Prototype robot workflows
Inspect ROS 2 nodes and topics over rosbridge, subscribe to selected messages and review explicitly authorized publications.
ROS 2 · rosbridge INTRODUCING ROBOFORGE STUDIO v0.4.0
From ideas to
working systems.
Explore industrial protocols, prototype robotic integrations and review AI-assisted code from one local-first engineering workspace.
11bundled integrations
04AI provider options
02interface themes
ROS 2
OPC UA
MQTT
AI
CONNECTORS DISCOVERED AT BUILD TIME 01 — 10
ROBOTICSINDUSTRIAL DATAIoT & TELEMETRYASSISTED DEVELOPMENTPROTOTYPING
01 / USE CASES
One workspace. Several disciplines.
RoboForge helps organize the early stages of engineering work without pretending to replace specialized industrial systems or safety validation.
02 INDUSTRIAL DATA
▤
Explore machine telemetry
Browse a configured OPC UA address space and read values locally before designing higher-level tooling.
OPC UA · read-only03 CONNECTED SYSTEMS
◉
Build IoT observability
Subscribe to MQTT-over-WebSocket topics, observe event traffic and publish only after human confirmation.
MQTT · EMQX04 AI ASSISTANCE
✳
Draft and inspect code
Choose local Ollama or an optional external API. Generate drafts, inspect resulting files and review before deployment.
Ollama · OpenAI · DeepSeek05 SIMULATION
◇
Observe simulated systems
Explore Isaac Sim-related ROS telemetry such as /clock in experimental workflows—without claiming scene-control support.
06 DEVICE EXPLORATION
▣
Inspect connected devices
Monitor authorized Arduino serial data, Home Assistant entities and selected enterprise API resources where available.
Arduino · Home Assistant · Siemens07 SOFTWARE ANALYSIS
⌘
Inspect application structure
Use optional local REA to collect static analysis Evidence from selected JavaScript/Electron, .NET, Go and Rust artifacts with explicit authorization.
REA · opt-in · experimental02 / INTERFACE
Engineered for clarity.
Graphite, silver and cyan. A restrained working environment with distinct light and dark appearances.
ⓘ These are approved static design previews, not live React/runtime or hardware test screenshots. The depicted status indicators are illustrative.
03 / CONNECTORS
Bring your toolchain together.
Eleven bundled integration modules are documented here. Each has defined limitations; experimental integrations have not been validated for industrial deployment.
ROS 2 CORE
rosbridge inspection, subscriptions, confirmed publish
OPC UA CORE
Local address-space browse and read
MQTT / EMQX CORE
WebSocket telemetry and confirmed publish
NVIDIA Isaac Sim EXPERIMENTAL
ROS-based clock observation; no scene control
Siemens Xcelerator EXPERIMENTAL
Product-specific configured HTTPS API inspection
Arduino EXPERIMENTAL
Permission-gated Web Serial monitoring
Home Assistant EXPERIMENTAL
Authenticated entity and automation observation
REA Analysis EXPERIMENTAL
Optional local static analysis Evidence · external official REA CLI required
Refract Studio EXPERIMENTAL
Optional isolated CPL → CPA text preview; trusted local checkout required
DeepSeek Janus EXPERIMENTAL
Multimodal integration planned; no inference or bundled model weights
ChromaPlex Coding Agent EXPERIMENTAL
Target-aware source review, optional fail-closed ClamAV preflight, verified build manifest inspection; separate Linux installation required
Trusted extensions
New bundled modules can be added to source and discovered at build time. No arbitrary remote code loading.
04 / PROVIDERS
Keep AI on your terms.
Local-first doesn't mean local-only. RoboForge defaults to Ollama; external model services are optional and explicitly selected in Settings. Credentials must stay private.
Code generation is assistance, not deployment.
Results are reviewable text. Generated commands must not be executed on robots or machines without independent validation and operator approval.
01
OllamaLocal AI models, local-first default
DEFAULT02
OpenAI APIOptional external service
OPTIONAL03
DeepSeekOptional external service
OPTIONAL04
Compatible APIExplicitly configured backend URL
OPTIONAL05 / GET STARTED
Run locally.
Work deliberately.
Extract the source archive, install dependencies, run the automated tests and open the application. Node.js 20.19+ or 22+ and npm are required for the first build.
For Linux launchers, optional integrations and configuration, see the project README on GitHub. The website you are viewing is a project presentation, not the RoboForge application.
LINUX SHELL
npm --prefix frontend install
npm --prefix frontend run build
npm --prefix backend test
node backend/server.jsOpen http://127.0.0.1:3001 after starting the server
!
Engineering tool. Not an industrial safety controller.
Frontend production build and real hardware, Siemens tenant, model provider and service integrations have not been independently verified in this presentation package. Local API health does not prove that connected equipment is available. Any live deployment requires separate authorization, safety review and acceptance testing.
06 / OPEN SOURCE
Built to evolve. Open to ideas.
RoboForge Studio is an open-source engineering workbench released under the MIT License. Explore the code, follow development and contribute on GitHub.
Explore the source. Help shape the next release.
Developers and engineers can contribute bug reports, reproducible test cases, documentation and proposals for new integrations. RoboForge remains under active development, and connections to physical industrial systems require independent validation before use.