Introducing Tileflow
Hi đź‘‹ We are introducing Tileflow: a code-first way to design, preview, and ship product maps without moving the work into a separate map studio.
We built it because today’s mapping tools are powerful, but often too complex for the teams that just want maps to behave like the rest of their product. Styles live somewhere else, changes are hard to review, and getting from “this looks right” to production can involve too many hidden steps.
Tileflow brings that workflow back into your repo: typed config, basemaps, themes, modules, labels, POIs, icons, static images, local previews, and deploy-ready MapLibre output in one place.
For tiles, we are starting from reliable OpenStreetMap data through an OpenMapTiles-compatible pipeline, with attribution built into the generated styles. Data quality, freshness, coverage, and regional detail will keep improving release after release.
We are also investing in the serving layer itself: dedicated tile infrastructure, aggressive caching, and a delivery path designed for fast warm loads, predictable latency, and production traffic rather than demo-only maps.
There is a lot more coming. The focus from here is developer experience and ease of use: fewer decisions, clearer defaults, better data, faster previews, and maps that feel natural to build with.