Skip to content
GarnetOS

Built in the UK, for UK businesses

Run the company, not the admin.

GarnetOS keeps your people, documents, approvals and compliance evidence in one connected system — and tells you what needs attention next.

For teams of 10–250. No card, no trial clock — we will show you the product and tell you honestly whether it fits.

The GarnetOS Action Centre, listing work waiting on one person

Home

My actions

4 open

  • Approve Ahmed Siddiqui’s leave

    Leave

    Five days requested from 14 April. Two others in Operations are already off that week.

    Due 9 AprWith You
  • Verify Sarah Donnelly’s passport

    Documents

    A new document was uploaded on Tuesday and nobody has checked it against the original.

    Due 11 Apr
  • Resolve an attendance exception — Tomas Novak

    Attendance

    Recorded as working on 2 April, which is a closure day for his working pattern.

    Overdue — was due 4 Apr
  • Review a change to Priya Nair’s salary

    People

    Her pay was changed on 1 April, effective from 1 May. A second person has to look.

    Due 15 Apr

Why this exists

Your company already has systems. It does not have one.

Most businesses of this size run on a payroll product, a shared drive, a calendar and about nine spreadsheets. Each is fine. The gaps between them are where the work goes missing.

  • A spreadsheet of holiday
  • Contracts in a shared drive
  • Passport scans in an inbox
  • Probation dates in a calendar
  • Approvals in WhatsApp
  • Right-to-work checks in a folder
  • Starters in a chain of emails
  • Who reports to whom, in somebody’s head

Nothing here is wrong on its own. Together they are the reason nobody can answer a simple question quickly.

One structured layer

  • Every person, with their actual record
  • Every document, with its expiry
  • Every approval, with who decided and why
  • Every obligation, with the evidence behind it

Action Centre

One place for everything waiting on you.

Leave to approve, a document to verify, an attendance exception, a salary change that needs a second pair of eyes. In most companies those live in five places. Here they are one list.

What happened
Stated plainly, in the title.
Why it matters
Every action carries its reason. Not a subtitle — a required field, so nobody is asked to do something without being told why.
What happens next
The decision, and where it is recorded.
The GarnetOS Action Centre, listing work waiting on one person

Home

My actions

5 open

  • Approve Ahmed Siddiqui’s leave

    Leave

    Five days requested from 14 April. Two others in Operations are already off that week.

    Due 9 AprWith You
  • Verify Sarah Donnelly’s passport

    Documents

    A new document was uploaded on Tuesday and nobody has checked it against the original.

    Due 11 Apr
  • Resolve an attendance exception — Tomas Novak

    Attendance

    Recorded as working on 2 April, which is a closure day for his working pattern.

    Overdue — was due 4 Apr
  • Review a change to Priya Nair’s salary

    People

    Her pay was changed on 1 April, effective from 1 May. A second person has to look.

    Due 15 Apr
  • Provide missing evidence — right-to-work check

    Compliance

    The record names a check on 3 March but no document is attached to it.

    Due 18 Apr

Actions are raised by the system from what actually changed — not typed in by somebody remembering to.

The platform

Built around the company, not a department.

People software knows about people. Document software knows about files. GarnetOS holds one record of the organisation, so a leaver, an expiring passport and an unapproved change are the same kind of fact — and can raise the same kind of action.

People
Documents
One systemYour companyOne record, one set of permissions, one audit trail
Compliance
Operations

Designed for, not built yet

  • Assets
  • Software & subscriptions
  • Finance

People

A reliable record of everyone in your organisation.

Not a directory. The actual record — who they are, what they are contracted to, who they report to, what they have taken, what you hold on file, and every change anybody has made to it.

  • Employee records and contracts
  • Organisation structure and teams
  • Leave, with balances worked out
  • Attendance and exceptions
  • Onboarding and offboarding checklists
  • Documents, with expiry dates
More on People
An employee record in GarnetOS, showing leave balance and documents

