Visible QA
Engineers should see what the worker is doing.
Queue depth, worker health, topic validation results. We refuse to hide the pipeline behind a spinner and a confidence score.
Company
We build the rosbag to map workflow we always wanted.
LidarFlow is built by engineers who spent too many late nights tuning SLAM stacks. We want robotics teams to get a map back without rebuilding the pipeline every time a new recording lands.
What we believe
Three things we will not bend on.
No opaque platform language
Name the libraries that do the work.
GLIM does the SLAM. FlexCloud does the georeferencing. ROS1 .bag and .mcap go in, mapped point clouds come out. The stack is in the docs, not in a brand guideline.
Refuse to fake metrics
We will quote numbers from your own recording.
You will not find a marketing benchmark chart on this site. Reconstruction quality depends on your sensors, route, and trajectory. We say so out loud.
Who we are
A small team that shipped rosbag pipelines the hard way first.
Before LidarFlow, we built and maintained internal SLAM and georeferencing pipelines for AV, UGV, and survey teams. Every project ended in roughly the same place: a folder of glue scripts, a CUDA box under someone's desk, and a doc that only one person could update. LidarFlow is the version we wish we could have bought.
Talk to us