The short operational comparison
Both products can participate in a photogrammetry workflow, but their centres of gravity differ. Cloud reduces the friction of shared access; Matic provides local project control and the Standard/Analyst/Pro survey workflow.
| Decision factor | PIX4Dcloud | PIX4Dmatic |
|---|---|---|
| Processing environment | Online, subject to plan and supported pipeline | Local desktop, Windows or macOS |
| Core strength | Shared 2D/3D review, measurements and collaboration | Photogrammetric processing and survey-data analysis |
| Plan structure | Starter, Pro; enterprise arrangements separately | Standard, Analyst, Pro |
| Repeat construction sites | Pro sites, timelines and comparisons | Project-specific desktop analysis and exports |
| Terrain and advanced vectorisation | Not the equivalent of Analyst | Analyst or Pro |
| Restricted-data route | Requires approved hosting and sharing | Local processing can simplify governance; licence/IT needs remain |
When cloud is the sensible centre
Choose a cloud-centred route when several authorised roles need browser access, field uploads should move quickly into review, and repeat-site collaboration is more important than advanced desktop vectorisation. Pro is the relevant plan for sites, timelines, design overlays and repeat comparisons.
When desktop is the sensible centre
Choose a Matic-centred route when imagery must remain within a controlled processing environment, when operators need detailed calibration and project control, or when Analyst/Pro terrain and CAD workflows are required. Reviewers can receive agreed exports without every reviewer needing a processing seat.
A combined workflow can be deliberate, not duplicative
Some teams process or inspect locally, then publish an approved dataset for stakeholder review. Others upload field captures to cloud and download supported results for desktop analysis. The combined route should identify the authoritative version at each step, processing credits and licence dependencies, file-transfer responsibilities and the point at which a shared model becomes an issued deliverable.
Evaluate using one representative project
Run the same project brief through the proposed route: capture, coordinate setup, processing, QA, analysis, review, export and archival. Record time, manual transfers, user roles, failure points and the exact output each role needs. This reveals operational fit more reliably than a feature checklist alone.