Structured inventory
Browse the assets, their properties and their relationships according to the structure defined in your metamodel.
An enterprise architecture tool connected to reality
Your models reflect the IT landscape the day you present them. As it evolves, the diagrams drift away from reality. Boldo connects your assets, their dependencies and your views in a living repository.
The deliverable ages. The repository has to live.
A diagram exported into a presentation is a snapshot. As the IT landscape evolves, it becomes hard to know whether it still reflects the real applications, technologies and dependencies.
In Boldo, every view stays connected to the assets and relationships it rests on. When an element evolves, the model keeps its consistency without forcing you to rebuild every document.
You no longer just produce deliverables: you maintain reusable knowledge for the analyses, trajectories and architecture reviews to come.
What model fragmentation leads to
- Inventories and diagrams that gradually diverge
- Dependencies documented across different documents
- Modeling conventions specific to each project
- Impact analyses that depend on a few experts
- Architecture decisions whose context is lost over time
A flexible metamodel, not a straitjacket
Asset types, properties and relationships follow your organization's vocabulary and conventions. The default metamodel is a starting point, not a doctrine.
Your metamodel
You define the structure your analyses need:
- asset types for applications, capabilities, processes, technologies, data and teams
- typed properties: text, number, date, boolean, single or multiple choice
- directional relationships that represent real dependencies
- a unique key per type to make imports and updates reliable
Start with one domain, one program or one specific question. You then extend the model as new needs appear, without trying to cover the whole organization from the outset.
Impact analysis
Make the model answer your architecture questions
Which applications support this business capability? Which processes depend on an end-of-life technology? Which assets will be affected by a platform change?
Typed relationships let you find the elements concerned and walk through their dependencies. You analyze the model from a 360 page, a view or a diagram, without losing the link to the source data.
Impact analysis stops being a memory exercise. It becomes readable, verifiable and reusable.
One repository, as many readings as audiences
An architect, a business owner and an executive committee do not approach architecture with the same level of reading. Inventories, diagrams, maps and dashboards use the same objects and the same relationships: you adapt the reading, not the data.
Collaborative diagram
Represent a portion of the architecture and work in real time during your workshops.
Nested map
Build a hierarchy from the relationships, for example between domains, capabilities and applications.
Filtered view
Isolate an analysis scope with the columns, groups and filters you need.
Dashboard
Combine charts and indicators into a document usable in an architecture review or committee.
One data point, many views
When an asset evolves, every diagram, map and table that relies on it uses the same information.
The ease of use and the flexible metamodel let us map the IT landscape and the organization very quickly.
Discover IT landscape mapping
The architecture work where the model makes the difference
A single repository can support several approaches, provided it keeps the relationships, states and decisions that make it possible to understand how the IT landscape evolves.
- Mapping01 / 04
Structuring the IT estate
Connect applications to the capabilities, processes, technologies and data they involve. You move beyond the limits of a flat inventory and build a model usable for future analyses.
Structure your IT mapping - Trajectory02 / 04
Target architecture and migrations
Represent the current state, the target and the intermediate states. Statuses and relationships help identify the dependencies that condition each step of the trajectory.
Frame an application migration - Obsolescence03 / 04
Technologies and lifecycles
Connect technologies to the applications and processes that depend on them. You identify the assets exposed when a version, a platform or a component reaches end of life.
Explore the features - Decision04 / 04
Architecture principles and decisions
Document a decision, the assets concerned and the associated impacts. The context stays accessible in the repository, beyond the report or the document in which the decision was presented.
Read: the evolving role of the enterprise architect
Contribution
Distribute knowledge without losing control of the model
When knowledge rests on a single person, every departure weakens the repository. Boldo lets domain experts contribute on the assets they know, while the architecture team keeps control of the structure and conventions of the model.
- A domain expert enriches their assets without changing the metamodel
- An architect keeps control of types, properties and relationships
- Every change is logged and attributed to its author
- Roles frame what can be read and modified
- Access domains isolate sensitive scopes
Feed the repository from what exists
Your first material often already exists as exports, extractions, legacy files or data from other tools. Boldo takes it in and structures it according to your metamodel.
- Files
CSV / XLSX import
Map columns to properties or relationships, choose a stable key and preview the changes before validating them.
- Programmable
REST API v1
Create, update and query assets and their relationships from your scripts. Build the syncs you need with your teams.
- AI assistants
Read-only MCP
Give compatible assistants read access to your data, within each user's permission scope.
Accessible to get started, clear on pricing
Plans start at EUR 39 per editor per month, with a 14-day free trial. Boldo training, from 4 to 16 hours, supports readers, editors and administrators and is eligible for OPCO funding.
Frequently asked questions about enterprise architecture tools
No. You define the asset types, properties and relationships that match your framework, whether it draws on a standard or on your own practices. Boldo claims no native compatibility with any particular framework.
This flexibility lets you choose the relevant level of detail. In practice, a model centered on the questions to address is often more useful than an exhaustive transposition of a standard.
Test Boldo on a real architecture question
Bring a scope, a metamodel or a trajectory to structure: see how to model dependencies, analyze impacts and keep your views up to date.
Book your demo
30 minutes dedicated to your metamodel and your use cases.
By submitting this form, you accept our Privacy Policy.