What we appreciate most about MapTiler is that it provides a complete and flexible mapping platform at a fair price point. We use it as the central mapping component of our mobility platform, covering public transport, bike sharing, scooter sharing and car sharing, across both native mobile applications (via MapLibre Native) and web applications (via MapTiler SDK JS). These integrations are delivered by multiple service providers, so the ability to manage multiple API keys is particularly valuable. We also make regular use of additional services such as the Geocoding API. Having a single platform for these different use cases has significantly simplified our workflows and reduced integration effort.

A particularly valuable feature for us is the combination of maps, tilesets and datasets within one environment. Most of our data updates are fully automated through the Upload API and scheduled jobs from multiple data providers. This has greatly reduced manual work while improving traceability through separate credentials and detailed change history.

From a UI/UX perspective, the map editor is intuitive and has improved considerably over the years. At the same time, it still allows advanced customisation through the MapLibre Style Specification when more complex styling is required.

We have also been pleasantly surprised by features such as 30-day recovery for maps, datasets and tilesets, as well as the ability to track who made specific changes. These capabilities provide an additional level of operational safety that is particularly important for customer-facing mobility services.

In terms of performance and ROI, the platform has proven reliable for our production workloads over several years. The breadth of functionality, continuous innovation and API-driven automation provide a solid return on investment.

Finally, while we have occasionally encountered technical issues, we value the fact that MapTiler actively develops the platform, takes customer feedback seriously and continues to improve the product. The support experience has not always been perfect, but we have consistently found MapTiler to be responsive, collaborative and willing to work towards a constructive solution when problems arise. Review collected by and hosted on G2.com.

What we like least about MapTiler is that the platform evolves at a very rapid pace and new functionality is often introduced directly into the production environment. While this allows users to benefit from improvements more quickly, it can occasionally result in changing workflows, unexpected behaviour, or regressions in areas that were previously working well.

Over the years, we have encountered a number of issues affecting production usage, including problems within the map editor, inconsistencies between different editing views, dataset and tileset upload issues, and delays in the propagation of changes. In most cases, these issues were eventually resolved, but they sometimes increased operational effort and slowed down day-to-day work.

We would also welcome more detailed error reporting. When problems occur, the error messages available in the MapTiler administration interface are often quite limited, which can make troubleshooting more difficult and time-consuming.

Another area for improvement is permissions and access management. We currently use a five-seat team account, but the current role model is very basic, with only Owner, Editor and Viewer roles available. The Viewer role has little practical value, while Editors cannot be restricted to specific maps, datasets or resources. The same applies to API credentials, where additional restriction and security options would be beneficial.

Within the map editor itself, the user experience is generally good, but some workflows could be streamlined further. Moving changes from test maps to production maps often involves manually copying and reusing layers, and a more structured promotion process would be highly appreciated. In addition, while the editor is very accessible for less experienced users, advanced users would benefit from features that provide deeper support for the MapLibre Style Specification. An integrated AI assistant for styling, validation and troubleshooting would also be a valuable addition.

Finally, although support has always been professional and constructive, we occasionally found that multiple rounds of communication were required before reaching a solution. Faster diagnosis of technical issues and more detailed troubleshooting information would further improve the overall experience.

Overall, most of our criticism relates to operational efficiency, governance and platform stability rather than core functionality. The underlying platform is powerful and capable, but additional focus on error diagnostics, permissions, release management and advanced-user workflows would make it even stronger. Review collected by and hosted on G2.com.