Capture is only half the job. Deliverables arrive in industry-standard, non-proprietary formats that open directly in the CAD, BIM, GIS and construction platforms your team already runs — no new subscription, no locked file, no conversion work on your end.
A deliverable that only opens in one vendor's software is not really yours.
Every dataset is exported in open, industry-standard formats. That means your team can use it today in whatever platform you already pay for, and still use it in five years in whatever replaces that platform. It also means handing the data to a surveyor, an engineer, an architect and an insurance adjuster does not require any of them to adopt a tool.
Where a client already runs a connected platform, data can be routed into it directly. Where they do not, nothing is lost — the same files are delivered for upload.
Format, coordinate system and deliverable structure are confirmed before the flight, not after. Capturing to a specification is straightforward; retrofitting one is not.
Standard deliverables can be incorporated into common CAD, BIM, GIS and construction platforms — including, but not limited to:
CAD and civil. DXF and SHP carry contours and linework into AutoCAD and Civil 3D for design and earthwork.
BIM and VDC. LAS/LAZ and E57 point clouds import into Revit and Navisworks for coordination against model geometry and clash review.
GIS. GeoTIFF and KML/KMZ preserve georeferencing for ArcGIS and QGIS, keeping captured data aligned with existing spatial layers.
Construction management. Orthomosaics, progress documentation and 360° walkthroughs attach to the project record where field teams already look.
Processing is matched to the deliverable rather than forced through one pipeline.
Running more than one processing path matters because jobs differ. A stockpile volume, a facade model, an interior walkthrough and a marketing edit do not want the same pipeline, and forcing them through one compromises all four.
In September 2026, Procore completed its acquisition of DroneDeploy, which now operates as a Procore company. For teams already running Procore, that makes DroneDeploy the shortest path from a flight to the project record — orthomosaics, 360° panoramas and field notes moving into Procore Photos, and Procore drawings pulling back as overlays to compare design against actual conditions.
Beyond Procore, DroneDeploy supports roughly twenty integrations covering project management, BIM, GIS and document control — Esri ArcGIS, Autodesk Construction Cloud and Forma, BIM 360, PlanGrid, CompanyCam, Box, Egnyte, Amazon S3, Azure, OneDrive, Google Drive and Google Cloud Storage among them.
Routing into a client's environment is coordinated with that client's account and platform licensing. Where a direct connection is not in place, the same deliverables are provided in standard formats for upload — the data is identical either way.
No. Every deliverable is produced in industry-standard, non-proprietary formats — GeoTIFF, LAS/LAZ, OBJ, DXF/SHP, E57, KML/KMZ, JPG and MP4. Those open in CAD, BIM, GIS and construction platforms directly, with no subscription to anything on our side.
DroneDeploy is one delivery path among several. If your team already runs it, data can be routed there. If not, nothing changes about what you receive.
Procore acquired DroneDeploy in September 2026, and DroneDeploy now operates as a Procore company — which makes it the most direct path from aerial capture into a Procore project. Orthomosaics, 360° panoramas and field notes can move into Procore Photos, and Procore drawings can be pulled back as overlays for comparison against actual site conditions.
Routing data into a client's Procore environment is coordinated with that client's account and platform licensing. Where a direct connection is not in place, the same deliverables are provided in standard formats for upload.
Processing is matched to the deliverable rather than run through a single pipeline. DroneDeploy and Pix4D for mapping, orthomosaic and photogrammetric output; Agisoft Metashape for dense reconstruction and detailed modeling; WebODM for open processing workflows; SkyeBrowse for rapid video-based reconstruction; and the Insta360 pipeline for 360° interior and confined-space capture that can feed immersive walkthrough platforms including Matterport.
Media production runs through Adobe Creative Cloud.
Yes. DXF and SHP bring linework and contours into AutoCAD and Civil 3D. LAS/LAZ and E57 point clouds import into Revit and Navisworks for VDC and BIM coordination. GeoTIFF and KML/KMZ carry georeferencing into ArcGIS and QGIS.
If your team needs a specific format, coordinate system or deliverable structure, that gets confirmed before the flight rather than after — it is far easier to capture to a specification than to retrofit one.
DroneDeploy supports roughly twenty integrations, including Esri ArcGIS, Autodesk Construction Cloud and Autodesk Forma, BIM 360, PlanGrid, CompanyCam, Box, Egnyte, Amazon S3, Microsoft Azure, OneDrive, Google Drive and Google Cloud Storage.
In practice this means captured site data can be delivered into project management, BIM, GIS and document control workflows a team already runs, rather than arriving as a folder somebody has to redistribute by hand.
You do. Deliverables are yours to store, share, and use however your project requires. Working files are retained for a reasonable period so additional exports or alternate formats can be produced without reflying the site.