The editorial argues the app's durability comes from its non-profit structure and lack of venture funding, not its feature set. Because no one is pressured toward a monetization inflection point, the offline-first, no-ads, no-trackers philosophy can persist — which is the exact failure mode that killed Maps.me after the Daegu acquisition.
The editorial reframes the competitive question: the moat was never the app UI but the tile pipeline, routing graph, and POI database. After 20 years, OSM has made the first two usable and POI density is now good enough in dense areas that most everyday queries feel indistinguishable from Google Maps.
The submitter surfaced Organic Maps to HN where it climbed to 503 points, signaling strong developer endorsement of the offline, tracker-free approach. The top-voted thread consensus acknowledged weaker turn-by-turn, uneven POI density outside Europe, and missing transit routing, but kept returning to the point that the app is dependable and won't be enshittified.
Organic Maps hit the top of Hacker News this week with 503 points — a rare score for a project that has been quietly shipping since 2020. The pitch on organicmaps.app is refreshingly boring: a free offline maps app for iOS and Android, built on OpenStreetMap data, with no ads, no trackers, no accounts, and no cloud. It does turn-by-turn navigation for cars, bikes, and hikers. It works on a plane. That's it.
What makes Organic Maps interesting isn't the feature list — it's the origin story. The app is a hard fork of Maps.me, the OSM-based navigation app that was acquired by Daegu Limited in 2020 and promptly gutted: ads injected, tracking added, the offline-first philosophy quietly abandoned. A group of the original Maps.me engineers walked, kept the AGPL codebase, and rebuilt it under a non-profit structure. Six years later, the fork is more actively maintained than the original, ships on F-Droid, the App Store, and Google Play, and has zero venture funding pressuring it toward a monetization inflection point.
The HN thread surfaced the usual suspects — turn-by-turn is rougher than Google Maps, POI density is uneven outside Europe, transit routing is missing — but the top comments kept circling one point: it just works, and it will keep working, because nobody has an exit strategy that requires breaking it.
The interesting question isn't whether Organic Maps is technically better than Google Maps. It isn't. The interesting question is why a small volunteer team can ship a maps app at all — and the answer reframes what "competing with Google" actually costs in 2026.
The moat around Google Maps was never the app. It was the tile pipeline, the routing graph, and the POI database. OSM has spent 20 years building the first two into something usable, and the third — points of interest — is now good enough in dense areas that most users won't notice a difference for the queries they actually run ("nearest coffee," "gas station on my route," "how do I get to this address"). Organic Maps consumes that upstream work and adds the last-mile: a rendering engine, a routing UI, offline tile packaging, and turn-by-turn voice guidance. That's maybe 100k lines of C++ and a handful of maintainers.
Compare that to what Google Maps needs to sustain: satellite imagery contracts, Street View fleets, real-time traffic ingestion from billions of Android devices, a 24/7 SRE org, and an ads business that pays for all of it. Organic Maps doesn't try to compete with any of that. It ships the 80% of the product that most people use most of the time, and it doesn't charge for it because it doesn't have to.
The community reaction on HN was more emotional than technical, and that's the tell. Comments about "finally an app I can trust with my location" outnumbered comments about routing quality by roughly three to one. The wedge Organic Maps has isn't performance — it's governance. In 2026, "this project cannot be acquired and ruined" is a feature you can market, because everyone who's been on the internet for a decade has watched it happen to something they loved. Maps.me itself is the cautionary tale baked into the product's origin.
There's also a quieter story here about what AGPL actually buys you. Maps.me's acquirers kept the codebase but not the community. The engineers took the license and walked. The AGPL didn't stop the acquisition, but it made the fork trivial, and it made the fork's community stickier than the original's. That's the license working exactly as designed — and it's a case study worth citing next time someone argues that copyleft is obsolete.
If you ship anything with a "show this on a map" feature, the economics have shifted. Google Maps SDK pricing has drifted upward for years — $7 per 1,000 map loads on the standard tier, more for advanced features — and every startup that hit scale has had the same panicked meeting about their maps bill. The alternatives used to be Mapbox (better pricing, still per-request) or self-hosting OSM tiles (operationally painful). Organic Maps doesn't change those trade-offs directly, but it validates the underlying stack: MapLibre GL, OSM vector tiles, and OSRM or Valhalla for routing are now a production-grade path if you're willing to do the integration work.
The pragmatic move for most teams isn't ripping out Google Maps — it's stopping the drift into deeper SDK lock-in. Use Google Maps for the surface where users need Street View and live traffic. Use MapLibre plus OSM tiles for internal dashboards, embedded pickers, admin tools, and anywhere the map is a UI element rather than a navigation product. Every screen you migrate is a screen that stops metering per view.
If you're building a mobile app with an offline mode — logistics, field service, outdoor recreation, anything that has to survive a bad cell signal — Organic Maps is worth studying as a reference implementation. The tile-packaging strategy, the storage-vs-detail trade-offs, the routing graph compression: it's all in the repo, all AGPL, and all battle-tested by users who actually take the app hiking.
Organic Maps won't dethrone Google Maps, and it isn't trying to. What it demonstrates is that the ceiling for community-owned infrastructure keeps rising, and the floor for what a small team can ship keeps dropping. A decade ago, "build an OSM-based navigation app" was a 50-person company. Today it's a non-profit with a handful of maintainers and a Patreon. Whatever the next Google Maps looks like, it probably won't be built by a company at all — and that's the shift worth paying attention to, whether you're picking a maps SDK or picking which open-source projects deserve your recurring donation.
There is also CoMaps (https://www.comaps.app/) which is a fork of Organic Maps, after concern over the governance of Organic Maps https://itsfoss.com/news/organic-maps-fork-comaps/
I would recommend people use comaps instead which is the actual FOSS fork. OM has a long history of malicious behaviour like quietly adding ads, turning a part of its previously open sourced code proprietary and misappropriating donations. OM has lost most of its community a year ago to comaps and a
The quality of the maps is getting better, much more useful and detailed than Google Maps. I find it much easier to locate myself on Organic Maps than Google Maps. For example parks are only a green blob on Google Maps, while benches, walking paths, drinking water points, toilets and other landmarks
To the best of my knowledge, Organic Maps is a dying project.CoMaps was forked from Organic Maps because of shift in how things were being done and ignored. I mean, those in IT know very well how that is ending.CoMaps is highly active and receiving new features release by release.If you wanna use a
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.
Organic Maps was my go to app for a navigation app where you can fix errors yourself immediately! So much better than having to work for free on the proprietary apps, and hope they accept your editsThere’s a fork from one year ago, CoMaps, that is gaining different featuresE.g., I am adding CarPlay