People · Employees

Priya Nair

EMP-014

Operations Manager · Operations

Started 4 March 2024 · Marlow Ltd

Review required

Annual leave · 2026

9.5

days left

Allowance
28
Carried in
3
Taken
21.5

Documents

  • PassportIn 24 days
  • Employment contractNo expiry
  • Right-to-work check3 Mar 2026

Compliance

The word “compliant” appears nowhere in GarnetOS.

Not an oversight — a test that fails the build if anybody types it. No software can judge where a company stands legally, and the ones that imply otherwise are selling a feeling. GarnetOS does something more useful: it shows what is missing, what has changed, and what a person needs to decide, then keeps the evidence behind every decision they made.

How compliance works

The only words it uses

  • Evidence complete
  • Review required
  • Evidence missing
  • Potentially reportable
  • Action required

Each one describes the state of your records — a fact the software can stand behind. None of them describes your legal position, which is not ours to judge. When something may need reporting to an authority, GarnetOS says potentially reportable and names who should decide. A person does the reporting, and records that they did.

Who it is for

The same system. Six different jobs.

What somebody sees follows what they are responsible for. An employee gets their own details and nothing else; an owner gets the whole organisation without asking anyone for a report.

  • Business owner

    See what is happening across the organisation without asking anyone for a report.

  • Operations

    Run joiners and leavers to a checklist that says who is doing what, and by when.

  • HR

    Keep people, records, leave and documents in one place that is actually current.

  • Manager

    See your team and the decisions waiting on you. Nothing else.

  • Compliance

    Find the gaps in evidence and the changes that may need reporting, before an audit does.

  • Employee

    Your details, your documents, your leave. None of the company’s administration.

How it fits together

One person joining, from first record to ongoing watch.

Not six screens somebody visits in order. One record moving through states, with the system raising the next piece of work each time — and carrying on long after the first week.

  1. Record created

    Name, start date, job, legal entity.

  2. Documents requested

    The person is asked for what is missing.

  3. Account invited

    They set their own password. Nobody emails one.

  4. Evidence reviewed

    Somebody checks each document and signs it off.

  5. They start

    Leave allowance opens, pro-rated from the start date.

  6. Still watching

    Expiries, probation dates and changes keep raising actions.

Audit trail

Know what changed, who changed it, and why.

Every consequential change is written to an append-only record. Not a log somebody could tidy up later — the database grants the application permission to insert and read, and nothing else. A year from now, the answer to “who approved this?” is still there.

What changed
The field, the old value and the new one.
Who changed it
A named person, not “system”.
When
Recorded at, and effective from — which are rarely the same date.
Why
The reason given at the time, required on anything consequential.

How we build it

Software shouldn’t make you check five places to find out what your company needs.

Every screen in GarnetOS is built to answer four questions without being asked: what happened, why it matters, who needs to act, and by when. If a feature cannot answer those, it is not finished.

Security

Built for data you are legally required to look after.

Employee records, passports and right-to-work evidence are not ordinary application data. The architecture reflects that from the database upwards.

  • Separated at the database

    Every company’s rows are isolated by the database itself, not by application code remembering to filter.

  • Private file storage

    Documents are never publicly addressable. Access is a short-lived signed link, issued per request.

  • Uploads are scanned

    Files land in a quarantine bucket and are scanned before they can be read.

  • Two-factor sign-in

    Available to every account, and enforceable company-wide.

  • Encrypted throughout

    At rest with a customer-managed key, and in transit everywhere.

  • Hosted in London

    eu-west-2. Your employee data does not leave the UK.

Read the detail

Today

People, documents, compliance and the everyday operations around them.

All of it built, running, and the reason companies start with us.

Designed for

The rest of the company — assets, software, subscriptions, approvals and obligations.

The record and the permissions already work this way. We will tell you when the modules are ready, and not before.

See what one system could replace.

Half an hour, the real product, and an honest answer about whether it fits how you work today.