We're excited to introduce Canopy, the architecture canvas built for developers. Canopy turns your stack into a living architecture map: every service, what it costs, and who owns it, in one picture you can actually trust, and that your AI agents can finally read.

Why we built Canopy

Every team has the same broken ritual. Someone draws an architecture diagram. It's beautiful for about a week. Then the system changes, the diagram doesn't, and within a month you're making decisions off a picture that's quietly wrong.

The root cause isn't laziness. It's the format. A diagram is a drawing: a thing a human has to remember to update by hand, forever. You can't diff it, you can't query it, and no machine can read it.

Canopy fixes this by changing the format. Every map in Canopy is structured data you own, not a drawing. That one shift is what makes everything else possible: cost roll-ups, dependency queries, and exports your coding agents can consume.

What Canopy does

Canopy is organized around four verbs: Capture. Visualize. Operate. Share.

Every map is structured data you own, exported to CLAUDE.md, AGENTS.md and MCP.

Capture: get a map in minutes, not hours

You don't start from a blank canvas unless you want to. Canopy can populate a map from:

• A GitHub repo: install the Canopy GitHub App and it detects services from your package.json, lockfile, and infra files.
• An integration catalog: search 200+ services and hand-pick your stack.
• A template: start from a real, editable community map.
• A canopy.json file: paste a structured map and go.
• Canopy AI: describe your system in plain English and get a draft map.

Visualize: a picture that stays true

Because the map is data, the diagram is just one view of it. Canopy gives you interactive React Flow maps, workspace topology, and cost-domain views, and when the data changes, the picture changes with it. No more stale drawings.

Operate: architecture that knows what it costs

This is where a Canopy map stops being a diagram and becomes an operational tool. Attach spend to each service and Canopy rolls it up per map and across your workspace. Add ownership, environments, and operational metadata. Your architecture diagram just became a FinOps and on-call reference at the same time.

Share: publish, or sell

Make a map public, share a private link, or list it as a paid template in the marketplace with Stripe Connect payouts. Verified workspaces get a seal and provenance-stamped clones.

The part we care about most: your agents get the map

Here's the feature that changes how it feels to work day to day. Your AI coding agents (Claude, Cursor, whatever you run) currently reconstruct your architecture from scratch every session, one file at a time, and they get it wrong in exactly the places a senior engineer wouldn't.

Canopy closes that gap. Because your map is structured data, Canopy can:

• Export CLAUDE.md and AGENTS.md so your agents get the architecture as standing context.
• Serve a read-only MCP server with tools like get_architecture, list_services, get_spend, and find_dependencies, so agents can query the live map on demand.

One source of truth, delivered to your team and your tools.

Getting started

The Free plan is enough to draw your first living map:

1. Sign up at canopy.8starlabs.com.
2. Create a map: import a repo, pick integrations, or start from a template.
3. Draw the connections and attach spend and ownership.
4. Export a CLAUDE.md for your agents, or share a public link.

Read the quickstart to go from zero to a living map in about two minutes.

This is just the start

On the roadmap: live metadata sync, deeper AI architecture analysis, cost-optimization recommendations, graph querying, and agent-native payments. Canopy is part of a bigger belief at 8StarLabs: that developer tools should be built for both the humans and the agents now working side by side.

If your architecture deserves to be more than a stale drawing, come map it.

Try Canopy free. And if you build interfaces, check out our open-source component library, 8StarLabs UI, too.