Skip to main content

Welcome to Caplo

Caplo helps teams model their architecture as reusable data, not as isolated drawings. You can maintain a shared repository of applications, capabilities, processes, data objects, vendors, and other architecture elements, then use that repository in diagrams and reports.

Origin Story​

Caplo exists because enterprise architecture teams are often forced to choose between two imperfect options. Whiteboarding and diagram tools make workshops and collaboration easy, but the result often lives in disconnected diagrams, slides, and spreadsheets. Traditional EA tools keep structured data, but they are harder to adopt broadly and the repository can drift away from day-to-day design work.

Caplo is designed to close that gap. Diagrams, repository data, reports, and AI all work from the same shared digital twin, so each interaction can improve the architecture model instead of creating another isolated artifact. The goal is broader adoption without losing rigor: a tool that is collaborative enough for workshops, structured enough for analysis and governance, and grounded enough for AI-assisted decisions.

Caplo is useful when you want to answer questions such as:

  • Business Design: How do goals, capabilities, processes, and applications fit together for this initiative?
  • Application Portfolio Management: Which applications drive the most cost, risk, or lifecycle pressure in our portfolio?
  • M&A: Where do buyer and seller landscapes overlap, and what should be merged, kept, or retired?
  • Dependency Insights: What is the critical path behind this application, API, or data flow?
  • Data Sovereignty: Which sensitive data must stay in a region, and which systems handle it?
  • Compliance: Which controls have linked evidence, clear owners, and open gaps across our systems?

Platform tour​

Caplo is organized around a few main areas:

  • Overview is the place to find and organize diagrams, saved repository views, and saved reports.
  • Repository is the structured list of reusable entities and relations in your workspace.
  • Diagrams are visual views that can reuse repository entities and relations.
  • Reports turn repository data into timelines, landscapes, bubble charts, and custom charts.
  • Settings is where you manage your profile, company profile, workspace members, custom properties, and diagram visibility.

What you can model​

Most Caplo work starts with a set of entities and relations. For example:

  • An application realizes a business capability.
  • A process uses an application.
  • A data object is accessed by an application.
  • A vendor supplies an application.
  • A work package changes a group of applications.

You can then show that same information in different ways: a repository grid for cleanup, a diagram for a workshop, and a report for an executive review.

Where to start​

If you are new to Caplo, start with Getting started. If you already understand the basics, jump to Repository, Diagrams, or Reports.