Experimental · Invite-only beta

The living map of your software.

Claude reads your code. Archadio turns it into a map of every service, endpoint, event and database — one you can zoom into, follow end to end, and trust in your next design review.

Request an invite See how it works

Design-time, not runtime: no agents, no traffic capture — just your architecture, as designed and as coded.

An example architecture map Two clients call an orders service and a catalog service. A design-time trace follows one request: the web shop calls POST /orders, orders calls payments, which calls an external card provider; orders writes to its database and publishes an order-placed event that shipping and notifications consume. clientweb-shop clientmobile-app serviceorders servicecatalog servicepayments eventorder-placed databaseorders-db databasecatalog-db indexsearch externalcard-provider serviceshipping servicenotifications
calleventone request, followed end to end

The problem

Your architecture is a rumour.

01

It lives in a few heads.

When they're on holiday, so is the knowledge. Everyone else pieces it together from code, chat and guesswork.

02

Diagrams lie by Friday.

Last quarter's whiteboard photo is already wrong — and nobody is sure which parts.

03

"What breaks if we change this?" takes a week.

Of chat threads, guesswork and code archaeology — before a single line of the change is written.

How it works

From code to clarity.

Four steps, and the map keeps itself up to date — because it comes from the code, not from memory.

  1. Scan

    Point Claude at a repository. It finds the services, endpoints, events, queues and databases, and drafts the map.

  2. Review

    Every proposal arrives as a change set: what's new, what changed, what's gone. You approve it — nothing lands behind your back.

  3. Explore

    Zoom from the whole landscape to a domain, a service, a single endpoint — and follow a request across every call, event and database it touches.

  4. Share

    Diagrams and traces that stay true, because they're drawn from the map, not by hand.

Claude connector

Let Claude do the cartography.

Documenting a system used to mean weeks of interviews and diagrams nobody updated. Archadio's Claude connector reads your code where it already lives — in Claude Code or on claude.ai — and proposes the map. You stay the editor: review the plan, settle conflicts, apply. After a big change, re-scan just that part and only the difference comes back.

  • Works where you already use Claude. Claude Code in your terminal, or claude.ai in the browser.
  • Targeted re-scans. One service, one concern, one fix — without disturbing the rest of the map.
  • Nothing changes without your review. Additions, changes, conflicts and removals are all in the plan first.

Illustration

What you get

Everything that moves, on one map.

Blast radius, before you ship

Pick any endpoint and follow it downstream through calls, events and data stores. See what a change touches before it touches production.

Contracts, not guesses

Methods, paths, parameters, schemas and security for every operation. Import OpenAPI or let Claude declare them.

Events you can follow

Channels, messages, who publishes and who listens — async flows stop being invisible.

Data stores in the picture

Databases, queues, caches and external systems, and exactly who reads and writes them.

Diagrams that stay true

Build your own views from the map, with automatic layouts and labelled lines. When the map changes, they follow.

Boundaries built in

Nested domains, team access by namespace, a separate workspace per organisation, and a full export whenever you want it.

Made for the moments that matter

  • Design reviews
  • Impact analysis
  • Onboarding a new engineer
  • Migrations and modernisation
  • Audits and due diligence

Beta

Be early. Shape what's next.

Archadio is an experimental project in an invite-only beta. Tell us a little about your system and we'll send you an invitation — and we'd love to hear what you think.

  • A workspace for your organisation, with your team invited.
  • The Claude connector, ready to scan your first repository.
  • A direct line to the people building it.

Questions

Good questions.

Is this runtime tracing or APM?

No. Archadio maps your architecture as designed and as written in code: no agents, no traffic capture. A trace in Archadio follows the map, not live requests.

Does my source code leave my machine?

Claude reads your code in your own Claude session. Archadio receives the architecture it describes — services, endpoints, schemas, links — not your source files.

Do I have to use Claude?

No. You can model by hand or import OpenAPI; Claude just makes it fast.

Can I take my data with me?

Yes, export a whole workspace any time.

What does "experimental" mean?

Archadio is a young, independent project. Expect rough edges and quick changes; your feedback shapes what comes next.