Skip to content

What Canopy Is and Isn't

Canopy is the self-hosted code intelligence platform that makes your AI coding agent dramatically smarter — no cloud, no credits, one binary.

That sentence has a lot of words chosen carefully. Let’s unpack them.

Canopy does not include an AI model and does not generate code. It is a context engine — software that transforms a raw code repository into a structured, queryable graph of symbols, dependencies, health findings, and history that an AI agent can interrogate precisely.

The AI agent (Claude Code, Cursor, Codex CLI, etc.) supplies the intelligence. Canopy supplies the facts about your specific codebase. Together they produce dramatically better results than either can alone.

Think of it this way: an AI agent without Canopy is a very smart developer who has never seen your codebase. With Canopy, that same developer has a complete architectural map, annotated with which files are risky to touch, which exports are dead weight, and which modules have been thrashed by recent commits.

Canopy runs entirely on your machine. The binary indexes your repo into a local SQLite database. The MCP server that answers tool calls runs on your laptop or CI server — not on Ironpine Labs infrastructure, not in any cloud.

Your code never leaves your machine. The only outbound connection Canopy makes is a weekly license health check that sends a hash of your license key, your Canopy version, and your platform. No code. No queries. No file paths. See License and Privacy for the exact payload.

No Docker. No daemon to manage. No service mesh. One static binary that you put on your PATH. canopy serve . starts the MCP server. canopy index . builds or updates the index. canopy health runs checks. Everything else follows.

Canopy exposes its intelligence through the Model Context Protocol (MCP). Any MCP-compatible AI client (Claude Code, Cursor, Windsurf, Zed, Continue, and others) can connect and use all 21 tools. The tools are organized into three tiers: three workflow composites that cover 80% of use cases, and 18 detailed tools for deep analysis. See Tool Catalog for the full list.

Canopy does not write code, explain concepts, or answer questions about programming in general. It answers structural questions about your specific codebase: “Who imports this file?” “What exports are unused?” “Which files have changed most in the last 30 days?” “Is this module reachable from any entry point?”

Canopy is not a replacement for ESLint, Clippy, mypy, or similar tools. Those tools enforce code style and language-specific rules. Canopy operates at the architectural level: dependency edges, module reachability, dead code at the module boundary, secrets in source files. The two complement each other.

Canopy does not have a cloud pricing tier. There is no “Canopy Cloud” or “Canopy SaaS.” The product is a binary you download and run. If you need zero network calls (defense, healthcare, classified environments), the Air-Gapped tier compiles out all networking at build time. See License and Privacy.

Canopy’s current tiers (Solo, Pro, Team) target individual developers and small teams of 3–10. There is no SSO, audit logging, or SLA. Enterprise teams with those requirements should contact [email protected] for custom contracts.

CanopyAugment CodeSourcegraph Cody
Where it runsYour machineCloudEnterprise self-hosted
Code leaves your machine?NeverYesDepends on config
Pricing modelOne binary, per-seat annualCredit-basedEnterprise only (free/pro discontinued)
AI model includedNoYesYes
MCP serverYes (21 tools)PartialPartial
Air-gapped optionYesNoYes (enterprise)

Canopy has real limits worth knowing:

  • Five languages only (v1.4.0): TypeScript, JavaScript, Python, Rust, Go. Other languages are indexed for text search but not AST-parsed. More languages are on the roadmap.
  • First index takes time: A 50K-file repo takes 5–15 minutes for a full index with search and git history. Incremental updates after the first run are fast.
  • Weekly heartbeat exists: Canopy makes one outbound network call per week for license validation. It’s minimal (hash + version + platform), but it exists. If you need zero network calls, the Air-Gapped tier is the answer.
  • Not a linter: Canopy finds dead exports and broken imports, but it won’t catch type errors, style violations, or logic bugs. Keep running your existing analysis tools alongside Canopy.