Airports, utilities & critical infrastructure
No valid permit.No engine start.
A reader in the cab checks apron permit, type training and departure check before a ground vehicle’s engine can start – and Attraccess records who drove what, when and in what condition. The same rules cover workshop equipment. For airports, ground handlers and utilities, on your own servers.
- On-premises, no cloud account
- Your DESFire badges or ours
- Source code available to your security review
Access decision · example
Pushback tug PB-07
Reader in the cab · start released via relay
Choose a person
- Apron driving permit: passedValid until 04/2027
- Type training · pushback tug: passedRefreshed 02/2026
- Vehicle status: passedNo open maintenance
- Departure check on the reader: passed6 of 6 items confirmed
Trusted in production at
TUHHTechnischeUniversität HamburgUniversity · labs & workshopsaticinteriorWoodworking coworking & interior manufacturing
Today
Three lists, one key board, no check.
In most depots and plant workshops the rules are right. They just aren’t enforced at the moment someone turns the key.
01
Permits and trainings live apart
The apron permit sits with the airport’s ID office, type trainings and welding certificates in a spreadsheet, keys on a board. Nobody cross-checks all three at 5 a.m. before the first turnaround.
02
Expiry dates expire silently
A refresher lapses and the person keeps driving – until an audit or an incident finds out.
03
After an incident, everyone searches
Who had the de-icer at 06:10? Was the departure check done? Paper logs are incomplete, illegible or missing.
How it works
From badge to engine start in seconds.
The example is a pushback tug. The same steps work for de-icers, high loaders and baggage tractors – and for the lifts, tyre changers and welding gear in the GSE workshop.
Beforehand
Permits and trainings, with expiry
Record apron permits, vehicle-type trainings and safety briefings per person, with an expiry date or a refresher interval. Trainers sign off in the app; if you want, supervised first drives count towards the introduction.
In the cab
Tap before you start
An Attractap reader in the cab reads DESFire EV2/EV3 badges – your existing ones if your issuer provisions an application, otherwise cards issued by Attraccess. It checks every requirement for this vehicle.
On the reader
A departure check, not a clipboard
A checklist on the reader’s touchscreen: tyres, lights, hitch, fluids. Required items have to be confirmed before the vehicle is released.
At the starter
Start released, never cut
A relay in the starter or start-enable circuit releases the start. Once the engine runs it stays untouched – Attraccess never switches off a moving vehicle.
On return
Return, report, maintain
Ending the session records duration and the return checklist. Defects become maintenance requests for the workshop, usage hours trigger inspections – and a vehicle in maintenance can’t be checked out.
Honest status
What works today – and what we build with you.
Critical infrastructure deserves precise answers. Here is what Attraccess does now, what we set up together in a pilot, and what doesn’t exist yet.
Qualifications with expiry and refreshers
Expiry by date or after a period without use, trainers per resource or group, supervised sessions that turn into an introduction.
Checklists at session start and end
Required checkboxes and fields on the reader and in the app – the departure check and the return report.
Existing badges, secured with AES
MIFARE DESFire EV2/EV3 with an application from your badge issuer, or DESFire and NTAG 424 DNA cards issued by Attraccess.
Maintenance that blocks use
Inspections by usage hours, number of uses or interval. Anything in maintenance stays locked for everyone except the workshop.
Audit log and exports
Every sensitive change with who, what and when, with configurable retention. Session exports per resource as CSV.
On-premises with single sign-on
One Docker container in your data centre, no cloud account. OIDC and SAML with Entra ID, Keycloak & co., passkeys and 2FA.
Engine start release on the vehicle
Reader in the cab, relay in the starter or start-enable circuit, powered from the vehicle. We fit, commission and test it with you on the first vehicles of one class.
Workshop equipment, lockers and gates
Relays and PLC outputs switched by flows. We wire, commission and test them with you on site.
Your telematics and training systems
A REST API and MQTT/HTTP flows pass go/no-go decisions to systems you already run. We build the connector with you.
Offline operation on the apron
Today the reader needs network at the moment someone taps, so vehicles are released where they park: at the depot, the charging point or wherever your WiFi reaches. Starting without any network isn’t available yet.
Attraccess decides who may use a resource. It is not a safety function and has no PL or SIL rating.
“Set up in the pilot” means the software side exists, and we wire, configure and test it with you on site.
FAQ
Questions from security, operations and the works council.
Why a small team
Small team. Direct answers.
Attraccess is built by a small company in Hamburg. For you, that means fewer layers between your problem and the fix.
The engineer on the call wrote the code
No ticket ping-pong through support tiers. You know the people by name – and for the pilot we commission the first readers with you on site.
Your gap becomes our sprint
Missing an interface? We build it with you in the pilot instead of putting it on a roadmap slide. Scope, cost and ownership agreed in writing.
You shape the product
Pilot partners have a direct say in what we build next. Your requirements end up in the product, not at the bottom of a feature-request queue.
Code your security team can read
Attraccess is source-available. Your IT security can review the source code of the server and the reader firmware.
The questions procurement will ask, answered upfront
- No ISO 27001 certificate. We answer your security questionnaire in full – including the answers that are “no” – and show how we scan our dependencies.
- No 24/7 call centre. Support hours, response times and escalation are agreed in the contract – and you reach an engineer directly.
- What if we’re gone? Attraccess runs on your servers, with your data in one folder. Data export, licence continuation and source-code escrow can be part of the contract.
Start with a handful of vehicles.
We’re looking for pilot partners: a few vehicles of one class at one depot, or one plant workshop. Engineers on site for commissioning, success criteria you define – and a say in what we build next.
- 1Free intro call about vehicles, equipment, permits and badges
- 2Site visit and a written pilot plan with success criteria
- 3Pilot on a few vehicles of one class or in one workshop
- 4You decide – based on your data, not our slides
Other use cases
