Eraser is an AI diagramming tool for technical teams: it generates architecture, sequence, flow, ERD and BPMN diagrams from prompts, images, files and code, stores them as diagram-as-code, and offers an MCP server and agent skills. CoPage is a workspace where AI agents build diagrams and decks and people review, check and sign off; its free CLI keeps diagrams in your repo, on your computer.
At a glance
| CoPage | Eraser | |
|---|---|---|
| What it is | A workspace where agents build diagrams and decks and people review and sign off, plus a free local CLI for diagrams | An AI diagram tool with diagram-as-code, a visual editor and AI documents |
| Made for | Consulting, pre-sales and architecture teams; developers who keep diagrams in a repo | Software engineers, DevOps, enterprise architects and technology consultants |
| AI agents and MCP | Works with the agents you already use: Claude Code, Codex, Cursor and GitHub Copilot through the CLI or a local MCP server; Claude, ChatGPT and other MCP clients connect to the app. No AI of its own does the work | Its own AI generates diagrams from a prompt, an image or a file (Terraform, database schemas), from Git repositories and from cloud accounts. MCP server and Agent Skills for Claude, Claude Code, ChatGPT, Cursor, Codex, VS Code, GitHub Copilot and others; generations use Eraser AI credits |
| Editing agent work in place | The agent changes the same diagram in small, atomic edits, sees what people changed since its last edit and builds on it. One agent edits at a time, and a person can stop it | The MCP server's update_diagram edits a diagram from an instruction; diagram-as-code can be diffed and edited as text; Eraserbot updates codebase diagrams in CI |
| Review and sign-off | Comments for people or for your own agent, which makes the change and replies; history of who changed what, a person or an agent; versions from the last 30 days restored, ones marked with a status kept for good | Comments and tagging, real-time collaboration; version history from 7 days (Free) to unlimited (Business) |
| Checks before the client | Built-in checks the agent runs and fixes: arrows attached, icons labelled, nothing stacked, no placeholders; decks add packs such as Client-ready | Rules and presets the AI follows while it generates; a check report after the fact: not documented |
| Official cloud icons | 3,000+ icons, offline: AWS, Azure, Google Cloud and general | 3,000+ tech icons, including AWS, GCP, Azure and Kubernetes; custom icons on paid plans |
| Decks and PowerPoint | Diagrams sit on slides and stay linked: fix one, and every slide that shows it updates. Native PowerPoint and PDF export of whole decks | One selected diagram exports as a single PowerPoint or Google Slides slide; Eraser says neither builds a multi-slide deck. Also PNG, SVG, PDF, BPMN, Visio and draw.io |
| Local and offline | The free CLI keeps diagrams in .copage/ in your project, with no account; nothing is sent to us |
— (Enterprise lists "flexible deployments") |
| Pricing as published | CLI free; the app is in early access, by request; private deployments as pilots | Free (3 files, 3 AI diagrams), Starter $15 and Business $45 per member per month billed annually, Enterprise custom |
When to choose Eraser
- You like diagrams as code: text you can read, diff and review in a pull request, with layout handled for you.
- You want diagrams generated from what already exists: a repository, Terraform, a database schema, or AWS, Azure and Google Cloud accounts, kept current by Eraserbot in CI.
- Design docs and diagrams belong together, with Notion, Confluence, GitHub and VS Code integrations.
- You want generation itself to follow your team's conventions through presets, rules, templates and references.
When to choose CoPage
- You want people to review the agent's work, not just receive it: comment on an area, the agent changes it, runs the checks and replies, and your hand edits stay.
- You want the agent to catch its own mistakes before you look:
copage diagram checkflags loose arrows, unlabelled icons and stacked shapes, and the agent fixes them in a loop. - The architecture goes into a client proposal: in the CoPage app, architecture and BPMN process diagrams sit on slides in your brand and stay linked, and the whole deck exports to native PowerPoint.
- Diagrams must stay on your computer: the CoPage CLI needs no account, has no AI of its own and sends nothing to us. The SVG or PNG it exports carries the diagram inside, so it opens for editing again.
Using them together
Both read and write draw.io files. Eraser imports .drawio onto its canvas and exports a selected diagram as
.drawio; CoPage does the same with copage diagram import and copage diagram export. A diagram can move
between them that way; expect to check icons and layout after each move.
Compared on 2026-10-05 from public documentation; tell us at hello@copage.app if something changed.
Questions
Is CoPage an alternative to Eraser?
For architecture diagrams your coding agent draws and keeps up to date in the repo, yes, and the CoPage CLI is free and local. If you want diagram-as-code with layout done for you, or diagrams generated from cloud accounts, Eraser does that and CoPage doesn't.
Can I move my Eraser diagrams to CoPage?
Through draw.io files: export the diagram from Eraser as .drawio, then run copage diagram import file.drawio.
Cloud shapes are matched to CoPage icons by name; shapes with no match are kept as images and listed.
Does CoPage have diagram-as-code?
Not as a text language. A CoPage diagram is a JSON document the agent edits with small, checked operations, and
it places the boxes itself. You can commit the files in .copage/ and review them in a pull request, and fix the
layout by dragging in the editor.
Which one works without sending diagrams to a server?
The CoPage CLI: diagrams, icons, fonts and checks are on your computer. Your coding agent still sends what it reads to its AI provider, as it does with your code.