1. Start with a template
Start from a preconfigured model for local authorities, with asset types and relationships you adapt to your organisation.
Map your local government IT to build a smart city that lasts
Business applications piled up over successive terms, services shared with the inter-municipal body, GDPR obligations and transformation projects: local government IT has become hard to grasp. Boldo helps you structure it and make it readable, from the CIO to elected officials.
Boldo · Aperçu produit
The tool's ease of use and strong visual impact allowed us to reinforce our Smart Citadelle roadmap and present it to elected officials with clear, reliable and engaging data.
Explore the Antibes use case
Local government IT under pressure
Civil registry, urban planning, childcare, finance, roads: every department uses its own applications, some chosen years ago, some shared with the inter-municipal body or a partner syndicate.
Knowledge often stays scattered across spreadsheets, diagrams and a few experts. Each pooling, digitisation or modernisation project then starts with another round of investigation.
In 2024, France's national cybersecurity agency (ANSSI) handled 218 incidents affecting local authorities, an average of 18 a month (CERT-FR, 2025).
It is hard to protect your IT or properly document data processing without knowing which applications handle which information, for which services and under whose responsibility.
What a map changes
- A shared overview across the CIO, departments and management
- Dependencies between missions, applications, data and providers made visible
- A structured basis for pooling and IT master plans
- Documented answers to GDPR and cyber requirements
- A roadmap that is easier to explain to elected officials
Build a first usable map quickly
Start from a model built for local authorities, reuse the data already available and focus first on the services and assets your decisions require.
2. Reuse your data
Import your applications, services, teams and relationships from CSV or XLSX files, then preview the changes before validation.
3. Adapt and validate
Complete the model with the departments involved and formalise the responsibilities, flows and dependencies specific to your territory.
Pooling
Map what is owned, shared or pooled
An application can be used by a town, operated by the inter-municipal body and covered by a contract held by another entity. These responsibilities quickly become hard to track in a flat inventory.
Boldo connects each application to the local authorities, services, teams and providers that use or operate it. This is how you tell apart the assets owned by one entity, the pooled services and the dependencies on the territory's partners.
- Tell apart owned and pooled applications
- Identify the entity responsible for operations
- Link contracts to the benefiting local authorities
- Prepare convergence or separation decisions
Connect public services to the applications that support them
Civil registry, social action, mobility, urban planning or facilities management: every mission depends on different applications, data, providers and teams.
Typed relationships let you start from a public service or a capability of the local authority, then trace back the IT components that support it.
This is how you can identify sensitive dependencies, applications with no clearly assigned owner and the services affected by a change.
- Understand the dependencies behind each service
- Identify the applications critical to continuity
- Trace back the responsible teams and providers
- Analyse impacts before a transformation
Impact analysis
Steering
Make the roadmap understandable to everyone
Technical teams, business departments and elected officials do not need the same level of detail. Boldo lets you build several readings from a common base.
Filtered inventories, diagrams, nested maps and charts make projects, responsibilities and dependencies easier to present.
The history keeps the changes to the repository, while shared views support master plan decisions and roadmap tracking.
- Present a summary view to management and elected officials
- Keep the decisions and their associated responsibilities
- Track projects and their impact on the asset base
- Adapt each representation to its audience
One base for several use cases
A map is not an isolated deliverable. It becomes a common basis for the local authority's main digital projects.
- Master plan01 / 04
Structure the IT roadmap
Connect objectives, projects and the assets involved to build a roadmap grounded in the existing asset base.
- Pooling02 / 04
Compare perimeters
Identify shared applications, responsibilities and opportunities for convergence between local authorities or shared services.
- Resilience03 / 04
Analyse critical dependencies
Trace back the applications, data, providers and infrastructure needed to keep priority services running.
- GDPR04 / 04
Document data processing
Connect applications, data, services and owners to make the work of the DPO and security teams easier.
Feed the map from what already exists
The first information is often already available in application inventories, contract files, technical exports or master plan documents.
- Files
CSV / XLSX import
Reuse the existing applications, teams, contracts and relationships, then map the columns to the properties of your model.
- Programmable
REST API v1
Build the syncs you need when some sources must keep feeding the map.
- Contribution
Validation by departments
Give business and technical referents the rights they need to check and enrich the information within their scope.
A tool built for local government teams
- Hosted in France with Scaleway
- Access control through roles and domains
- Preconfigured model, adaptable to your organisation
- Views accessible to technical and non-technical teams
- Change history and clearly identified responsibilities
- Pricing from €39 per editor per month
Frequently asked questions about local government IT mapping
Boldo can be used by towns, inter-municipal bodies, metropolitan areas, departments, regions or joint syndicates.
A single user can belong to several Boldo organisations. A shared team can therefore work across several contexts while keeping distinct data and rights for each local authority.
Explore Boldo on a local government model
See how to connect public services, applications, data and responsibilities in a living territorial map.
Request a demo
30 minutes focused on your local authority and its digital challenges.
By submitting this form, you accept our Privacy Policy.