Can Nodlume draw a cloud architecture diagram?

No. Nodlume models the inside of one React application — its pages, data, routes, and roles. It does not depict infrastructure, message queues, or services written in other languages. Eraser is built for that.

Does Eraser generate application code?

Eraser produces diagrams and documents, and can generate diagrams from prompts or from a code-like syntax. It does not scaffold an application. Nodlume's Export tab produces the file tree, a build order, and starter code for the defined project.

Yes. A common split is Eraser for the system-level architecture doc and Nodlume for the definition of the React application inside it. Nodlume's ER designer exports Mermaid, which can be pasted into a design doc.

All comparisons

Diagrams and docs vs. system design

Nodlume vs Eraser: Diagrams vs a Buildable App Definition

Both products sit at the design stage of software work, before code exists. They answer different questions. Eraser records how a system is shaped, for any language or infrastructure. Nodlume records what one React application consists of, in enough detail to generate its files.

What Eraser does

Eraser is a docs-and-diagrams tool for engineering teams. It draws cloud architecture, entity-relationship, sequence, and flow diagrams from a diagram-as-code syntax or from an AI prompt, keeps design documents beside those diagrams, and syncs them with a repository. It is stack-agnostic: a Go service on Kubernetes and a Rails monolith are equally at home.

What Nodlume does

Nodlume is a system-design workspace for a React application. A project targets one platform — a Next.js site, a Tauri desktop app, an Expo mobile app, an Ink terminal app, or a Manifest V3 browser extension — and defines its pages, components, layouts, data model, API routes, stores, roles, features, and theme in connected tabs. The Export tab turns that definition into a scaffold in build order, an AGENTS.md, generated starter code, a project report, and a GitHub push.

Nodlume is narrower and deeper. It assumes the thing being designed is a React application with one platform target, and uses that assumption to connect the parts: a page knows its layout and guard, an API route knows its data model, a feature knows which pages implement it. Because the definition is structured rather than drawn, it exports a scaffold, a build order, and a report.

Capability by capability

Capability	Nodlume	Eraser
What a project describes	One React app: pages, components, layouts, data model, API routes, stores, roles, features, theme.	Any system: services, infrastructure, data flows, sequences, plus the design docs around them.
Platform scope	One target per project — Next.js, Tauri, Expo, Ink, or a browser extension — and the export follows it.	No platform model; a diagram can depict any stack.
Data modeling	Entities with typed fields, keys, and relations; a free ER designer with Mermaid export.	ER diagrams from diagram-as-code or AI, rendered and versioned.
Authoring method	Structured tabs and forms; the canvas is one of the views.	Diagram-as-code text, drag-and-drop, or an AI prompt.
Code output	Scaffold in build order, AGENTS.md, generated starter code per file, GitHub push.	None; diagrams and documents are the deliverable, synced to the repo as assets.
Requirements traceability	Features map to the pages and routes that implement them; a traceability matrix and report.	Handled in prose within design docs.
Access control design	Roles and an RBAC matrix per surface; guards are emitted in the scaffold.	Not modeled; describe it in the doc.
Collaboration	Live multi-editor documents, share links with optional passcode and expiry.	Team workspaces with shared docs and diagrams.
Free tier	Three documents and a monthly AI credit allowance; the standalone tools need no account.	A free plan exists; see the vendor for current limits.

Eraser details reflect the vendor's public documentation as of September 2026. Confirm current features and plans with the vendor.

Choose Eraser when

Your architecture spans several services, languages, or cloud providers.
The deliverable is a design document with diagrams reviewers can read.
You want diagrams kept as text in the repository next to the code.
The team already writes design docs and needs a home for them.

Choose Nodlume when

The thing being designed is one React application.
You want the definition to produce the project's files, not only a picture of them.
Features, roles, and routes need to stay connected so the plan can be checked for gaps.
The target platform (web, desktop, mobile, terminal, extension) changes what gets built.

Common questions

Can Nodlume draw a cloud architecture diagram?: No. Nodlume models the inside of one React application — its pages, data, routes, and roles. It does not depict infrastructure, message queues, or services written in other languages. Eraser is built for that.
Does Eraser generate application code?: Eraser produces diagrams and documents, and can generate diagrams from prompts or from a code-like syntax. It does not scaffold an application. Nodlume's Export tab produces the file tree, a build order, and starter code for the defined project.
Can I use both?: Yes. A common split is Eraser for the system-level architecture doc and Nodlume for the definition of the React application inside it. Nodlume's ER designer exports Mermaid, which can be pasted into a design doc.

Other comparisons

Define the application and see what it exports.

The free plan includes three documents. The standalone tools need no account.

Start planning free