Tareky Stack
The Tareky platform, on your own servers.
The same API, search, routing, tiles and sign-in that run Tareky, packaged as containers. Your data stays on your infrastructure and you decide when anything changes.
Why run it yourself
Your data stays with you
Search, routes and your own datasets are served from servers you control, in the country you choose to host in.
Your own datasets and styles
Upload your own layers, fonts and map styles and serve them beside the Iraq basemap, without them leaving your infrastructure.
Request shapes you already use
Directions, matrix, map matching, optimisation, static images and tilequery follow Mapbox’s and OSRM’s shapes, so most clients change only the host.
You pick the update day
You decide when an update goes live. The road graph rebuilds itself every week from the latest OpenStreetMap data.
What is in the box
API
Search, geocoding, reverse geocoding, plus codes and nearby places, with keys, limits and metering.
Routing
Directions, matrix, map matching and trip optimisation on OSRM, for cars and on foot.
Tiles
Our Iraq vector basemap, built from OpenStreetMap and served by Martin, with your own tilesets beside it.
Traffic
Anonymous probe intake and speed aggregation. It starts in shadow mode, so you see its speeds before routing uses them.
Sign-in
Single sign-on over OIDC and SAML, and SCIM provisioning, for your organisation’s people.
Data workers
They turn uploaded vector and raster data and fonts into tiles and glyphs you can style.
How it runs
You bring the database and storage
A PostgreSQL database with PostGIS and pg_trgm, and S3-compatible object storage.
One server, one command
Clone, fill in the environment file and start the containers with Docker Compose. The database is brought up to date on first start.
Build the map
The first basemap takes about an hour to build and the road graph about five minutes.
It keeps itself current
The road graph rebuilds every week from the latest OpenStreetMap extract. Tiles refresh when you publish a new basemap.
What it needs
A server
Ubuntu 24.04 with Docker. The single-server layout is sized for 8 vCPU, 24 GB of memory and 100 GB of disk.
A database
PostgreSQL with PostGIS and pg_trgm, managed or your own. It is not part of the containers.
Object storage
Any S3-compatible bucket, for map files, uploads and backups.
A domain
Hostnames for the API, tiles and sign-in. The bundled Caddy terminates HTTPS.
Iraq data
The map data we build and test is Iraq’s. Another region needs its own data build, which is a project, not a setting.
Terms are agreed for each project
Licence, support and price are set in writing for each deployment. Tell us what you need to run, where and for whom, and an engineer will reply with what is possible.
The basemap is built from OpenStreetMap, so “© OpenStreetMap contributors” stays visible on every map you draw.