One source of truth
Define the robot, its components, and its services once, then validate the complete system before launch.
Open-source · Pre-alpha
Build robots that can leave the lab.
Phoxal is a Rust-first robotics framework designed to give teams one coherent path from robot definition and simulation to deployment and operation—without rebuilding the stack at every stage.
Model once. Test in simulation. Run on hardware. Understand every run. Ship the next version with confidence.
Why Phoxal
Infrastructure that stays out of the way.
Robotics teams should spend their time on the robot, not on stitching together incompatible tools. Phoxal turns the common infrastructure into one understandable system.
Simulation-to-field continuity
Use the same system boundaries and timing model in Webots and on real hardware.
Strong contracts
Typed Rust interfaces catch integration mistakes early and make communication easier to inspect.
Process-level reliability
Native, isolated processes make lifecycle, ownership, and failures explicit without an orchestration layer.
Evidence from every run
Logs, telemetry, recordings, timing, and provenance are part of the system rather than an afterthought.
Safer iteration
Inspectable, versioned runtime bundles create a deliberate path to deploy, recover, and roll back.
Keep improving
Turn every run into a better next release.
Bring your own models, policies, training stack, and evaluation logic. Phoxal is being built to connect field experience to repeatable evaluation and deliberate deployment—without letting production behavior change behind your back.
Use the tools and learning methods that fit your robot. Keep the path to production explicit, testable, and reversible.
Phoxal defines the lifecycle, not your intelligence stack.
-
01
Capture
Record typed state, outcomes, feedback, timing, and provenance from every run.
-
02
Create
Train or derive candidates outside the robot using the tools that fit the problem.
-
03
Prove
Compare each candidate in repeatable scenarios against the acceptance criteria that matter.
-
04
Ship
Promote a passing artifact into a versioned bundle with a known fallback and rollback path.
Developer experience
From prototype to production, without rebuilding your stack.
A dependable robot framework should let developers move from definition to simulation and hardware, diagnose failures, and recover without editing framework internals or inventing custom glue.
-
01
Build the complete robot from one validated project
-
02
Run the same system model in simulation and on hardware
-
03
Deploy, observe, stop, restart, and roll back with confidence
Built in the open
A clear path to v1.
Phoxal is pre-alpha: the public repositories move quickly and interfaces can change. The architecture and implementation are open today for robotics engineers who want to explore the direction, challenge it, and follow the path toward a stable v1.