Our access to your server, on the record

Why

After an incident, the first question is who touched the server.

Your system holds your money, your stock and your customers. The people who run it can open the server it lives on. Auditors, banks and boards ask the same thing: who from your supplier entered production, when, and what did they do? Most suppliers can only give their word. We give you the record.

How it works

Four steps, and each one runs by itself.

This is how every server we have set up since November 2026 works. Nothing depends on a person remembering to do it.

Step 1

The server writes it down.

Every 15 minutes, the server copies each new sign-in, each switch to administrator rights and each command run with those rights into a record for the month. Lines are only ever added.

Who · when · from which address · which command

Step 2

It seals the month.

Once a day, the server encrypts the month so far. Only one key can open it, and that key is not on the server.

Encrypted before it leaves the server

Step 3

It stores the month where it cannot take it back.

The sealed month goes to separate storage. The server can add to that storage and can never delete from it. The storage itself refuses to delete any record for 35 days, whoever asks, including us.

Add only · locked against deletion

Step 4

Another machine checks every hour.

A separate machine checks that each server stored its record today. If a server goes quiet for two days, or tries to hide a record, we get an alert.

Checked every hour

What you get

Ask for any month. You get it within five working days.

What the record shows

Who entered your server, by name.
When they signed in and when they left.
The address they came from.
Every command they ran with administrator rights.

How it reaches you

One encrypted file, and a one-time key that opens it.
The file and the key travel by two different channels, for example email and a message.
When your agreement ends, the whole record goes to you with its key. Our copy is deleted within 37 days.
It is part of every system we run. There is no extra fee.

Other suppliers

What other suppliers give you.

We read the public documentation of the systems our clients compare us with, on 10 November 2026. Each row links to its source. If something has changed, write to us and we will correct the row.

Supplier	When their staff access your system	What you can see	Source
OdooOdoo Online, Odoo.sh	Support staff sign in with their own staff credentials. Odoo says their actions are separately controlled and audited.	The security page does not offer you a copy of that record.	odoo.com
Zoho	Administrator access and privileged commands on Zoho’s servers are logged, and Zoho audits them.	Your audit log covers the actions of your own users. The security page does not offer a copy of staff access.	zoho.com
MicrosoftDynamics 365	Customer Lockbox: an engineer asks, and your administrator approves or refuses before Microsoft opens your data. Emergencies are excepted.	Each request, in your audit log. It needs Managed Environments and a Microsoft 365 E5-level licence for your users.	learn.microsoft.com
SAPS/4HANA Cloud	The application’s security audit log records the requests of SAP’s support users.	The application’s log. The logs of the servers underneath stay with SAP, unless you buy an extra service for the private edition.	sap.com
Salesforce	You grant support staff access to your account for a set time, up to one year.	Changes they make in Setup appear in your Setup Audit Trail, kept for 180 days.	salesforce.com
Google WorkspaceFor comparison, not an ERP	Access Transparency records each time Google staff open your content.	The full log, in Enterprise Plus and a few other top editions only.	google.com
A partner who hosts your systemon its own server	The server keeps its own system log.	Whoever administers the server can edit or delete that log. A copy for you is rarely part of the contract.	-
a-systems	Every sign-in and every administrator command, sealed and stored where the server cannot delete it.	Any month, within five working days, in every plan.	This page

The large platforms keep this for their top plans. We include it in every system we run.

Limits

What this does not do yet.

The same rule as on our Trust page: we list the gaps too.

No approval before each accessWe do not ask your permission each time one of us enters the server. Microsoft and Google offer that in their top plans. We keep the record instead, and you can check it.
35 days of lock on your server’s recordAfter 35 days the record stays for as long as your agreement runs. From then on, the owner of the storage account, which is us, could delete an old month. On our central servers, which build and hold the software for every client, the lock lasts three years.
Systems started before November 2026They use the earlier form. The record is the same, but it is sealed every month and copied to a second machine of ours, where we could delete it. Each system moves to the locked storage when it moves to a server of its own.
A system on your own serverThe server keeps its own system log, and your administrator reads it directly. A sealed copy into storage of your own is planned.

When we enter your server,
it goes on the record.