Different tools for different jobs. Here is where Eraser is the better choice, and where isketch adds something it does not.
Where Eraser is better
Diagram-as-code across many syntaxes, with a polished editor and diagrams that look sharp in docs.
A whole suite around engineering docs: OpenAPI files, release notes, an AI to draft diagrams.
A company behind it, shipping fast.
Where isketch adds something different
isketch is a sketchpad whose output is agent-ready: the diagram is text a coding agent reads exactly, and can edit back.
Open and local: your diagrams are `.flow` files in your repo, not documents in a service. A CLI renders them with no browser, and no account is needed.
The MCP server works on your folder as it is, so the agent you already run edits the diagrams next to the code they describe.
Sketch when you want to think, structure when you want to build: one diagram, both surfaces.
Try both
Eraser is good at what it does, and you can bring your Eraser diagrams along: the converters run in your browser.