Introducing Nodlume

Design the plan, then export the project

Nodlume is a visual planning workspace for React applications. You lay out pages, components, layouts, shared stores, API routes, and data models on a canvas, connect them to describe how they relate, and export a conventional React project from that plan.

The idea is simple: the shape of an application is easier to reason about as a graph than as a folder of files. Nodlume keeps that graph as the source of truth and treats the file tree as an adapter, so the structure you design and the skeleton you ship never drift apart.

More than boxes and arrows

A file tree records where code lives; it says nothing about why. The canvas carries the decisions around the structure too. Data models live on their own nodes and flow into the types your components and routes reference. Roles and an access matrix declare who can reach what, and the export honors them — guarded pages check the session, API routes answer with a 403 instead of a redirect. A generated project report ties every feature back to the nodes that implement it, so "what does this app actually do" has an answer you can send to someone.

When you want feedback, share a read-only link. Links can carry an expiry date or a passcode, and both stay editable after you have sent the URL. When you want more than feedback, invite collaborators and edit the same canvas together, live.

What it costs

The designer itself is not metered. Every canvas allows unlimited nodes on every plan, skeleton export and report generation are included everywhere, and collaboration time is never counted.

The one metered resource is AI. Generating implementations and chat-assisted edits draw from a monthly credit allowance that every plan includes — most actions cost a single credit. Paid plans raise the allowance, lift the document limit, add version history and shared documents, and let you top up with one-time credit packs. The pricing page has the current numbers.

Built to be understood

Nodlume does not try to hide the code or replace engineering judgment. Generated projects follow ordinary React conventions, every generated file keeps a reference back to the canvas node that produced it, and the export is yours to take anywhere.

We are just getting started. Create a project, sketch an application, and export it — we would love to hear what you build.