Upload a .mcap or ROS1 .bag recording. LidarFlow runs LiDAR SLAM, aligns it with GNSS, and hands you back a point cloud map in your browser without installing ROS.
This is the whole pitch in engineer-native language. Feed LidarFlow the same topics you already record. Download the mapped artifacts you actually need.
recording.mcap or run.bagLiDAR recording with the topics you already captured./velodyne_points or /ouster/pointsLiDAR is required and validated before the run starts./imu/dataOptional. Used when the recording includes an IMU./fix or vendor GNSS topicOptional. Needed only when you want a georeferenced map.output.pcdThe mapped point cloud artifact used across the product.map.plyThe canonical full-GLIM export path when the precision run produces it.metadata.jsonRun settings, validation, and provenance in one file.slam_trajectory.txtUploaded when trajectory material is available for the run.No GNSS? You still get a locally consistent SLAM map. With GNSS, you also get a georeferenced one.
The deep walkthrough lives on the dedicated page. The short version is four verbs and one browser tab.
.mcap or ROS1 .bag
We check LiDAR, TF, GNSS, and IMU
GLIM runs LiDAR SLAM
FlexCloud aligns the map to WGS84
These landing pages go after the queries robotics engineers type when they need to turn a recording into a usable map.
Compare the local CLI, a Python script, and the browser workflow when you need a point cloud out of a recording.
Open guide →
See the difference between exporting frame-by-frame PCD files and building one mapped point cloud you can review.
Open guide →
Inspect MCAP with upstream tools, then bridge the gap from recorded topics to a mapped output in the browser.
Open guide →
Compare running GLIM + FlexCloud yourself against using a managed rosbag-to-map workflow.
Open guide →
Not in the browser upload flow yet. Upload `.mcap` and ROS1 `.bag` files today. ROS 2 `.db3` is on the roadmap.
Today the mapped workflow centers on `output.pcd`, `map.ply`, `metadata.json`, and `slam_trajectory.txt` when trajectory export is available. Georeferenced runs also expose preview and download artifacts through the browser.
No. Everything runs in your browser. Upload a bag, start a run, and download the map.
LidarFlow works with PointCloud2 recordings. The current beta already has presets and field-tested paths for Ouster, Livox, and common Velodyne-class captures, and the upload validator will tell you what topics were detected before you start a run.
The current upload limit is 20 GB per file by default.
No. Without GNSS you still get a locally consistent SLAM map. With GNSS you can also georeference it.
It depends on recording length, LiDAR density, and whether you choose the standard or precision path. We have not published a single benchmark number yet because we do not want to fake one.
The workspace is authenticated, and browser downloads use same-origin artifact routes instead of exposing raw storage keys. If you have retention or deletion requirements, ask before onboarding and we will confirm the beta workflow with you.
LidarFlow is invite-only during beta. Early users are onboarded directly while pricing is being finalized.
Start with the guides if you are still comparing approaches, or request access if you want to run a real recording through the beta.