Fast by design
Rust NIFs for tile encoding, CQL2 filters and geoprocessing.
One server for the map under every product you build.
Vector tiles, base-map styles and the OGC APIs, from your own data, on your own infrastructure. It already draws the map under our own location products.
From your data to the map
MVT straight from PostGIS tables and functions, plus PMTiles, MBTiles and composite sources.
Eight designed styles that stay quiet under your data, with sprites and glyphs served alongside.
OGC API Tiles, Features and Processes and WMTS 1.0.0: sixteen conformance classes from one server.
Ready to operate
Caching
gzip, ETags and an in-memory or Redis cache.
Operable
A health check, Prometheus metrics, API keys, rate limits and CORS.
Honest under failure
When a database is down it answers 503 with Retry-After instead of hanging.
Everything that draws a map can use it
Your apps speak the standards they already know, and your data stays in your database.
Tiles
PostGIS
PMTiles
MBTiles
Your app
OGC clients
Redis
Under the hood
- One Elixir server, with Rust where speed matters
- TileJSON, gzip, ETags
- CQL2, paging, bbox, six CRS in OGC API Features
- Buffer, simplify, centroid, hull and intersection as jobs
Does your product depend on someone else’s map?
We’ll show it to you working, using the product and its demo materials, and talk through your case.
Ask for a demo