Demos · running now

Every one of these runs in your browser

Each app below is a whole NodeGX project, published with the product’s own deploy. No account, no install. Open one and use it. Under each one: why we built it, then what building it taught us about NodeGX.

The Planning demo in dark: four hour budgets across the top — billable, building, admin and hobby, each with what is left in it — a strip of next moves by urgency, and six day columns of blocks from Monday to Saturday.
Freelance planning

Planning

A week for people who bill by the hour. It shows what the month has to earn, how many hours a day that is from here, and what is left for the work that pays later.

Why we built it

Richard bills by the hour. He wanted one screen on Monday morning that says where the month stands, without scrolling.

What it proved

A real backend app that handles money can be built through the agent’s door. The person who asked for it can read every rule in the graph.

Open the demo →
Rocket School's home screen for a player called Léa: skills to review today, days practised and stars earned, the stars she has left to spend in the hangar, then the games to pick from, starting with Rocket Race and Make Ten Merge.
Game · ages 8–12

Rocket School

Maths and typing practice in English and French. Make a player and race the computer to the planet. 62 skills from CE2 to 6e, with progress kept in your browser.

Why we built it

Richard’s children needed to practise maths and typing. The game is bilingual because they are at French school.

What it proved

Three play tests with children changed the game three times. Each change was built through the same door the agent uses, with the whole template regenerated and checked byte for byte.

Play the demo →
The todo list demo in dark: eight numbered tasks, one overdue, and the first — Write the release notes — open beside them with its deadline, three next actions, one done, and its history.
Productivity

Todo list

One list, in the order you will do things. Nothing is deleted. You close a task by writing what happened.

Why we built it

Richard hates task software. He wanted the simplest list that keeps a trace of every change.

What it proved

A template can carry its own backend and its own rules. Each person’s rows are private and nothing can be deleted. Those rules live in the project, not in a setting somewhere.

Open the demo →
A learner's course in Digital Bricks Training: a line of what they have done running ahead of the dashed pace line to the date they agreed with their coach, and four gauges of how it is going, each with the coach's goal marked.
Coaching · eLearning

Digital Bricks Training

A coached course where the learner’s own project is the curriculum. Look at one programme from both sides, the learner’s and the trainer’s.

Why we built it

The app is the training product Richard sells, rebuilt in NodeGX.

What it proved

Where a graph stops helping. This is the largest app we have built through the door. About a third of it is JavaScript inside script nodes. The editor now shows that number for every app.

Open the demo →
Pixel Dungeon, room one: three hearts, no coins yet, and a walled grid with coins to collect and a way out.
Game

Pixel dungeon

A turn-based dungeon played with the arrow keys. The five rooms are one list in one node. Add a sixth entry and it is in the game.

Why we built it

Richard asked for something that shows off the node graph and is not a website.

What it proved

Building the dungeon found two defects, both fixed since. NodeGX had no node that ticks on its own, which is why the game is turn-based. A default on the States node silently did nothing.

Play the demo →
The story engine on its first passage, The lamp-room, with three choices below it and an empty list of what you carry.
Interactive story

Story engine

A branching story where choices hand you things, and some choices only appear once you carry them. Paste your own story in and it plays straight away.

Why we built it

Richard’s question was: you can build anything with Claude Code today, but can you go in and edit it afterwards?

What it proved

We rebuilt the engine with a completely different story and compared every component. The two builds differed in one parameter of one node.

Read the demo →
A landing page for a design studio, Halden & Rowe: a navigation bar, a full-width workshop photograph and the headline We draw it, then we make it.
Static site

A business landing page

A landing page for a design studio: a header that follows you, links that scroll to their section, and no backend at all.

Why we built it

The first thing most people need is a page, not an app.

What it proved

A one-page site needs none of the backend. The template ships inside the editor, with three page types in it.

Open the demo →
A school stage in blocky 3D with a red curtain and a clock above it. Seven dancers in purple stand in a line with their arms out, two of them touching hands. On the right, the evening's running order, and below it what just went wrong: a move from the floor straight into a pirouette, and two dancers bumping hands.
In the works · best on a computer · French and English

Le Gala de danse

You run a dance school’s gala night. Plan the running order, the formations, the costumes and the snacks, then watch the evening play out. Nothing marks your answers. If the maths is wrong, you see it happen.

Why we built it

A maths game where the maths hides inside a dance school’s gala night: the timings, the spacing, the snacks.

What it is

Claude Code built it as a plain web page first, so it could be play-tested. It then converted the game to NodeGX: 54 components, 762 nodes, in one sitting. Both versions, and what the conversion cost, are on the From code page.

Open the game →
Three long grey warships seen from above in space, each with a deck of small node cards joined by green and blue wires, an explosion ring beside the middle one. A panel on the right lists the nodes of one component, and the todo list app runs in a window in the corner.
Your own editor

Orbit and the space map

Claude Code built Orbit and the space map from the NodeGX packages. Orbit lifts a timer’s nodes into 3D around the running app. The space map shows the todo list as a fleet of 80 ships.

See your own editor →
The backend map looked at as one learner, Marie Dubois. Pink wires run from her card through two functions to the tables her rows come from, and each lit table shows a pink bar and a count such as 4 of 33 rows. The other tables stay dark. A panel on the right reads 37 of 289 rows.
Prototype · best on a computer

Backend map

The map shows a training app’s screens, cloud functions and tables in one picture. Pick one of the app’s twelve people and only the rows that reach them light up. A new learner reaches 2 of its 289 rows. A member of staff reaches 261.

Why we built it

So someone who doesn’t write code can answer a client who asks who can see their data.

What it proved

Who can see what can be measured instead of guessed. The map ran every function each person may use with that person’s access. Then it counted the rows that came back. The people are test accounts.

Open the map →
Three phone screens of a marketplace called Market Square. The shop lists sellers in Nigeria, Ghana and Kenya. A basket holds a pepper sauce from Ghana and a drink from Nigeria, paid separately in cedis and naira. An order shows each seller's part waiting to be confirmed.
The Low Code Foundation

A community app and a marketplace

Two apps built free for a community group: a members’ app for a church, and a marketplace for small sellers in three countries.

See the Foundation →

Make it yours Every NodeGX app above is a template. Download NodeGX, open the launcher’s Templates tab and pick the one you just used. The whole app lands on your machine as a project, every node and wire of it, ready to change. The one exception is Digital Bricks Training: its template needs a backend of its own and is not on the shelf yet.

Download NodeGX