NodeGX

Where it started

A note in the code, and the editor it makes possible

Richard built Communauté Coiffure, an app for independent hairdressers in France, in plain code. He asked Claude to leave a note on every style setting saying how far it may go. The app has 70 of them.

What Claude writes

/* @tweak text-base: range 14px 20px */
--text-base: 16px;

What a client can be given

Body text 16px

14px20px

Your prices this month, and what each service earns you.

The note tells Claude the limits. When Claude later raised two of the app’s font sizes, it stayed inside them. The same note is all an editor needs to give a client a slider that can’t go wrong.

The rule

In NodeGX the list comes with the part

In our tests, AI assistants sometimes skipped instructions that were right in front of them. A note you ask for is a note that can be forgotten. So NodeGX doesn’t ask. Claude builds from a fixed set of parts. Each part already carries the list of what a person can change.

A part of a page

Today

What the Button node lists

Button
  label    text     "Book a cut"
  colour   choice   teal
  size     choice   medium
  rounded  on/off   on

The panel the editor builds from it

Label

Colour

Size

Rounded

Book a cut

Simplified from a real NodeGX node. Whatever part Claude used, its settings are there to open and change.

A 3D model

Spaceship
  paint      colour     steel
  length     20–60 m    40 m
  wingSpan   0–40 m     26 m
  engines    1–4        2
  stripe     on/off     on
  fins       on/off     on
  cannons    on/off     off
  thrusters  on/off     off
  parts: hull, cockpit, wing,
  engine, stripe, fin, cannon

Paint

Length 40 m Wing span 26 m Engines 2

Stripe Tail fins Cannons Thrusters on

The model, built from those settings

Drag to turn it. Click a part.

We’re taking the rule to 3D games written in plain code. A model lists its parts and settings. A 3D Studio turns them into controls. Nobody has to learn 3D modelling software.

Convinced?

Pick your way in

Each one opens the steps, in order, for where you are now.

New to building

I’ve never built an app

Describe your app to Claude, and NodeGX Studio opens right in the chat so you can watch it being built and change it.

See how it works · coming soon → Trying ideas

Build a website, app or game with your AI coder

You use Claude Code, Cline or Vibe and want to see what it can make. Add NodeGX to the project before your AI coder starts. It then builds with parts you can open and change.

Set up a project → For a business

Internal tools and apps for your customers

You need an app that people will rely on. Choose how you’ll change it: NodeGX Studio, the NodeGX editor, or an editor your AI coder builds for your team. Add the NodeGX backend for accounts, data and your own server.

Choose your setup → Coming from Bubble

Bring your Bubble app across

NodeGX Studio imports your app’s pages and back end. Studio works the way a Bubble builder expects. Your app runs on your own machine.

Import your app →

Three ways to touch your app

Every one of them opens the same folder. You choose how deep to go.

The part in the chat

one piece of the app, live, in the conversation

a decision while it builds

NodeGX Studio

an editor inside the chat, or in its own window on your computer

the day-to-day; changes you make yourself

The NodeGX editor

a free download for your computer

when you want to work at that level

Under all three: the files. Developers put them in git and open them in VS Code. If none of that means anything to you, ask your AI coder to build you an editor that suits your understanding of the app, so you are never shown a thing you can't understand.

NodeGX works inside the AI coder you already use. Claude Desktop is the first app that shows Studio and the parts to approve inside the chat, and that is where we build first.

Compare the three →

Not convinced yet?

See what’s been built with it

Demos

Eight working apps

A maths game, a planning tool, a marketplace and more, each running in your browser.

Your own editor

Editors Claude built from the packages

A 3D editor, a children’s block editor and a map of a backend, each built in under a day.

Backend map

Who can see whose data?

Pick one of a training app’s twelve people and see only the rows that come back to them.

Your first project

One brief, built three ways

Claude Code built a game on its own, on NodeGX, and on NodeGX with our guides. Play all three.

From code

A coded game, converted

A game written in plain JavaScript, rebuilt in NodeGX by Claude Code: what came across and what it cost.

Dive deep

Docs, code export and how it’s made

Docs

Node reference

What every node does, its settings and what it sends on.

Code export

Leave with React source

Two apps exported as React and as iPhone apps, then tested end to end.

The comparison

Claude Code on its own and with NodeGX

We built one brief both ways. The first versions look alike. What differs comes later.

Source

NodeGX on GitHub

It holds the code, the issues and every release. The tools are open source under GPL-3.0. The runtime your app runs on is MIT. The app itself is yours.

NodeGX is made by the Low Code Foundation and Richard Osborne. Read where it came from.

Community

Somewhere to ask, and somewhere to learn

You do not need an account to read any of these, and NodeGX works fully without one.

community.nodegx.io

Mailing list

Hear about important updates

An email when there is important news about NodeGX, or a release you should know about. Not every release, and nothing else.

Your AI builds the app. You can still change it without code.

Price list