Records
Every company's records live in a database of their own, not in a shared table sorted by a company column. A sign-in opens one company's database.
Security
What protects a company's records, stated as it stands today.
Each company on its own database.No bridge between companies.
Files
Every company's files sit in a folder of their own, beside its database.
Infrastructure
PIRION runs on Google Cloud technologies.
No back door into a company's records.No support account. No signing in as someone else.
No database screen
No screen in PIRION lets a person open a database or run a query on it.
No view from above
The screen that runs the platform shows companies, credit, AI usage, backups and health. It does not show a company's modules, its user list or its keys.
Help on request
When a company needs support, it shares a key for that time, then its own Admin gives a new one.
Roles, ships and a record of who did what.Set by the company, kept by the system.
Roles
What a person can do in each module comes from the role the company gives them.
Ships
An account is bound to its ships, and the office works across the fleet. A ship's account asking for another ship's certificates is refused.
System log
Saved changes leave a line in the System log: who did what, and when.
Locked at the door.Sign-in, sessions and the connection.
The connection
Between the browser and the server, everything travels encrypted.
Passwords
Stored only as salted hashes, never as the password itself.
Wrong tries
A source that keeps guessing is refused for a while. The limit fades with time, so a mistyped password never locks a seafarer out for good.
Sessions
A session ends after 30 minutes without use and after 12 hours in all, unless the person chose "Keep me signed in for 90 days".
Administration
The system's administration screens do not open from the public address.
Two kinds of backup, and a person decides.Going back is never automatic.
Copies
Each company's database is copied twice a day, and the last fourteen copies are kept.
Nightly trial
Every night the newest copy is restored on trial, never for real, to show that it can be. Its tables are counted against the last trial, and a table that has shrunk by half or more is named on screen.
Disk snapshot
Once a day the whole disk, files included, is captured and kept for fourteen days away from the server.
Restore
The system notices a fault and reports it, but it never goes back to a copy by itself: one misread fault could start an endless loop of restores, each undoing newer work. A company's database goes back to a copy only at the request of its ADMIN & IT, when a person presses Restore and gives the key again.
What goes to an AI provider.Said plainly.
When an agent runs
The text it needs is sent to an AI model provider over an encrypted connection. Each run works on one company's records.
The Consultant
It reads the records through a read-only connection, so it cannot change them. Every query is checked before it runs, and the table holding password hashes is closed to it.
What people write
Text people write reaches the agent marked as material to read, not as instructions. A sentence in a report that reads like a command counts as part of the report.
Reviewed by AI agents, built on little.Checked again and again, with as few moving parts as possible.
Security reviews
Current AI agents have reviewed the code and the live system repeatedly, each area by its own reviewer, with every finding challenged before it counts. The latest full check, in October 2026, found no critical or high finding.
Load and link
Speed under load has been measured on a copy of a company's data. Screens are walked over a link held to 400 kbit/s with a 700 ms round trip.
Few dependencies
The server stands on nine direct packages, the browser screens on five. Each one added is a decision, and the locked set is checked against public vulnerability lists.