Axxession
An engineer entering a code to open a server rack
Inside the hall

Provable access, rack by rack

In this sector the access record is not an admin artefact. It is part of what you are selling. Cage- and rack-level control, escorted visitors and tamper-evident logs.

Data Centres

Data centre access control and customer audit evidence

Your customers audit you, and access is what they audit

Who is on your sites

Remote-hands and field engineers

OEM technicians, often at night, often once

Customer and tenant visits

Escorted, ticket-driven, per hall or per cage

Construction and fit-out

Long build-out phases inside a live facility

Auditors and certification bodies

On behalf of your customers

What you are held to

Customer contracts · information security standards

  • Access to a customer's hall or cage restricted to named, approved people
  • Every visit tied to a reason. A ticket, a work order, an approval
  • A full record produced on the customer's timetable

Where it breaks today

  • Access is sold per cage but granted per hall, because the access system groups it that way
  • Escorted visits are logged on paper at reception and typed up later, or not at all
  • Every customer audit becomes a manual export and a week of somebody's life
An engineer entering a code to open a server rack

A prospect asks how you control access to their hall. Today the honest answer is a process document. It should be a screen you can turn around and show them.

Data Centres

Scenario

A customer audit with 48 hours' notice

Your largest tenant is being examined by their own regulator and needs 12 months of physical access evidence for their hall.

The request lands on a Friday

12 months, one hall, every person who entered. With the reason and the approval behind each visit.

Pulled from the record

The history is already in the platform because it was recorded as it happened, per person and per zone.

Each visit carries its reason

The work order or ticket that justified the access is attached to the grant, and therefore is the approver.

Handed over signed

The report exports in a form the tenant can put straight into their own evidence pack.

What changes

  • The audit answer moves from days of manual export to minutes of filtering
  • No standing access to customer halls, every entry is requested, approved and time-boxed
  • The access record becomes something your sales team is happy to show
Questions

Frequently asked questions

Can access be granted per cage instead of per hall?

Yes. Zones are modelled in the governing layer, instead of being inherited from how the access control system happens to group doors. A grant can be scoped to a single cage even where the underlying system groups at hall level.

How quickly can 12 months of access evidence be produced for a tenant?

In minutes, and without a data project. The history is recorded as it happens, per person and per zone, with the approver and the reason attached to each grant. Producing the report means filtering a record that already exists.

Does every visit have to carry a ticket or work order?

It can. Access requests can require a reason. A ticket, a work order or a named approval. That reference stays attached to the grant in the evidence record.

The first step

Start with 1 site and 1 population.

You judge something that runs on your own site. Your access systems and readers stay where they are. If it earns its place, we extend it site by site.

One siteOne populationYour readers stay