// the take
MapStore is a Java/React web-GIS framework for building maps, dashboards and geostories with 2D (OpenLayers, Leaflet) and 3D (Cesium) rendering, speaking standard OGC services like WMS, WMTS, WFS and CSW. It's aimed at GIS teams and public-sector/environmental orgs who want a self-hosted alternative to commercial webGIS portals and already have GeoServer or similar OGC endpoints to point it at.
Three rendering engines (OpenLayers, Leaflet, Cesium) under one plugin API means you can swap 2D/3D without rewriting app logic. Native OGC support (WMS/WMTS/WFS/3DTiles/CSW) means it plugs straight into existing GeoServer or ArcGIS infrastructure instead of requiring a proprietary format. Release discipline is real: separate DEV/QA/STABLE deploy targets, CI with coverage tracking, and a documented backport/release-branch process rather than ad hoc tagging. GeoSolutions offers paid support, so there's a commercial backstop if you get stuck, which is rare for a project this size.
Deployment is a full J2EE stack — Tomcat, a WAR file, Maven build, plus a GeoStore persistence layer (H2 or Postgres) just for app config/user data — there's no lightweight static-hosting path. 664 stars for a project with this much surface area signals a small community outside GeoSolutions' own client base, so you'll be leaning on the mailing list or paid support more than Stack Overflow. The React/Redux frontend and Java backend are two separate build toolchains (npm + Maven) you maintain in lockstep, which raises the bar for anyone wanting to contribute a small fix. It's built for institutional GIS workflows (OGC-first); if you just want a quick embeddable map widget, this is a lot of operational weight for that job.
We read the README, the directory tree and a key source file in October 2026. Nobody pays to be listed. How we judge →