Earthmover

Name: Earthmover
Brand: Earthmover

AI Native

The cloud platform for scientific data teams

Est 2022|Valuation $26M|Raised $13.3M|26 Ref Customers

LinkedIn 6K|Website|Web traffic 8K|FTEs 11|HQ New York, New York, US

MarketsData Warehouses & Lakehouses Data Catalog

01Competitive Landscape

Narrative analysis

Where Earthmover is differentiated: - Open-source core (Icechunk) and positioning around the Zarr ecosystem, aiming to limit storage-layer lock-in. - Standards-first delivery (OGC EDR, WMS, OPeNDAP/DAP), which supports interoperability with scientific and GIS tooling. - Hybrid architecture: data can remain in customer-managed buckets, while backend services run in a vendor-managed environment. Where alternatives may excel: - TileDB: longer track record in array databases and enterprise sales; potentially more third-party validation and broader non-climate vertical presence. - Databricks + geospatial partners (Esri/CARTO/Felt ecosystem): strong fit if an organization already standardized on Databricks for analytics/ML and wants geospatial functions inside the lakehouse. - Google Earth Engine / Planetary Computer: strong for EO analytics when organizations accept a vendor-managed platform and want immediate access to curated datasets and compute. Market adoption / trend signals: - Public funding announcements and open-source traction (Icechunk open-source repository) indicate early momentum, but mainstream B2B review presence is limited, suggesting the product is still early in broad enterprise adoption.

	Earthmover (Arraylake + Flux + Icechunk)	TileDB (TileDB Cloud)	Google Earth Engine
Starting Price	Quote-based (platform fee + usage-based Flux)	Public pricing page exists but many tiers are contact/tailored	Public usage-based pricing model published
Best For	Teams needing cloud-native array/tensor governance and standards-based delivery (EDR/WMS/OPeNDAP)	Array database + R&D data management, multimodal/scientific datasets	Large-scale geospatial analysis with managed datasets and compute
Key Strength	Customer-managed cloud storage options + open standards (Zarr/Icechunk) + geospatial delivery layer	Mature array DB lineage; broader enterprise positioning	Large curated catalog and scalable geospatial compute ecosystem
Key Weakness	Limited independent reviews; compliance posture not clearly public; quote-based pricing	Potential lock-in to TileDB format/ecosystem; pricing complexity	Less "bring-your-own" governance for proprietary datasets; vendor-managed environment

01Competitive Landscape

Narrative analysis

Where Earthmover is differentiated:

Open-source core (Icechunk) and positioning around the Zarr ecosystem, aiming to limit storage-layer lock-in.
Standards-first delivery (OGC EDR, WMS, OPeNDAP/DAP), which supports interoperability with scientific and GIS tooling.
Hybrid architecture: data can remain in customer-managed buckets, while backend services run in a vendor-managed environment.

Where alternatives may excel:

TileDB: longer track record in array databases and enterprise sales; potentially more third-party validation and broader non-climate vertical presence.
Databricks + geospatial partners (Esri/CARTO/Felt ecosystem): strong fit if an organization already standardized on Databricks for analytics/ML and wants geospatial functions inside the lakehouse.
Google Earth Engine / Planetary Computer: strong for EO analytics when organizations accept a vendor-managed platform and want immediate access to curated datasets and compute.

Market adoption / trend signals:

Public funding announcements and open-source traction (Icechunk open-source repository) indicate early momentum, but mainstream B2B review presence is limited, suggesting the product is still early in broad enterprise adoption.

	Earthmover (Arraylake + Flux + Icechunk)	TileDB (TileDB Cloud)	Google Earth Engine
Starting Price	Quote-based (platform fee + usage-based Flux)	Public pricing page exists but many tiers are contact/tailored	Public usage-based pricing model published
Best For	Teams needing cloud-native array/tensor governance and standards-based delivery (EDR/WMS/OPeNDAP)	Array database + R&D data management, multimodal/scientific datasets	Large-scale geospatial analysis with managed datasets and compute
Key Strength	Customer-managed cloud storage options + open standards (Zarr/Icechunk) + geospatial delivery layer	Mature array DB lineage; broader enterprise positioning	Large curated catalog and scalable geospatial compute ecosystem
Key Weakness	Limited independent reviews; compliance posture not clearly public; quote-based pricing	Potential lock-in to TileDB format/ecosystem; pricing complexity	Less "bring-your-own" governance for proprietary datasets; vendor-managed environment