Let staff collect and return shared vehicles without chasing keys, calling the fleet desk or leaving gaps in the booking history.
Controlled pickup
Give drivers a clear collection path while keeping vehicle access tied to the booking and the person using it.
Secure key storage
Use vehicle hardware or Torus key cabinets to reduce key desk traffic and protect shared fleet keys.
Accountable return
Keep pickup, return, cabinet details and follow-up actions close to the trip, so issues are easier to resolve.
Hardware Range
Put the rightaccess hardwarewhere work starts.
Choose the physical access method that fits the site: vehicle-mounted Keyless Go hardware for direct access, or Torus cabinets for secure shared key storage.
Let approved drivers unlock the right vehicle. Keyless Go, RFID, relay and vehicle access hardware.
Keyless Go suits pool cars where drivers should collect the booked vehicle directly, with access linked back to the booking and driver.
Use installed hardware for vehicle access where the vehicle supports it
Support RFID and driver identification where the site needs named access
Reduce key desk handover for regular shared fleet use
Secure shared keys without building a key desk. Torus electronic key cabinets for depots and facilities.
Use Torus cabinets to control physical key release and return, with every handover linked to the booking.
Use 5, 15, 25, 50 or 100 key cabinets to match the site
Store shared vehicle and facility keys behind controlled access
Add emergency release, RFID reader and keyring options where the rollout needs them
Booking and Access
Show accesswhere the nextdecision happens.
Connect access hardware to vehicle rules, booking decisions and driver pickup.
Set the handover method on the vehicle. Vehicle access rules and cabinet mapping together.
Fleet teams can see whether a vehicle uses depot default handover, staff handover, keyless access or a Torus cabinet path before it reaches the driver.
Set access method by vehicle when it needs a different process
See the mapped Torus cabinet and slot beside the vehicle
Keep setup detail focused without exposing the full vehicle register
Key managementReadyPLT-204 · Toyota Hilux SR5 · West depotHandover methodHow drivers collect the keys for this vehicle.OverrideCabinet and slotMapped through the Torus integration.Require a booking to releaseKeys only release against an active booking for this vehicle.Custom instructionsShown to drivers in the booking and pickup flows.After hours, badge in at the West depot side door, then collect from the cabinet.81/200Last changed by Sam R. · 2d agoNew bookingStep 2 of 3Choose a vehicle · Tullamarine site · 9:00–2:006 of 6 available Tue 13 MayAvailabilityAccessKey pathDKP-55Ranger uteFree all dayReadyWST-KC1 · slot 4EV-12Polestar 2Free 9:00–2:00ReadyWST-KC1 · slot 7GHK-44i30 hatchFree all dayStaff handoverFront counterPLT-204Hilux SR5Free 9:00–2:00ReadyWST-KC1 · slot 12TRP-7HiAce vanFree 9:00–2:00Key path not set—VAN-12TransitFree from 8:00Staff handoverFront counterPLT-204 · keys release from the cabinet at pickup.
Show access readiness before the booking is confirmed. Availability, vehicle fit and key path in one choice.
The booking flow can surface whether the selected vehicle has automated access ready, so staff do not find out at pickup time that the key path is unclear.
Show the vehicle, pool and access method during selection
Highlight automated access readiness before the next step
Keep detailed booking work on the shared fleet booking page
Give the driver a clear pickup step. Scan, access and pre-trip tasks in the driver flow.
Drivers need enough instruction to collect the right vehicle and move on, without turning pickup into a support call.
Show the assigned vehicle and pickup step on mobile
Keep access instructions close to pre-trip checks
Use the driver flow to confirm what happened at collection
PickupDriver appPriya K. · PLT-204 Hilux SR5 · West depot, bay 3 · 9:00–2:00
Find vehicle
2Pre-trip checks
3Release keys
Scan at the cabinet to release the keysWest depot Torus cabinet · slot 12ReadyAfter hours, badge in at the West depot side door.Pre-trip checks3 of 5 doneWalkaround — no new damageRequiredFuel / charge level OKRequiredLights and indicatorsRequiredOdometer readingRequiredDash warning lightsRequiredPhotosOptional2 required checks leftTorus Technical Specifications
Cabinet sizes,security andintegration options.
Torus cabinets provide controlled physical key access where pool cars, plant or shared assets still need a key, with self-service issue, return and a complete audit trail.
Model
Capacity
Weight
Cabinet dimensions
Typical fit
Torus 15
15 key bunches
35.2 kg
674.8mm H x 532mm W x 212.6mm D
Smaller sites, satellite depots and compact car pools.
Torus 25
25 key bunches
39.1 kg
674.8mm H x 620mm W x 212.6mm D
Departmental pools and medium shared vehicle locations.
Torus 50
50 key bunches
54.1 kg
674.8mm H x 840mm W x 212.6mm D
Busy fleet rooms, councils, campuses and high-use sites.
Torus 100
100 key bunches
89 kg
941.8mm H x 1036mm W x 212.6mm D
Large fleet pools, central depots and multi-team operations.
Depth includes the mounting bracket. Torus cabinets are wall mounted and designed for indoor installation with no direct exposure to sunlight or water.
Hardware and power
110VAC to 240VAC input with 14VDC output
PoE, PoE+, PoE++ support
DC12V 7.2Ah rechargeable battery backup
Powder-coated mild steel body with 4mm polycarbonate door
Wall-mounted indoor cabinet with Bi-Lock mechanical override
Operating environment from 0C to 55C
Users and authentication
Up to 10,000 users and 100,000 cabinet events
6.5-inch capacitive touch screen, 800 x 1024 resolution
User ID plus PIN, card, or card plus PIN authentication
Card and fingerprint reader options using Wiegand and RS485/OSDP
Communications and storage
LAN 10/100Mbps Ethernet and optional 4G/LTE connectivity
Embedded Linux firmware with 8GB eMMC flash memory
20GB per cabinet for event data
365-day reporting retention with downloadable or subscribed reports
Azure data location options include Australia, Canada and USA
Security and API integrations
End-to-end encrypted traffic using TLS 1.2 and X.509 certificates
Local data storage hashed using SHA-256
Azure Application Gateway, Web Application Firewall and IoT Hub architecture
Torus Exchange and Torus REST API options for approved third-party integrations
Handover History
Keep thehandover trailclear.
Access details, admin changes and reports stay attached to the vehicle handover, so managers can see who had the vehicle and what happened next.
Cabinet mappings
Connect each Torus cabinet slot to the vehicle it controls, with depot and vehicle context visible to fleet staff.
Driver ID support
Use RFID and driver identification hardware where access needs to be linked to the person collecting the vehicle.
Manual handover fallback
Keep staff-confirmed handover and return available when a site needs a practical backup process.