Skip to content
Albumi Docs

What is Albumi

Albumi is an enterprise architecture management (EAM) platform. You use it to keep a current-state model of your IT landscape — the applications, the data flows between them, the technology underneath, and the business capabilities they support — and to manage changes to that model through a review workflow.

What you can do with it

Section titled “What you can do with it”
  • Describe applications, integrations, data objects, business capabilities, IT components, and organizations.
  • Link them: applications to the capabilities they realize, integrations to the data they carry, applications to the technology they use.
  • Track lifecycle: long-lived entities move through Plan → Phase-In → Active → Phase-Out → End-of-Life, based on dates you set. There is no status dropdown; status is derived from dates.
  • Analyze impact: “what depends on application X?”, “what carries the Customer data object?”, “what breaks if we retire Y?”.
  • Govern changes: propose a change, route it to a review board, approve and implement it with a full audit trail.
  • Automate with AI: an MCP server exposes the same operations to AI agents, so a Claude, Cursor, or other MCP-compatible session can generate or update the landscape from existing documentation.

Who uses it

Section titled “Who uses it”
  • Enterprise and solution architects, as the primary daily users.
  • IT portfolio managers and CTOs, for portfolio-level views and decisions.
  • Change owners and project leads, to scope and track landscape changes.
  • Review boards, to approve architectural changes.

Entity model

Section titled “Entity model”

Albumi’s data model has seven entity types:

  • Application — a piece of software used by the business.
  • Integration — a data flow from one application to another.
  • Data Object — a logical business data concept (Customer, Order, Invoice).
  • Business Capability — what the business does, named independently of how it does it.
  • IT Component — a technology (database engine, language, framework, middleware) used by applications.
  • Organization — a node in the company structure; used for classification and ownership.
  • Initiative — a planned change effort affecting the landscape.

Everything you edit on the landscape is one of these seven. Governance constructs — Architecture Change Requests, review boards, review sessions — sit on top of that model and coordinate how it is changed.

What Albumi is not

Section titled “What Albumi is not”
  • Not a CMDB. It models the logical landscape, not runtime infrastructure. Server instances, VM metadata, and network topology live elsewhere.
  • Not a monitoring tool. Albumi describes your architecture; it does not observe it. Runtime telemetry belongs in an observability stack.
  • Not a project portfolio management (PPM) tool. Initiatives scope the architectural impact of a change; they do not replace a full project tracker.
  • Not a code or service catalog for a single engineering team. The scope is cross-functional architecture across many teams.

Next

Section titled “Next”