KIRI Innovation (麒砺创新)

| Aspect | KIRI Engine | Polycam | RealityScan | |--------|-------------|---------|-------------| | Starting Price | Free tier; published annual Pro pricing (Official vendor product page) | Free tier; published monthly and annual individual pricing; published business/enterprise per-user pricing (Official vendor product page) | Licensing and feature details not fully surfaced in captured snippets | | Best For | High-quality object scans; users needing 3DGS-to-mesh and mobile-first capture | Spaces/floor plans/measurement-oriented workflows; teams; enterprise controls | Users in the broader photogrammetry ecosystem; details depend on licensing and integration needs | | Key Strengths | Competitive pricing including a free tier with relatively generous scan/export allowances; user-reported higher detail in some cases; 3DGS mesh export capability | Measurement and floor plan features; structured team and enterprise positioning; broad export options | Established brand association within some photogrammetry ecosystems; licensing clarity in official documentation | | Key Weaknesses | Cloud dependence and potential queue times; limited public evidence of enterprise compliance; inherent photogrammetry failure modes remain | Higher cost for some individual users; tradeoffs in detail vs upload size reported by community members | Pricing and feature clarity not fully verified in this run | - Direct competitors and key differentiators - KIRI vs Polycam: - Vendor-authored comparisons exist and should be treated as marketing; independent user discussions emphasize perceived fidelity differences and practical constraints such as upload limits. - KIRI vs Luma: - Users compare results and realism, but Luma’s product suite and pricing can change; confirm the specific Luma workflow relevant to your needs. - Pricing comparison (value proposition) - KIRI's published annual Pro pricing is lower than some competitor individual pricing options cited for Polycam in this capture. - When customers choose competitors instead (and why) - Polycam may be preferred when teams require enterprise controls, floor plan workflows, or when users need larger/longer uploads. - Open-source local options (WebODM/Meshroom) may be preferred when offline control, reproducibility, and local processing are required.