GeoLensvsTile38
Two self-hosted Geospatial projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| GeoLens | Tile38 | |
|---|---|---|
| Score | 55/100 | 66/100 |
| Rank in category | #3 of 8 in Geospatial | #2 of 8 in Geospatial |
| GitHub stars | 306 | 9 761 |
| Stars, last 30 days | +24 | +16 |
| Stable releases, 12 months | 20 | 2 |
| Latest release | v1.34.0 · 22 Nov 2026 | 1.38.0 · 9 Jun 2026 |
| Setup | Moderate | Easy |
| Official Docker image | No | Yes |
| License | Apache-2.0 | MIT |
| Main language | Python | Go |
Which one should you pick?
Tile38 scores 66/100 against 55/100 for GeoLens, so it is the safer default.
GeoLens ships more often: 20 stable releases in the past year, against 2 for Tile38.
If you want the quickest setup, Tile38 is easier to run; GeoLens needs more configuration.
Key differences
- License: GeoLens is Apache-2.0, Tile38 is MIT.
- Language: GeoLens is written mainly in Python, Tile38 in Go.
- Only Tile38 ships an official Docker image.
- Platforms only GeoLens lists: Helm.
- Platforms only Tile38 lists: Docker, Homebrew, Linux, macOS and 1 more.
- Features only GeoLens lists: 3D Tiles and COPC point cloud hosting, AI-assisted exploration (Ask AI), Data export in multiple formats, Fuzzy keyword search and 4 more.
- Features only Tile38 lists: Command Line Interface, Field and ID filtering in searches, In-memory store with on-disk persistence, Leader / follower replication and 9 more.
GeoLens details →Tile38 details →All Geospatial projects →
Swap a project
Keep GeoLens, compare it with
Keep Tile38, compare it with