Skip to content

Your architecture, navigated

The living documentation for ArcaMira — catalogue what you have, map it to what the business does, and see what's at risk. Start with a spreadsheet and an hour, not a six‑month framework programme.

Get started Tour the features

Find your path

  •  Product reference

    What ArcaMira is, its data model, and a tour of every feature area — the place to build a mental model of the product.

    Overview · Core concepts · Feature map

  •  Playbooks

    Outcome‑first recipes. Each starts from a real situation — a deadline, a question from a boss — and walks the shortest path to a finished deliverable.

    All playbooks

  •  The EA function

    One guide per architecture discipline: the problem it solves, how ArcaMira addresses it, and what "good" looks like in practice.

    How the disciplines fit

  •  Help guides

    Task‑oriented, step‑by‑step instructions for the everyday jobs — importing, cataloguing, sharing, reviewing.

    All guides

  •  Get your sunset‑risk list

    Surface the technology heading for end‑of‑life before it becomes an incident.

    Open playbook

  •  Discover your SaaS

    Scan your domain or connect Microsoft Entra to find the applications you're already running.

    Discovery & connecting

  •  What breaks if I retire this?

    Trace the blast radius of a change before you commit to it.

    Open playbook

Conventions used in these docs

  • Bold marks UI elements you click (buttons, menu items, page names).
  • code marks routes (e.g. /applications), field keys, and literal values.
  • Roles are referenced as viewer, editor, admin — see Core concepts.
  • "The estate" means everything catalogued in your repository.

A note on philosophy

ArcaMira is deliberately calibrated for the mid‑market, not for heavyweight framework ceremony. The guiding rule throughout the product: a feature should tell you something true about your organisation that nothing else could — not just teach you a framework's vocabulary. You'll see this reflected in how features are scoped and where the tool deliberately stops short. See the Overview for more.