Eraser

Eraser is an AI tool for creating technical diagrams that matter, such as cloud architecture diagrams, business process flows and system designs. It turns text, code or files into clean, laid-out diagrams in seconds. Eraser says it has more than 5,000 customers among architecture and process teams. A customer solutions architect at Braintrust says Eraser will remain an important part of how his team communicates complex architecture to customers.

Inputs

You can paste a prompt, drop in Terraform, or upload a design document, and Eraser produces a diagram. Uploads include images in PNG, JPEG or WebP, and files such as PDF, Word, Excel, PowerPoint, Draw.io and Visio. You can also reference private or public Git repositories, so diagrams reflect your actual code. The site shows prompts such as a BPMN diagram for an insurance claims adjustment process, starting with a customer reporting a loss and the intake team recording the claim, and a GCP architecture deployment diagram.

Consistent output

AI presets help produce particular kinds of diagrams, and custom styles let you apply a team style preset so every diagram follows the same look. Eraser focuses on pixel-perfect output that is ready to share in documentation, presentations and customer conversations.

Editing

The editor's Add Reference menu brings in files, images and Git repositories as context, and Insert Item adds elements, so one diagram can draw on several sources such as a design document plus the code it describes.

Pricing

You can try Eraser free, and a demo can be booked for teams. Check the official pricing page for current plans, limits and any free trial, as prices and included usage can change.

Who it suits

Eraser suits software architects, engineers, solutions architects, DevOps teams and process or operations teams who need clear diagrams without drawing every box by hand.

Things to consider

Check generated diagrams against reality, since AI can misread code or documents and omit components. Be careful about which private repositories and documents you connect. Keep diagrams updated as systems change, so they remain a reliable reference rather than an outdated picture.

For teams, a shared style preset and a habit of generating diagrams from the latest code or Terraform can keep architecture documentation consistent, which helps onboarding and customer conversations.