A map that keeps working: the importance of maintenance and hosting

A digital map application lives in an ecosystem that is constantly evolving: browsers and devices are updated, security vulnerabilities emerge, data sources change and usage patterns evolve over time. What runs smoothly and stably on day one can become slower or start showing errors months later due to changes in technology or infrastructure. A yearly service agreement makes it explicit that Nazka is responsible not only for building the map, but also for keeping it operational throughout its entire lifecycle. In this way, a map application is no longer a static end product, but a service that can grow along with the digital landscape.

Concrete example: WayToGo, all shared mobility on one map

An illustrative example is the WayToGo map, from a network organisation that helps people find their way in shared mobility. On the online map, shared cars, shared bikes, shared cargo bikes and shared e‑scooters from different providers are brought together, allowing visitors to discover the shared mobility offer in their area with just a few clicks.

Shared mobility is growing rapidly and the offer changes quickly: new operators enter the market, existing ones expand their fleets or adjust their service areas. The map has to keep pace with that, both in terms of content (updates of data and layers) and technically (high‑performance hosting, scalable infrastructure and robust integration with external sources). Thanks to the yearly hosting and maintenance agreement, Nazka can continue to optimise the WayToGo map, integrate new datasets and keep the application safe and stable.

Hosting and maintenance: what is included?

Nazka’s map applications run in a cloud environment in data centres within the European Union. The full stack is hosted there: map application, databases, engines, scripts and media.

Hosting includes, among other things:

• capacity and server space for application, database and engines
• processing and storage of data, including traffic between servers and end users
• scalability when the application grows or experiences peak loads

Maintenance provides for:

• necessary (security) updates of all software components
• fixing bugs that come to light after launch, within the agreed scope
• minor text changes to keep content up to date

Larger changes to functionality, structure, design or repeated content updates are, if needed, carried out on demand or via a separate quote. This keeps it clear which efforts are covered by the yearly service and which fall under further development.

Monitoring, security and backups

Putting a map “online” is one thing; actively monitoring it is the next step. The applications are continuously monitored, as are the underlying databases, engines, scripts and external web services. Possible failures are detected in real time, enabling rapid intervention and keeping downtime to a minimum. The cloud infrastructure is monitored and automatically scaled up when necessary to guarantee performance. A well‑designed backup strategy and reliable cyber security are integral parts of the service, ensuring that data remains protected and applications can be quickly restored in case of incidents.

Service desk, cookies and user statistics

We always foresee a central point of contact for support related to the map application. Our clients and partners are quickly directed to the right expert and can count on efficient follow‑up of their questions or reports.

Privacy and analytics are also structurally taken into account. Cookie implementation complies with GDPR requirements, with a clear cookie statement and a cookie banner that visually matches the application. If desired, user statistics are collected via, for example, Google Analytics or a European provider like Plausible.io, with a dashboard for project managers. This offers insight into reach and usage patterns and forms a valuable basis for future improvements.

Mapframe as a foundation

Every new map application starts from Mapframe, Nazka’s own framework for high‑performance digital maps. This framework bundles reusable building blocks that have been refined in practice and makes it possible to deliver a robust and scalable result quickly. Mapframe is not sold, but licensed. The right of use is part of the yearly service, together with hosting, maintenance and support. This continuity allows Mapframe to be further developed in a targeted way, security updates to be implemented and ongoing support to be provided for new browser and device versions.

Why a yearly service agreement makes the difference

A yearly hosting and maintenance agreement provides:

• continuity: map applications keep functioning as intended, even as the environment changes
• security: security updates, monitoring and backups are structurally embedded
• predictable costs: clear agreements instead of ad‑hoc interventions
• a long‑term partnership: Nazka thinks along over the long term and grows with the applications

As a result, a map is not only a strong product at launch, but a reliable digital service that remains relevant and available year after year. A map is, after all, never finished.