Product
Scientific licensing
Licensing of research and method so that a result can be used without its provenance being surrendered.

Customer controlled Linux host · Browser access
What this covers
Licensing of research and method so that a result can be used without its provenance being surrendered.
How it is engaged
Scope and terms are agreed in writing before work begins. The commercial terms state what determines scope and how engineering is charged.
Where it runs
Install on a customer controlled Linux x86-64 host with PostgreSQL 18. People use it through a browser that can reach the host.
Installation, updates and recovery
| Supported target | A customer-controlled Linux host on x86-64 with PostgreSQL 18 (linux-x86_64-customer-controlled). |
|---|---|
| Not yet supported | Windows, macOS, phones and tablets, and Linux on other architectures. Each needs its own installation, update and recovery evidence before it is supported. |
| Check a device | Run rjv preflight on it. It reads the operating system, architecture, memory, disk, listen address, configuration, database, database role and schema, changes nothing, and exits non-zero if the current release cannot run there. |
| Installed as | One application and a PostgreSQL database. rjv install lays the current release (schema 162) down with a hardened service unit and an environment file, and installs every system on this site, including Scientific licensing. |
| Needs | Nothing beyond the release and its PostgreSQL database. |
| Data | It stays in the PostgreSQL database you run. The only outside service the release can use is an outbound mail relay that you configure. |
| Updating | A release is a numbered build. The schema is applied by a separate owner step (rjv migrate), and the application refuses to serve a schema it was not built for. |
| Backup and restore | rjv backup writes a checksummed dump. rjv restore restores it into an empty database and checks the checksum, the schema version and the audit chain of every account. |
| Leaving | The data is in your own database and can be dumped at any time. What you may do with the release is set by the terms on deployment and ownership. |
On a phone or tablet
Use the browser with a connection to the host.
See what works on your device
- Find this offering
- Browser (W)
- Carry out every authorised operation
- Client (C)
- Compute on the device itself
- Not supported (U)
- Use a host you own
- Client (C)
- Work without the host or the internet
- Not supported (U)
Nothing here needs a desktop because every operation that this site offers works in the browser on a screen down to 320 CSS px which is the narrowest width that we test. Where a row reads Not supported the browser is the alternative because we do not install the release on the device and no offline mode exists and the host that you control must be reachable and we do not use device sensors or accelerators.
- Published
- 28 October 2026
- Revision
- 4