Egameno

HSSE operations platform

The safety record a working site can actually keep.

Incidents, permits, risk and compliance in one system of record — captured on the phone in a gloved hand, at the point the work happens.

4
Modules, one record
100%
of tenant tables under forced row‑level security
0
Ways the app can edit its audit log

The problem

Safety runs on spreadsheets.

The incident happens on the night shift, on a jetty, in the rain. It reaches a clipboard, then a spreadsheet on somebody's laptop, then an email with three people copied.

It is filed late

By the time it reaches the person who can act on it, the shift has changed twice.

It is filed thin

The detail that mattered — which bay, which asset, who was standing there — has been rounded off.

It cannot be trusted

A spreadsheet can be edited by anyone, afterwards, with no record that it was.

The platform

Four modules, one system of record.

One codebase, configured per site. A permit knows which assets it isolates; an incident knows which risk assessment governed the work.
01

Incident & Observation

Building now

Report from the deck in under a minute. Triage, ICAM investigation, corrective actions with owners and due dates, and close-out.

02

Control of Work

Specified

Permits to work and isolations, with required competencies checked against the people actually on site rather than a folder of certificates.

03

Risk & Compliance

Specified

Risk assessments attached to the work they govern, so a control is something a permit can be blocked on rather than asserted in a document.

04

Environment & Analytics

Specified

Leading and lagging indicators computed from the record itself — per site, per contractor, per period — not re-keyed into a monthly deck.

Built for trust

The questions a safety buyer asks first.

We have no customer logos to show you — Egameno is new. What we can show you is how it is built, which is the part that would still matter if we had them.
Port terminal
Copper mine
Vessel operator

Enforced at the row

Row-level security

FORCE on every tenant table. The application role cannot bypass it.

One pooled PostgreSQL
Append-only audit log
Region recorded per tenant

Isolation is enforced by the database

Separation does not depend on application code remembering to filter. It holds even when the query is wrong.

The audit log cannot be rewritten

The application role holds INSERT and SELECT and is explicitly denied UPDATE and DELETE, so neither a bug nor a compromised session can revise history.

The data region is stated

Each tenant records the region its data is held in, and where the system runs is written down rather than implied.

Who it is for

The sites that are hardest to serve.

Container terminals, yards, mines and vessels — where the person who sees the hazard has both hands busy and twenty minutes of no signal ahead of them.

One hand, in gloves

Capture targets are sized for a gloved thumb and never drop below the 44px floor, with the primary action at 56px.

In direct sun

The interface is achromatic at rest, so when a safety colour appears it is the most saturated thing on the screen and means something.

With no signal

A send that fails does not clear what you wrote — the report stays on screen, ready to go again the moment the connection returns. Queued offline capture ships with the module.

That constraint shaped the product rather than being accommodated after it.

Request access

Tell us what you run.

Egameno is onboarding a small number of design partners — sites willing to be specific about what their current process actually costs them.

We read every request ourselves and reply within two working days.

By submitting you agree to our terms and to the handling of your details described in our privacy notice.

We use this only to reply to you. It is not added to a mailing list.

Egameno — HSSE operations for heavy industry