This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
GeoLens
Your team's spatial data: searchable, mappable, shareable
I got tired of watching teams lose control of their own spatial data. You load it into a platform, you build on it, and then leaving turns out to be expensive: the export is lossy, the API is proprietary, and everything downstream has to be rebuilt. It's your data right up until you try to take it somewhere else.
GeoLens is the inverse. Your data sits in your own PostGIS, on hardware you control. Upload Shapefiles, GeoTIFFs, GeoPackages, or CSVs, or register data you already have. You get a searchable catalog and a map builder in the browser, plus OGC and STAC APIs that QGIS, ArcGIS, and MapLibre already speak. Fuzzy search works without setup. If you outgrow GeoLens, you leave with a Postgres database and a set of open standards.
It's Apache 2.0 and self-hosted. It phones home to nothing, so there is no telemetry to opt out of. Deploying takes one command.
This is an early release. The self-hosted distribution is young and some APIs will still move before they settle. If you hit a rough edge, open an issue. I read all of them.
The demo at demo.getgeolens.com is live and you can browse it without an account.
If you work with spatial data, I'd like to know where yours actually lives right now, and how hard it would be to leave.
GeoLens was submitted on Product Hunt and earned 0 upvotes and 1 comments, placing #109 on the daily leaderboard. Self-hosted, open-source GIS data catalog with OGC API support, semantic search, and map builder. Apache 2.0. Deploy anywhere.
GeoLens was featured in Open Source (68.7k followers), Developer Tools (517.5k followers) and Maps (12.9k followers) on Product Hunt. Together, these topics include over 96.6k products, making this a competitive space to launch in.
Who hunted GeoLens?
GeoLens was hunted by Ian Shiland. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how GeoLens stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hey Product Hunt! I'm Ian, and I built GeoLens.
I got tired of watching teams lose control of their own spatial data. You load it into a platform, you build on it, and then leaving turns out to be expensive: the export is lossy, the API is proprietary, and everything downstream has to be rebuilt. It's your data right up until you try to take it somewhere else.
GeoLens is the inverse. Your data sits in your own PostGIS, on hardware you control. Upload Shapefiles, GeoTIFFs, GeoPackages, or CSVs, or register data you already have. You get a searchable catalog and a map builder in the browser, plus OGC and STAC APIs that QGIS, ArcGIS, and MapLibre already speak. Fuzzy search works without setup. If you outgrow GeoLens, you leave with a Postgres database and a set of open standards.
It's Apache 2.0 and self-hosted. It phones home to nothing, so there is no telemetry to opt out of. Deploying takes one command.
This is an early release. The self-hosted distribution is young and some APIs will still move before they settle. If you hit a rough edge, open an issue. I read all of them.
The demo at demo.getgeolens.com is live and you can browse it without an account.
If you work with spatial data, I'd like to know where yours actually lives right now, and how hard it would be to leave.