Elementary Interactive

What you own

Most vendors leave this question to the contract. Here it is up front.

What doesn't transfer

The Nitrogen platform is licensed, not sold. Neither the platform's own packages nor the third-party libraries it depends on become your property when an engagement ends.

That is true of every licensed platform. We say it on a public page rather than leaving it to a clause you find in month eleven.

What is yours

Three things that are yours, without qualification.

Your content

Pages, media, documents, submissions, attendee data. At any point, in a format another system can read.

Your configuration

Data structures, fields, taxonomies, permission groups, workflow definitions — the description of how your system works.

Custom code written for you

Where a bespoke administration layer is built for your organisation, that code is yours.

Why configuration can be yours

In 1945 John von Neumann described a machine whose instructions live in memory as data, rather than being wired into the hardware. It is the reason a computer can be reprogrammed instead of rebuilt.

Nitrogen works on the same principle. Your data structures, permissions and processes are not written into the platform's code — they are records in a database. That is what makes them describable, portable, and yours.

It is also what keeps the system's behaviour out of the vendor's hands. What your platform does is determined by its configuration, not by what we are willing to change.

The same applies to action

An action is attached to an identity. Agents run under a user, not alongside one: without a permission they cannot act, and what they do appears in the audit record exactly as a person's work does.

Exchanges with a language model are retained in full — the prompt sent, the response received, and the token usage behind it. Neither depends on our discretion: it is how the records are written.

Take-out

Because configuration is data, it can leave.

Take-out is our commitment to export it in a documented, human-readable format — JSON or YAML — on request, and at the end of an engagement. Not a database dump: a description of how your system was set up, in a form another team can read.

What take-out does not solve

It gives you the description, not a running system. Rebuilding on another platform would still be work.

What it removes is the part that is usually impossible: knowing what you had.

Vendor continuity — what happens if we disappear — is a separate question. We answer it on How we work.