Tile38 logo


High-performance database for geospatial and realtime geofencing applications
+ 1

What is Tile38?

It is an open source (MIT licensed), in-memory geolocation data store, spatial index, and realtime geofence. It supports a variety of object types including lat/lon points, bounding boxes, XYZ tiles, Geohashes, and GeoJSON.
Tile38 is a tool in the In-Memory Databases category of a tech stack.
Tile38 is an open source tool with 8.9K GitHub stars and 560 GitHub forks. Here’s a link to Tile38's open source repository on GitHub

Who uses Tile38?

3 companies reportedly use Tile38 in their tech stacks, including ZGPS, dapem, and wulo.

13 developers on StackShare have stated that they use Tile38.

Tile38 Integrations

Python, Node.js, Java, PHP, and C# are some of the popular tools that integrate with Tile38. Here's a list of all 18 tools that integrate with Tile38.
Decisions about Tile38

Here are some stack decisions, common use cases and reviews by companies and developers who chose Tile38 in their tech stack.

Gagan Jakhotiya
Engineering Manager at BigBasket · | 5 upvotes · 59.2K views
Needs advice

I have a very limited but significant use case for spatial index in a routing service. I see these indexes not growing beyond 10,000 geometries for the next 1 year and maybe 100,000 for the next 3 years. The solution needs to be approached from a delivery timeline perspective mostly because the use case also comes with a slightly relaxed compute time SLA and cost optimum implementation PoV.

We have chosen R-Tree based index as a suitable choice for our use case. We are already using Aerospike and MySQL in our stack. MySQL supports R-Tree and has good docs as well. I couldn't find anything specific to R-Tree with Aerospike. Also, generally would like to understand from the performance perspective how these two choices would fare with something like Tile38?

Suggestions beside these are also most welcome.

See more

Tile38's Features

  • Spatial index with search methods such as Nearby, Within, and Intersects
  • Realtime geofencing through webhooks or pub/sub channels
  • Object types of lat/lon, bbox, Geohash, GeoJSON, QuadKey, and XYZ tile
  • Support for lots of Clients Libraries written in many different languages
  • Variety of protocols, including http (curl), websockets, telnet, and the Redis RESP
  • Server responses are RESP or JSON
  • Full command line interface
  • Leader / follower replication
  • In-memory database that persists on disk

Tile38 Alternatives & Comparisons

What are some alternatives to Tile38?
PostGIS is a spatial database extender for PostgreSQL object-relational database. It adds support for geographic objects allowing location queries to be run in SQL.
Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.
JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
Git is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency.
GitHub is the best place to share code with friends, co-workers, classmates, and complete strangers. Over three million people use GitHub to build amazing things together.
See all alternatives

Tile38's Followers
40 developers follow Tile38 to keep up with related blogs and decisions.