PSF Product Platform

PSF Workbench

Robotics tooling, deployable. PSF Workbench turns complex robotics stacks into repeatable operator workflows, so teams can focus on the machine, the task, and the policy instead of rebuilding the environment every time work begins.

Talk to GSN Robotics View product platforms View Workbench on GitHub

Operator View

Behavior DeckCompose robotics behavior as named cards with clear parameters.

Code SurfaceEdit generated policy code without leaving the workflow.

Run PanelLaunch play, eval, submit, and diagnostics through one surface.

Adapter PackWrap ROS 2, simulation, controllers, and vendor tooling without replacing them.

From lab toolchains to usable robotics workflows.

Modern robotics stacks are powerful, but the hand setup can be fragile: simulators, containers, ROS topics, policy code, controllers, diagnostics, and submission paths all need to line up. Workbench packages those moving parts into a deployable surface that a technical operator can actually use.

Desktop UI

Operator-ready control

A desktop surface for choosing projects, editing policy code, composing behavior decks, launching runs, and watching output without jumping between tools.

CLI

Repeatable automation

The same underlying actions can run headless for scripting, diagnostics, CI, or remote workflows where a GUI is not the right tool.

Adapters

Wrap, never replace

Adapter packs connect Workbench to robotics ecosystems such as ROS 2, Gazebo, MoveIt, Nav2, ros2_control, vendor SDKs, and future industrial endpoints.

Behavior Deck

Policy work made visible

Named behavior cards give operators and engineers a structured way to compose motion and task logic while still producing readable project artifacts.

Simulation Loop

Run before the real machine

Workbench can launch live simulation and policy containers together, making the system behavior visible before it reaches hardware.

Diagnostics

Know what is running

Topic inventories, run logs, cleanup behavior, and planned log intelligence help turn robotics output into operational status.

Built for teams that need robotics to run outside the demo room.

Workbench is designed around the practical handoff from engineering environment to deployable workflow. It keeps the underlying tools intact while changing the user’s relationship with them.

Generated artifacts stay readable.Workbench emits files into the project instead of hiding state inside a black box.

Runs should be reproducible.Every run can carry the information needed to understand what happened and why.

Local-first by default.Robotics work should not require telemetry or unnecessary external dependency paths to be useful.

Engines do not own actuation.Automation and intelligence belong behind deterministic gates before they touch real motion.

Initial tooling coverage

ROS 2GazeboMoveItNav2ros2_controlVendor SDKsContainersDiagnostics

The architecture is also designed to extend toward MuJoCo, microcontroller endpoints, PLCs, Modbus, OPC-UA, and other industrial integration points.

Where it fits in the PSF family.

PSF Workbench helps develop, run, inspect, and package robotics behavior. PSF Helm focuses on local intelligence at a single endpoint. PSF CORE focuses on large-scale orchestration across many endpoints. Together, they form a path from engineering workflow to endpoint reflexing and broader industrial coordination.

Explore PSF Helm Explore PSF CORE

Make robotics tooling easier to deploy.

For labs, integrators, and industrial teams that need repeatable robotics workflows, PSF Workbench turns complex toolchains into a controlled operating surface.

Start a conversation

Note: PSF Workbench has community/developer materials available separately. Enterprise packaging, support, adapter coverage, deployment targets, and integration services can be scoped for production robotics environments.