Manual · The book

What Neuridion deliberately does not do, and why.

A tool earns trust by saying what it will not do. These are decisions, not gaps — each with its reason, and none discovered by surprise at a customer's desk.

No Undo — yet

Model A (leaving a field writes it) costs exactly one thing: there is no way back from a mistake. Undo is planned for 2.0 — done right rather than rushed — and until then the nets are real: automatic backups, the read-before-write rule on everything destructive (deletes ask and show, imports preview, restores copy first), and the revision counter that refuses silent overwrites in multi-user work.

“Protected”, never “uncrackable”

Your project travels inside a built application as an encrypted payload, and your scripts are protected from casual reading. A determined attacker with the application on their own machine can defeat any such protection — ours, and every competitor's. We say protected and mean it; anybody who says uncrackable is selling something.

macOS, and only macOS

No Windows, no web version, no mobile. Being one platform's native product — newest technology, no compatibility baggage — is the advantage, not the apology. (Whether the server could one day serve your forms to a browser has been studied and answered “possible, later, deliberately”; it is a 3.0 question.)

Not in the Mac App Store — yet

An App Store build is sandboxed to Apple's rules, and a sandboxed application cannot write wherever your scripts say. That has to be found out by building one and clicking through everything — planned for 2.0, and the build sheet will say plainly what such a build cannot do.

The internet is a VPN

Client/Server targets the local network. Over distance the official road is a VPN; a relay of ours is ruled out for ever, because it would be the first service a built application could not live without.

No users, no permissions — on purpose

Who may do what in your application is your customer's question, and you answer it with a login form, security.hashPassword and table events — the examples show the whole pattern. A permission system of ours would be one more thing between you and your rules.

What never changes

An application Neuridion builds contains no licence check, phones home to nobody, and never expires. That sentence has a mechanical guard in our build process and is the one promise everything else here is arranged around.