Skip to content
NRPS ndexr Rapid Prototyping System

Ask → live. Same moment.

Say it in plain language. An agent edits the module, the deploy rolls, your users see it. This page is one of them.

Start here

The whole system, in a few minutes

The fastest way to understand what this is. Present it, hand it over, or read it offline - the PowerPoint, PDF and Word downloads are the same document, not separate drafts.

Open full screen PowerPoint PDF Word Download all (zip)

Use the arrow keys inside the deck to advance. Rendered from one Quarto source — the same file produces the PowerPoint, PDF and Word downloads above.

What this replaces

The handoff is over

Describe it, watch it change, keep going. No ticket, no estimate, no waiting days to see whether anyone understood you.

01

From anywhere

The whole business, from a phone

These systems are run and changed from a phone. Not a dashboard that reports on the work - the actual controls, wherever you are.

02

In the room

Changed while the customer watches

The change lands in front of the person who asked for it, in the same conversation. They see it, react to it, and that reaction is the next change.

03

Without the trade

Speed that gives up no control

Every one of those changes is a commit on a pinned, rebuildable foundation. Immediate at the edge, centrally controlled underneath.

The idea

Instant on top, immutable underneath

Speed normally costs you provenance, and provenance normally costs you speed. It only reads as a trade-off while you assume a change means overwriting something. Nothing here is ever overwritten.

THE SURFACE The live interface always serving the newest version it changes while you are looking at it one atomic swap a pointer moves — nothing is rebuilt THE RECORD · APPEND ONLY v1 still boots v2 still boots v3 still boots v4 still boots v5 live now v6 your next ask nothing here is ever edited or deleted instant at the surface because permanent underneath
A change appends a new version and moves one pointer. That is the whole mechanism, and it is why both halves hold at once: the swap is immediate because there is nothing to rebuild, and it is safe because every earlier version is untouched and still boots. Going back is the same one-step move as going forward - which is what makes it reasonable to change a live site while someone is watching it.

Every one of them is the same running Shiny application — one app, one deploy, one thing to secure . Each site is a module inside it, with its own boundary.

Immutable by design

Built from parts that don't drift

Every layer is pinned, versioned and rebuildable from source. The same inputs produce the same system - here, or on your own hardware.

01

Versioned

Every change is a commit

Nothing is edited in place. Every state of the system is a point in history you can rebuild from exactly.

02

Continuous

Deploys are rolling

Build, migrate, drain, rotate. The new version is up before the old one stands down, so live sessions carry straight through.

03

Self-contained

Every domain is its own module

One module per host, each with its own boundary. Sites share no mutable state, so every one is built - and rebuilt - on its own terms.

NRPS

Ask → live. Same moment.

Tell us what you want to see and what data it sits on. You get a live link and a named agent behind it.