Let's get the uncomfortable part out of the way: free photogrammetry software is good. Not "good for the price." Good. Open-source projects have been turning drone photos into maps and models for years, and plenty of working pilots built their first deliverables on them. If someone tells you free tools can't produce a usable orthomosaic, they're selling something.
So the real question for a commercial pilot isn't "can free software make a map?" It's "what does running my business on it cost me in hours, risk and client experience?" That's what this post is about. If you want a list of options side by side, the drone mapping software comparison does that. If you're still sorting out what this category of software actually does, start with what photogrammetry software is. Here, we're weighing trade-offs.
The three free tools pilots ask about, in their own words
We describe each project only from its own documentation, because secondhand summaries of open-source tools go stale fast.
OpenDroneMap and WebODM
ODM describes itself as "an open source command line toolkit for processing aerial drone imagery." Its README lists classified point clouds, 3D textured models, georeferenced orthorectified imagery and georeferenced digital elevation models as outputs, and says the easiest way to run it is through Docker. The OpenDroneMap documentation gives a bare minimum of a 64-bit CPU, 20 GB of disk and 4 GB of RAM, warns that those specs handle no more than 100 to 200 images, and publishes a RAM table that climbs to 32 GB for 500 images and 64 GB for 1,500.
WebODM is the point-and-click option most pilots mean when they say "ODM." Its site calls it "the free and open source drone mapping software" and lists orthomosaics, point clouds, DSMs and DTMs, 3D models, volume measurements, ground control points, contours and map sharing. Worth knowing: WebODM's site and GitHub README now say it has "officially decoupled from OpenDroneMap" and processes with its own ODX engine, which it describes as forked from ODM. The README lists the AGPL-3.0 license. Per the WebODM download page, the Windows installer runs natively, the macOS and Linux versions use Docker, and you need at least 8 GB of RAM (16 GB or more recommended), with a note that 8 GB may not get you past about 100 images.
Meshroom
The Meshroom manual calls it "a free, open-source 3D Reconstruction Software based on the AliceVision framework." Its requirements page (written for the 2023.1 release) warns that it "requires an NVIDIA GPU card with a CUDA compute capability >= 3.0 for the MVS part," with a CPU draft-meshing fallback, and recommends 32 GB of RAM. The AliceVision site shows the photogrammetry template ending in a textured mesh and lists use cases like film and VFX, cultural heritage and science. Orthomosaics and elevation models aren't among the outputs it lists, so for map deliverables, Meshroom is a 3D-model tool first.
COLMAP
COLMAP describes itself as "a general-purpose Structure-from-Motion (SfM) and Multi-View Stereo (MVS) pipeline with a graphical and command-line interface," free and open source under a BSD license. Its FAQ says that without a CUDA-enabled GPU you can use "all COLMAP functionality except the dense reconstruction part," and that geo-registration works by supplying 3D locations for camera centers. Its install guide notes that the default Linux distribution packages don't come with CUDA support. COLMAP is a reconstruction engine that researchers and developers build on, not a turnkey mapping product.
Free vs paid at a glance
| Trade-off | Free / open-source route | Paid commercial route |
|---|---|---|
| Software license | No license fee (AGPL, MPL or BSD terms apply) | Subscription or license fee |
| Setup | You install, size hardware, sometimes manage Docker or GPU drivers | Vendor installer and onboarding |
| Support | Community forums, GitHub issues, docs | Vendor support tied to your account |
| Map outputs | Strong (WebODM/ODM); mesh-first (Meshroom); engine-level (COLMAP) | Depends on product |
| Client delivery | WebODM has sharing; the rest is up to you | Varies; some include client portals |
| Quotes, invoices, client records | Not what these projects are built for | Only if the product includes business tools |
| Accuracy workflow | GCPs in WebODM/ODM; camera-center geo-registration in COLMAP | Vendor-specific |
What you actually give up with free software
1. Your setup and server time
The license is free. The workstation isn't, and neither is the afternoon you spend getting it running. Read those RAM tables again: if your typical job is 600 to 1,500 images, the documentation is telling you to plan for a machine with 32 to 64 GB of memory. COLMAP and Meshroom lean on an NVIDIA CUDA GPU for their dense steps. None of that is a knock on the projects. It's just the honest bill of materials.
Then there's maintenance. Updates, Docker versions, driver changes and the occasional failed task that needs a parameter tweak all land on you. Do the math with your own numbers: if setup and troubleshooting eat ten hours a quarter and you bill $100 an hour, that's $4,000 a year of time you didn't invoice. Your rate and hours will differ. Run your figures, not ours.
2. Someone to call
Open-source support is real, but it's community support. You post a log, you wait, and kind strangers help when they can. That's fine on a Tuesday practice dataset. It's a different feeling at 9 p.m. when a client expects the map in the morning. With paid software, you're paying partly for an accountable support channel.
3. A client-ready delivery
A GeoTIFF on your drive isn't a deliverable to most clients. A builder or landowner wants a link that opens in a browser. WebODM does include sharing, which is a genuine point in its favor. With Meshroom or COLMAP you'll be assembling that piece yourself. Ask yourself how much of each job goes into packaging, uploading and explaining files. That's the step clients actually see.
4. Billing and the business around the map
None of these projects' docs describe quoting, invoicing or client records, and they shouldn't. They're processing tools. But your business still has to quote the job, track it, deliver it and get paid. If those steps live in four other apps, the "free" stack has a hidden admin tax every single job.
5. An accuracy workflow you can defend
WebODM and ODM support ground control points, and COLMAP supports geo-registration from known camera positions, so free doesn't mean inaccurate. What matters is whether you have a repeatable process: control, checkpoints, a record of settings, and a way to show a client how the map was checked. That's on you either way. Free tools just leave more of the process design to you.
When free is the right call
- You're learning photogrammetry and want to understand every knob.
- You process a handful of jobs a month and have a capable workstation already.
- You're comfortable with Docker, logs and forum troubleshooting.
- You need 3D models for creative or research work, where Meshroom or COLMAP shine.
- Your clients take raw GeoTIFFs and you bill from an accounting tool you already like.
If that's you, stay free. Seriously. Spend the money on a better camera or more batteries.
When paying starts to make sense
The math flips when mapping becomes a line of business rather than a side skill. More jobs means more setup hours, more support moments, more deliverables to package and more invoices to chase. At that point you're not really comparing software prices. You're comparing your time.
That's the gap SkyView is built for. SkyView Desktop processes RGB drone photos on your own Windows computer, so there's no per-map processing fee. It produces orthomosaics, DSMs and DTMs, contours and cut-fill, and you deliver maps to clients through private Pilot Ledger projects in a browser. Your quotes, invoices and client records sit in the same Pilot Ledger account. If you do drainage work, water flow analysis is available in the Survey & Earthworks add-on and runs on a DTM. It shows slope, drainage lines, ponding and catchments, and it doesn't model pipes, storm drains, rainfall, soil or time, so engineering still goes to an engineer. We go deeper on the local-processing model in desktop photogrammetry without a per-map fee.
SkyView isn't free, and we won't pretend otherwise. You're paying for local processing plus the client delivery and business tools around the map, in one account. Whether that's worth it depends on your job volume.
A fair way to decide
- Pick one finished dataset you've already delivered.
- Process it in a free tool (WebODM is the most direct comparison for map work) and log every hour: install, processing, fixes.
- Package it for a client the way you really would, and time that too.
- Run the same dataset through a paid option during its trial and repeat the log.
- Compare the totals, including what each one did to your quote-to-invoice time, not just the processing minutes.
The tool that wins on your real numbers is the right one, whatever it costs.
To compare SkyView plans and start a 14-day business trial with no credit card, see Pilot Ledger pricing.