Enterprise Architecture Workspace

Enterprise architecture that lives beyond the diagram.

M10A/EA gives enterprise architects and architecture teams one connected workspace to maintain a shared repository and architecture model, then turn the same knowledge into reusable views and reports. Authorized agents can work from that governed model when you grant access.

Free during alpha No credit card required

Product preview

See the repository become a working view.

Built from the current seeded model and implemented M10A/EA interface patterns.
Illustrative product preview. Based on the implemented workspace UI and the seeded Discovery Capability Focus view.

Connected architecture knowledge

Model once. Use the knowledge everywhere.

Keep applications, capabilities, data, processes, and the relationships between them as reusable repository records. Views and reports use those same records, so every audience works from connected knowledge.

Architecture knowledge gets fragmented across

  • Diagrams
  • Spreadsheets
  • Presentations
  • Wiki pages
  • Modeling tools

One connected repository

Views and reports are different representations of the same named objects and relationships.

  1. 01

    Shared architecture repository

    Search, filter, and maintain architecture objects with structured fields, modeled states, and navigable relationships.

  2. 02

    Repository-backed views

    Compose stakeholder views from existing objects, or use query-driven NodeSets to select, relate, sort, and lay them out.

  3. 03

    Reports from the same model

    Build saved, sectioned reports with repository queries, relationship-based nesting, sort rules, and configurable fields.

  4. 04

    Your architecture language

    Configure entity and relationship types, State models, fields, icons, and colors—starting from an ArchiMate-oriented default.

One connected model

From architecture language to useful outcomes.

Define what your team can model, capture the organization’s knowledge once, and shape it into the representation each audience needs.

01 · Define Ontology

What can be modeled

02 · Maintain Repository

Your organization’s architecture knowledge

03a · Visualize Views

For stakeholder perspectives

03b · Structure Reports

For organized information needs

Fit the work

Represent the architecture work your team already does.

These are examples the configurable model can represent—not separate, hardcoded product modules.

  • 01Strategy
  • 02Value chains
  • 03Capability landscapes
  • 04Application landscapes
  • 05Business platforms
  • 06AI agents
  • 07Data products
  • 08Domain models
  • 09Solution designs
  • 10Architecture reports

Authorized agent access · MCP

Let trusted agents work from the model you govern.

Connect compatible AI agents and MCP clients to the same ontology and repository your team maintains—without creating a second, disconnected source of architecture knowledge.

  1. Understand your modeling language

    Understand the organization’s modeling language by reading its entity, relationship, State model, and field definitions before acting.

  2. Inspect connected knowledge

    Search repository objects, inspect full records, and follow bounded relationships without broad data dumps.

  3. Create validated changes

    Create or update repository objects and relationships through the same ontology rules and revision checks as the product.

Design Partner Program

Help shape what M10A/EA becomes.

Bring a real architecture challenge into a free, collaborative 90-day evaluation and work directly with the product team.

Explore the Design Partner Program

Free during alpha

Start the architecture repository your team can grow with.

M10A/EA is free while we develop it with alpha users. Create your organization workspace and start connecting the model, views, and reports your team already needs.