Targetless calibration for the complete sensor stack, from a recording you already have.
Multi-lidar, multi-camera, IMU and GNSS. Intrinsic, extrinsic and temporal parameters solved together in one joint run.
No targets, no scripted drive, no site visit. $1,500 $150 launch pricing today: lidar–camera extrinsics for every camera in your recording, in the web app or through the API.
Prefer we run it? Email us a link to one recording and our engineers will send you the free preview, usually within a day.
What comes back: per-sensor extrinsics with a confidence score, plus a before/after report.
Every sensor on the platform, in one consistent model
One run calibrates the whole rig, and every sensor pair comes back consistent with every other.
- Vehicles
- Mobile robots
- Construction machines
- Agricultural machines
- Drones
- Humanoids
- Anything sensor-equipped that moves
Lidar
Self-serve APIDirectional or 360°. Roof and perimeter 3D ranging; several lidars on one rig through an engagement.
Camera
Self-serve APISingle or multi-camera. Forward, side and rear optical coverage.
IMU
EngagementInertial motion, calibrated together with the rest of the rig.
INS / GNSS
EngagementPosition and navigation reference. Satellite positioning alongside the inertial unit.
Radar
EngagementPoint and object radar streams, aligned to the rest of the rig.
Camera model parameters
Lens and projection parameters for each camera.
Spatial relationships
Derived for any calibrated sensor pair.
Time offsets
Relative timing across sensor streams.
Self-serve today: lidar–camera extrinsics in the web app and the API, $1,500 $150 per calibration at launch pricing. Need multi-lidar, IMU, GNSS, radar, vehicle (CAN) alignment, camera intrinsics or time offsets? The same engine runs them as an engagement.
Get started
Data that must stay inside your environment? Use the customer-hosted option.
A 1° error puts objects half a metre from where they are
Extrinsics decide where every lidar point lands in your camera image. A 1° rotational error shifts a point 30 m away by ~0.5 m sideways — enough to paint a pedestrian's points onto the car beside them, corrupt every fused label your models train on, and mis-associate tracks.
The damage is silent: perception degrades, and nothing tells you calibration was the cause. That is why every job here returns per-sensor error and confidence, not just a matrix.
Repeatability across independent 30-second recordings on the same vehicle: how much repeated calibrations agree with each other. This is not an absolute-accuracy claim; every job still returns per-sensor confidence and a before/after report. See how accuracy is reported.
Why targetless, and how it compares
Every route to sensor calibration asks something of you. Here is what each one asks.
| Compared on | Deepen Calibrate | Target-based tools |
|---|---|---|
| Calibration target | None — uses a recording you already have | Checkerboard, ChArUco or AprilGrid |
| Setup | Nothing to install to calibrate; optional free Data Checker CLI | Software you install and run yourself |
| Result quality | Per-sensor confidence and error on every result | Not standardized; varies by vendor |
| Recording formats | ROS1 .bag, ROS2 .db3 and .mcap, unmodified | Varies by tool |
| What gets solved | The whole stack jointly: lidar, cameras, IMU, GNSS (lidar–camera self-serve; multi-lidar, IMU and GNSS through an engagement) | Pairwise, one sensor pair per session |
| Capture session | None — no site visit | A session with the target in view |
Compares Deepen Calibrate to traditional target-based calibration tools (checkerboard, ChArUco, AprilGrid). Describes categories of calibration software, not a specific vendor. Verified against public vendor documentation at time of writing.
Every sensor solved together, in one run
Every sensor is solved together in one run, so errors never stack up across pairs. You get one consistent model of the whole rig.
Lidar–camera runs self-serve today, in the web app and the API; the full stack, multi-lidar, IMU and GNSS included, runs through an engagement.
From a full-size vehicle to a delivery robot
Illustrative; sensor counts and placement vary by platform.
Questions teams ask before their first run
Which sensor combinations do you support?
The engine calibrates the complete sensor stack in one joint run: directional and 360° lidar, single and multi-camera rigs, IMU, and INS/GNSS — intrinsic, extrinsic and temporal parameters solved together. Self-serve today: lidar–camera extrinsics in the web app and the API. Multi-lidar, lidar–IMU, lidar–vehicle, radar, camera intrinsics and time offsets run through a Deepen engagement on the same engine. The free Data Checker CLI checks whether a recording is eligible for lidar–camera, multi-lidar, lidar–vehicle and lidar–IMU calibration.
How does pricing work?
Launch pricing: $150 per calibration (list price $1,500, 90% off until December 31, 2026). Lidar–camera extrinsics for every camera in the web app or through the API; recordings up to 50 GB. Two ways to buy: in the web app you run first, preview free and pay $150 only to download the result; with an API key you pay first and integrate calibration into your pipeline. A failed job is returned to you automatically. Everything else the engine does — multi-lidar, IMU and GNSS in the joint solve, camera intrinsics, time offsets, radar, custom formats, customer-hosted Docker — is a consultative Enterprise engagement, priced per engagement. See pricing.
Can you run it for me?
Yes. Email a link to one recording (.bag, .db3 or .mcap, shared from Google Drive, S3, Dropbox or similar) to calibrate-support@deepen.ai, with rough camera positions if you have them (from CAD, a URDF or /tf_static); otherwise we work them out with you. Our engineers run it and send you the before-and-after preview, usually within a day. If you want the results, it is the same $150 launch price; if not, you pay nothing. Through December 31, 2026, we also set up the first run with any team that would rather do it themselves.
What happens to my data?
With the hosted API, your recording is uploaded to Deepen's service and used only to run your job. If you need your data to never leave your own infrastructure, the AWS Marketplace path (coming soon) runs the same engine entirely inside your own VPC. For specifics on retention and deletion, contact us.
Can I use a personal email?
No. The web app needs a company or university email; personal addresses such as Gmail, Outlook/Hotmail and Yahoo can't run calibrations. Calibrations run on your organisation's recordings and the results are delivered to that organisation, so we tie each run to it.
How accurate is it?
We report repeatability, not a single blanket accuracy figure: on the same vehicle, independent 30-second recordings agree to within 0.1° angular, 1 ms temporal and 2 cm translation. Absolute accuracy depends on your rig and scene, so every job also returns a confidence score per sensor, quality flags, error stats and a before/after overlay report with the seed-versus-recovered delta, so you can judge the result yourself. Run the free Data Checker CLI first to catch anything likely to produce a low-confidence result.
How strong is the technology, and why not open source or an AI-written script?
Deepen has calibrated production sensor rigs for automotive and robotics teams since 2017, including Applied Intuition, Aptiv, BMW, Bosch, Lucid, Nissan, Uber and VW, and the targetless method is patented. Open-source tools calibrate one sensor pair at a time with a target board and stop being maintained when the research project ends; our engine solves the whole rig jointly, from an ordinary recording, and is maintained and supported as a product. An AI model can write a calibration script in an afternoon. It cannot give you a validated engine, the rig-specific edge cases learned across a decade of real vehicles, same-vehicle repeatability to a tenth of a degree, a report that stands up in review, or a team that answers when a result looks wrong. That is what you buy.
What are the cost savings?
You skip the cost of a target rig or calibration bay, a scripted capture session, and a site visit — you calibrate from a recording you already have. Turnaround is 15–25 minutes versus roughly a business day for a typical vendor capture-and-review service, and the launch price is $150 per calibration (list $1,500) with no monthly commitment.
Run it as a service, or inside your own environment
The same engine and the same result schema either way. Only where it runs changes.
Calibration as a service
Deepen receives the recording and returns the calibration result plus a quality report. Self-serve through the hosted API; nothing to provision.
- One key, no infrastructure on your side
- Same engine and the same results as the customer-hosted path
- First result the same session you sign up
Customer-hosted software
Runs on your own hardware inside your environment; we size it with you. Built for data-residency and export-control reviews. An AWS Marketplace listing is coming soon.
- Your sensor data never leaves your environment
- Same engine and the same results as the hosted service
- AWS Marketplace, in your VPCComing soon
Works with the rosbags you already record
Upload what your stack already writes. No ROS install, no conversion.
Container formats
Sensor streams
Lidar
Velodyne, Ouster, Hesai, RoboSense and other point-cloud lidars
Camera
Raw and compressed image streams
Radar
Radar point and object streams, through an engagement
IMU
Standard IMU messages
GNSS / INS
GNSS fixes and INS navigation messages, through an engagement
Vehicle
CAN / vehicle-speed data, for lidar–vehicle alignment through an engagement
Calibration types
Every type runs on the same engine. The free Data Checker CLI checks whether a recording is eligible for lidar–camera, multi-lidar, lidar–vehicle and lidar–IMU calibration.
- Lidar–camera (web app, API)
- Multi-lidar
- Lidar–IMU
- Lidar–vehicle
- Camera intrinsics
- Time offsets
Platforms: passenger and commercial vehicles, mobile and delivery robots, construction, mining and agricultural vehicles, drones and aerial systems, humanoids, ships and tracked platforms — any sensor-equipped system that moves through its environment.
From upload to extrinsics in four steps
One API key, nothing to install on your side. Your engineers integrate it in an afternoon.
-
Upload your recording
The rosbag you already have, exactly as your stack wrote it.
-
We validate it
Eligibility and quality checks run before anything is charged against your calibration.
-
Calibration runs
Typically 15–25 minutes. Check back whenever you like.
-
Your results come back
Extrinsics, a confidence score per sensor and a before/after report. A failed job is returned to you automatically.
Check your recording free before you pay
The free Data Checker CLI reads your .bag, .db3 or .mcap on your own machine and tells you whether it is ready for calibration. No upload, no account. If it passes here, it passes when you upload.
- Runs on your machine
- No upload, no account
- Open source, Apache-2.0
pipx install deepen-bag-check
Open source, Apache-2.0 — get the Data Checker CLI on GitHub.
How to record a good bag
A short drive through a mostly static scene is all it takes.
A mostly static scene
Buildings, poles, kerbs, parked cars. Keep moving traffic and pedestrians to a minimum.
A short continuous drive
Every sensor recording continuously for the whole window.
Your normal recording format
ROS1 .bag, ROS2 .db3 or .mcap, exactly as your stack writes it. Run the free Data Checker CLI on it first.
Drive pattern
Figure-8
Most motion diversity.
A loop
Returns to the start.
A few turns
Multiple heading changes.
A straight drive
Works when lidar or IMU is available.
More varied motion, better result. If your platform cannot turn, record the longer window.
Start with a bag you already have
Check it free with the CLI. If it qualifies, one API key gets you extrinsics the same session.
One price per calibration
Two ways to buy the same calibration. Web app: run first, preview free, pay $150 to download. API key: pay first, integrate in your pipeline. A failed job is returned to you automatically.
What we need to scope an enterprise pilot
A small, well-defined sample is enough to establish fit.
- Sensor layout. Models, counts, resolution, fields of view, and the CAD for sensor placement and mounting.
- Sample data. Two representative continuous recordings, with formats and topic definitions.
- Camera intrinsics. Preferred, not required.
Suggested pilot: one platform, two independent data windows.
What an engagement covers
The complete sensor stack in one joint run, delivered the way your review process needs.
- Sensors. Multi-lidar, multi-camera, IMU and INS/GNSS solved together
- Outputs. Camera intrinsics, extrinsics for any sensor pair, inter-sensor time offsets
- Delivery. Calibration as a service, or a Docker image on your hardware (engagement models)
Built for data-residency and export-control reviews: with customer-hosted delivery your recordings never leave your environment.
In the web app you pay only when you download a result; a calibration bought with an API key is consumed on a successful job. Not sure whether your rig runs self-serve? Run the free Data Checker CLI: if it reports lidar–camera as eligible, the $150 calibration covers it; anything else, talk to us.
Payments via Stripe. Checkout is handled by Stripe — Deepen never sees or stores your card details.
Per-customer API keys. API access is scoped to a key issued to your account, not shared credentials.
Data handling by path. Calibration as a service: your recording is uploaded to Deepen for processing. Customer-hosted: your data never leaves your environment.
Tell us your calibration needs
Sensors, rig type, recording format, and which path you want. For an enterprise pilot, include the three scoping items above. We reply with access details.