WRITTEN AND PROVEN — IN SERVICE FOR OHMNIA
Together, without the cloud.
Nexika is the ResonLab multi-workstation server. One file to copy onto a PC or a NAS, and your workstations work on the same data — which never leaves your walls.
The link, not the trade
The name says what it does: the nexus. It holds no trade of its own — it links workstations to a single truth. Each application hands it a register of operations, a table of rights and a way to open its database; it brings everything else.
Ohmnia and Scenika
One server for both. A company that invoices and hires out gear does not install two account servers — two account servers that drift apart are worth less than no server at all.
Acustika is left out on purpose. It works on project files, not on shared company data. Two people do not edit one simulation at the same time.
On a machine of your own
An office PC, a NAS, a spare machine. One file to copy, started by a command: no installation, no npm install, no native dependency.
No cloud, no subscription, no data held by a third party.
Three roles, not thirty
Read to consult, write for day-to-day work, administer for what commits the company.
Every operation has its right, written by hand. Never inferred from the channel name: a rule saying “list means read” would be silently wrong about conditions:accepter.
Local mode does not move
Without a deliberate step on your part, the applications run offline exactly as before. Multi-workstation is chosen; it never arrives on its own.
It is a setting, not a different edition. And changing your mind never erases the local data.
What it refuses to do
These refusals are not settings: they cannot be switched off. Each has an automated check, and each has been proven by breaking it on purpose.
Listening without an administrator
While no administrator account exists, the server accepts only 127.0.0.1. Otherwise the first passer-by would create their own and take the books.
Listening without encryption
Passwords and tokens would travel in the clear. On 127.0.0.1, HTTP stays accepted: the traffic never leaves the machine.
An operation with no declared right
An operation whose right was never written is refused at runtime, and the check reports it. An oversight does not turn into an open door.
Losing the last administrator
They can be neither demoted nor disabled. A server with no administrator can never be taken back in hand.
One detail that matters: the sign-in failure message is the same whether the account exists or not. Otherwise the sign-in page would become a way to find out who works here.
Bringing it up
The first two refusals impose an order: the server must never be reachable before it is already protected. A five-step procedure gets botched — and when it does, the temptation is not to start over, it is to look for a way around the refusal that blocks you. The assistant satisfies them in the right order, in one command.
One command
The assistant does everything a machine can do on its own: the folder, the certificate, the first administrator, and the file that brings the server back after a reboot.
Then it prints the command to run and the address to enter on the workstations.
Nothing is overwritten: a certificate already accepted, an account already created — it notes them and moves on. You can rerun it without thinking.
It replaces no refusal — it satisfies them in the right order, which is different.
The certificate is built by the server itself, without OpenSSL. Requiring someone to fetch an external tool and retype an arcane line is an invitation to leave the server in the clear — that is, to defeat a security measure through the way it is deployed. It covers localhost, 127.0.0.1 and the machine’s IPv4 addresses: without those, a workstation aiming at its IP could verify nothing.
Each workstation will have to accept it once: that is normal for a self-signed certificate. It encrypts the link perfectly; what it does not do is prove to a stranger that they are talking to the right server. An existing certificate is never overwritten — every workstation that accepted it would ask for confirmation again.
What it does not do yet
Better said here than discovered in production.
Automatic startup takes one line
The assistant writes the file you need — a scheduled task on Windows, a systemd unit on Linux — and prints the command to run. It does not install it for you: a program installed silently is a program nobody knows how to stop six months later.
Designed for your walls
As soon as the server becomes reachable beyond the local network, it belongs behind a proper HTTPS reverse proxy.
It is your machine
The data lives with you: so does backing it up. That is the trade-off for having no cloud, and it has to be said.