Sandbox
Try it on a side project
$0 / month
- 1 database, 1 tile source
- Rebuild every 24 hours
- 50k tile requests / month
- 100 geofences, 100 tracked users
Pay for the sources you run and the requests you serve. Your database stays yours; we never bill on rows.
Try it on a side project
$0 / month
For a product with a map in it
$29 / month
For teams whose data moves all day
$149 / month
Dedicated workers, your cloud or ours
Let's talk
| Limit | Sandbox | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Tile sources | 1 | 5 | 25 | Unlimited |
| Databases | 1 | 2 | 10 | Unlimited |
| Tile requests | 50k / mo | 1M / mo | 10M / mo | Custom |
| Geofences | 100 | 5,000 | 100,000 | Unlimited |
| Tracked users | 100 / mo | 5k / mo | 50k / mo | Custom |
| Georeferenced maps | 1 | 10 | 100 | Custom |
| Updates | Rebuild every 24 hours | Live, seconds after a write | Live, seconds after a write | Live, seconds after a write |
| Custom tile domain | No | No | Yes | Yes |
Go over your tile limit on a paid plan and tiles keep serving; we email you before anything changes. The Sandbox pauses at its limit.
Yes, with one caveat: live updates use Postgres LISTEN, which doesn't work through transaction-mode poolers. Use the direct connection string (port 5432 on Supabase, the non-pooled host on Neon). If you can only use a pooled URL, pick snapshot mode and we'll rebuild on a schedule.
Typically one to three seconds from COMMIT to a fresh tile. Notifications are debounced into small batches, so a bulk edit of 10,000 rows re-renders each affected tile once instead of 10,000 times.
Anything that reads Mapbox Vector Tiles and TileJSON: MapLibre GL, Mapbox GL, OpenLayers, Leaflet with a vector-tile plugin, deck.gl, QGIS.
Yes. MapSocket runs tilefeed, which is MIT licensed. Every source has an Export config button that gives you the tilefeed TOML, and you can download the MBTiles or a PMTiles archive at any time.
A distinct userId that sent at least one /v1/track call in the month. Calls to /v1/context and geofence search don't count towards it.
A role that can SELECT the tables you publish. We recommend a dedicated read-only role; the dashboard gives you the exact CREATE ROLE and GRANT statements. For live updates you (not us) run a small trigger function on each table, which needs table-owner rights once.
Encrypted with AES-256-GCM before it touches our database, with the key held outside it. It's decrypted only inside the worker that builds your tiles, and it's never shown again in the dashboard or API, only host, database and user.