How it works

Four steps, and you write code in exactly one of them.

A visual tool that makes you write code for the obvious parts has not saved you anything. So the obvious parts are drawn and clicked, and the language is there for the decisions that are actually yours.

1 · Draw the data

Tables on a canvas, relationships as lines you drag between them. Change a field later and Neuridion migrates the customer's database on the next update, matching by identity rather than by name — so a rename stays a rename.

2 · Let the assistant build the windows

Point it at a table and answer three questions: which fields, in what order, grouped how. Out comes an entry form and a list — with a coloured header, a working search box, New · Duplicate · Delete already wired, and a footer that counts.

3 · Adjust by clicking

Move things about, set the columns, choose a named style. The canvas and the running window are two drawings of one object, and a test counts them against each other — so what you see is what your customer sees.

4 · Write the rules

Only the part that is genuinely yours: what happens on save, what a button does, which invoice may not be changed. Plain JavaScript, in an editor that knows your schema and underlines a mistyped table name before you run it.

The schema canvas: tables as cards with their fields, joined by relationship lines — **1 · Draw the data**Tables are cards, relationships are lines you drag between them — and the drawing is the database, not a picture of one.

A generated list open in the designer, with its row-action bar and its events in the inspector — **2 · Let the assistant build the windows**What came out: a list with six columns and eight buttons, none of them written by hand — and every event it can fire named on the right.

The form designer with a contact sheet open, its fields showing their bindings — **3 · Adjust by clicking**Each field shows what it is bound to. Move things about, set the header, choose a style — the canvas and the running window are two drawings of one object.

The code editor's completion list, each command with a one-line explanation — **4 · Write the rules**The editor knows your schema, so a mistyped table name is underlined before you run. Each command explains itself in a line — and ⌥↩ opens the manual at exactly that one.

Why JavaScript, and why so little of it. A visual tool that claims “no code” either cannot express a real business rule, or hides one in a dialog with fourteen popup menus. Neuridion takes the other road: avoid code wherever a click is honestly better — and where it is not, use the one language nearly every developer already reads. No macro dialect, no formula grammar of our own, nothing to learn twice. The whole API is synchronous: invoice.customer is the customer, not a promise of one.

Carry on.

What's in it

Every part, and the ones nobody advertises.

Speed

Measured on this machine, through the ordinary API.

Data migration

Version 2 has three more fields. Your customer has a year of data.