Map a system

Your system already carries its architecture. Let ProvenMap model it.

Software architecture visualization and intelligence, derived from the system itself: ProvenMap builds the living map, then lets anyone on your team ask it questions. Install one plugin, run four commands, and your first board is live.

No credit card · Upgrade when your team grows

Opening frame of the ProvenMap film

The short version · under two minutes

The first ten minutes

Four commands to your first board.

Install the plugin in Claude Code, Codex, or Cursor, open one repository, and run it. No migration, no rollout, no diagramming.

1 · Install

/plugin marketplace add provenmap/pmap-claude
/plugin install pmap-code@provenmap

Restart Claude Code so the commands load. Same marketplace for Claude Cowork.

2 · Run, in order

  1. /loginSign in through the browser and bind this repository to a board.
  2. /analyze-archetypesSettle which kinds of component this codebase has. Required before /analyze.
  3. /analyzeRead the codebase and build the layered map. Incremental afterwards.
  4. /syncPush the result to your board.

Lost? /start reads the repository’s state and tells you the one command to run next.

See it working

The product, unedited.

  • Map · 1:08

    Connect a board to the code plugin

    One system, one repository, mapped and synced to a board.

  • Discover · 0:51

    What your mapped board can already tell you

    /discover finds the insights and context boards worth showing.

  • Ask · 0:52

    Ask ProvenMap, get a context board

    A board drawn to answer one question, ready to share.

What leaves your machine

Your repository is never uploaded.

The plugin reads it in your session and sends only the derived description of your architecture, only when a command runs: one you type, or one on a schedule you set.

  • Component names and descriptions, each capped at about 500 characters
  • File paths and line ranges
  • Short source-code excerpts, each capped at about 500 characters
  • Passages /ground quotes from your repository's documents as evidence, each capped at about 500 characters
  • Findings /monitor draws from your production signals, pushed as insights
  • Your repository's git remote URL, branch, and current commit
  • The project name
  • A one-sentence summary of a sync, when your agent writes one
  • Which agent pushed (Claude Code, Codex or Cursor) and a one-way hash of the machine
  • Each scheduled run's outcome, branch and commits, up to five file paths with uncommitted changes, and, when it stops, the error line, capped at 1,000 characters

Credentials stay in a project-local file. Security details · Privacy policy

Start free

Map your architecture. Then ask it anything.

Map your first system on the Free plan. Connect the sources behind your system, get living boards, and give your whole team answers — without the diagramming and without the wait.

1 contributor · 5 boards · 2 connected sources · 5 published boards · 300 work items · 25 insights · 10 free Chat messages

No credit card · Upgrade when your team grows

© 2026 Syntaxia App Platform Ltd.

Syntaxia App Platform Ltd. Registered in England and Wales, company no. 15272701 Registered office: 3rd Floor, 86–90 Paul Street, London EC2A 4NE, United Kingdom contact@provenmap.com