Furio Sign in Try it
Open source · MIT

Furio likes things tidy.

Your architecture map, kept in your repos and checked like code. Every repo describes what it owns; Furio checks it on every pull request and draws the map of all of them.

Try it in your repo
See the live demo →
The real map of the three repos of the furio-demo workspace. Hover a card to light what it touches.

How it works

  1. 1

    Each repo describes what it owns

    A small YAML file next to the code: the services, functions, queues and databases this repo owns, and what they call, publish, consume, read or write. Parts owned by other repos are referenced by id, never copied.

    # .architecture/architecture.yaml
    version: 1
    project: shop
    owner: team-shop
    
    components:
      - id: shop-api
        type: service
      - id: orders-events
        type: queue
        provider: aws.sqs
    
    relations:
      - from: shop-api
        to: orders-events
        type: publishes
      - from: shop-api
        to: platform/users-api
        type: calls
  2. 2

    Every pull request is checked

    The GitHub Action validates the manifest like code: a wrong type, an unknown field or a reference to a service that does not exist shows up on the diff, with the line and the fix.

  3. 3

    The catalog draws the map

    One repo in your organization collects every manifest each hour and publishes the map as a static site: every project, every dependency between teams, the parts other repos reference but nobody declares. No server, no database.

    Open the live demo to see the map of the three repos above.

Ask it what breaks

Relations are data, so the map can answer questions a drawing cannot. Select a part and light its blast radius: everything that stops working if it goes down, hop by hop. Or light everything it needs to work. Every view is a link you can paste in an incident channel.

#/?sel=platform/users-api&mode=impact

  • Workspace and project views with the dependencies between teams.
  • A page per component: owner, repo, links, every relation, its diagrams.
  • Mermaid diagrams from the repos, for the flows a graph cannot show.
  • A health page: repos without a manifest, missing owners, broken references.
  • Search, filters, PNG and SVG export.
Blast radius of platform/users-api: if it goes down, shop-api and storefront stop working.

Your coding agent keeps it updated

A map is only as good as its last update. Furio ships a skill that tells Claude Code, Codex and any agent that reads AGENTS.md to update the manifest in the same change as the code, and to run the check before it finishes.

Free to run yourself. Hosted if you'd rather not.

Furio is open source: the CLI, the GitHub Action and the map are free, for any repo, forever. Furio Cloud hosts the map for you at getfurio.com/w/<name>, with no catalog repo to run. On Cloud, Free is for open source: public repos, public map. A paid plan makes the map private and accepts private repos.

Open source

0 €self-hosted

MIT license

  • Any repo, public or private
  • A catalog repo in your organization builds the map every hour
  • Publish it where you choose: GitHub Pages or any static host
  • Who can see it is up to your host
Set it up

Cloud Free

0 €forever

For open source projects

  • Public GitHub repos only
  • Public map: anyone with the link can view it
  • Unlimited repos and members
  • Repos upload from the Action; no catalog repo
Start free

Business

49 €per month

or 490 € a year · per workspace, VAT excluded

  • Public and private repos
  • Private map for the whole team
  • Unlimited repos and members
  • Invoiced to your company, with its VAT number
Start 7-day trial

A workspace's first paid plan starts with a 7-day free trial; cancel any time before it ends and nothing is charged. Payments, VAT and receipts by Stripe. A workspace is one GitHub account's repos on one map. See the terms and the refund policy.

Try it in your repo

  1. In a repo, create the manifest and teach your agent about it:
    npx @getfurio/cli init
  2. Describe what the repo owns, then check it:
    npx @getfurio/cli validate
  3. Add the check to pull requests and publish the map of your organization: Set up the GitHub Action

Open source under the MIT license. Node 22 or newer. Works with any GitHub organization.