For rig IT and the DPO
Your record stays on your rig.
Where the data lives, who can change it, and what leaves the rig. The technical note with the detail is available on request.
For rig IT, the DPO and the auditor
Your record stays on your rig.
The questions IT and data-protection people ask before anyone signs, answered plainly. A technical note with the detail is available on request.
Where the data lives
Installed on one Windows machine on the rig, the designated host; browsers on the rig network reach it. Nothing is installed per seat and nothing is stored in a cloud.
Internet
None required. Nothing listens from outside the rig, nothing phones home, and there is no telemetry. The AI runs on the host; no record is sent to an outside service.
Who can do what
Named sign-in for permits, hazmat and admin, with PINs stored hashed and locked out after failed attempts. Each department sees its own screens. The operator's window is read-only by construction.
Records that cannot be quietly changed
A closed permit or a submitted card is sealed with a key that never leaves the host. Signatures form an append-only chain, and every record that matters carries who did what, and when.
One writer for stock
Stock has a single writer: the ledger. On-hand, consumption and runway are derived from movements, never typed over. Two copies of the record are never allowed to disagree about a count.
Backup and recovery
A backup is a folder: one copy captures the database and its identity, with rig-local time on every date. If the host fails, a documented recovery brings the record up on a replacement machine.
It is your record
The data belongs to the contractor whose rig writes it. It leaves the rig only as the reports and backups you choose to send, and the five standard reports export in the same format every month.
Voice, kept on the rig
Safety cards can be spoken or typed in English; Thai speech follows after review. The recording stays on the host with its card, and discarding a card deletes its recording.
Demonstration and live kept apart
The demonstration fleet is fictional and a build guard keeps real operational data out of it. What you see in a demo is never another contractor's rig.
Updates
No automatic updates. New versions are installed on the rig by agreement, never pushed, so a rig in the middle of a well is not surprised by a change.
Need the detail for a security review? Ask for the technical note, or put your IT lead on the demo call.
Ask for the technical noteBuilt for offshore
Works at 3 a.m. with no signal.
Offline-first
Everything runs on the rig's own machine. Nothing waits on a satellite link.
One host, every workstation
Installed on one Windows machine on the rig; browsers on the rig network reach it. Nothing installed per seat.
Installed in a day
Usable from the first hour; registers filled over the first week. A Windows machine on the rig, a label printer and a UPS.
No inbound connection
Nothing listens from outside the rig, so the IT conversation is short. Browsers on the rig network connect over a certificate the host issues for its own address.
Individual sign-in
Permits, hazmat and admin need a named person. PINs are hashed and lock out after failed attempts.
Sealed records
A closed permit or submitted card is sealed with a key that never leaves the host machine.
Full audit trail
Who did what, and when, on every record that matters.
Your language
Thai and English in the app; voice cards in English, Thai after review. Other languages are added per fleet, and safety wording is reviewed by a person.
Backup as a folder
One copy captures the database and its identity. Rig-local time on every date.
Department scoping
Each department sees what it needs, not everything.
Nothing phones home
No telemetry and no automatic updates. The rig's data goes only where you send it.
White-labelled
Runs under the contractor's own name and branding.
See it on a rig.
Thirty minutes on a call, then a service technician on board with your crew.