Skip to main content
Help Centre Support Contact
Partners
Create Free Account
Create Free Account Book a Demo

For IoT & Hardware Companies

Your Hardware Opens the Gate. We Know Who Is Cleared.

You make the readers, turnstiles, key cabinets, and sensors on site. ComplyFlow holds whether each Worker and each plant item is cleared, so your device acts on one verified answer.

Become a Partner See the Connectors
A hardware engineer kneels beside an open turnstile control cabinet at a data centre entry, checking a tablet while a site security lead watches the reader panel ISO 27001 since 2019. Hosted on AWS in Australia. Native access and key connectors.

What Your Device Gains

One Answer at the Scan, Kept Current for You.

Your device is good at reading a card or a face. Whether the person holding it has a current induction, licence, and insurance is the record ComplyFlow keeps.

Connected Today

KeyWatcher Australia, Unicard, and Torus connect natively, built and maintained by ComplyFlow for each customer.

The Worker’s Status

Induction, licences, insurance, and permit checked against the person’s record, so your device reads a status rather than a spreadsheet.

The Plant Item’s Status

Plant and vehicle records, with their sites and documents, readable for equipment access and telematics.

An Open API for Every Other Device

Documented REST endpoints with a test environment, so your firmware or cloud can read the record and add inspections from the field.

How It Fits on Site

Your Device at the Door. Our Record Behind It.

Three places the join shows: the scan at reception, the live list of who is inside, and the plant item in the yard.

The Scan Reads the Record.

At the scan, the person’s induction, licences, insurance, and permit are read against their record. Anyone short is flagged on the spot. Where the site is set up that way, your hardware acts on the answer.

  • Read at the scan
  • Flagged on the spot
  • Where the site is set up that way, access follows status

Site Access

Who Is Inside, Right Now.

Everyone signed in across every site, with the company they work for and whether the gate cleared them. The sign-in book is readable by other systems, including yours.

  • Live list by site
  • Company, category, and status
  • Sign-in book readable through the API

Site Access

The Plant Item Has Its Papers.

Each plant item carries the documents its category requires, and the operator’s ticket sits on the same record. Telematics and equipment access can read both.

  • Documents set by plant category
  • The operator’s ticket on the same record
  • Inspections added through the API

Plant & Equipment

What You Make

Devices That Act on the Answer.

If your device decides who or what goes through, the record can tell it who is cleared.

Access Control & Turnstiles

Readers and barriers that let a cleared Worker through.

See how

Key Cabinets

Keys released to the person whose status is current.

See how

ID & Access Cards

A card tied to the person, not just the company.

See how

Kiosks & Tablets

Sign-in at reception on a tablet, no special hardware.

See how

Telematics & Plant

Equipment access that reads the operator’s ticket.

See how

Sensors & Wearables

Field data that adds inspections or reads incident history.

See how

See All Integrations

How to Start

From First Call to a Device That Reads the Record.

Every step is with a person on the ComplyFlow team, and nothing reaches a customer until both of us have agreed it.

  1. 1 A 20-minute call

    Your device, where it is installed, and the decision it makes at the door or in the yard.

  2. 2 We map the join

    Whether a native connector exists, or which endpoints your firmware or cloud should read.

  3. 3 Agreed in writing

    What each side builds and supports, and how we work together, before anything goes to a customer.

  4. 4 Tested on a real site

    A customer site you both serve, with the test environment first and our team on the call.

Worth Reading

Guides Your Customers Already Read.

All posts

Become a Partner

Tell Us About Your Device.

A short form, read by a person on the team setting the partner program up. Say what you make, where it is installed, and whether ComplyFlow already connects to it.

  • Whether a connector or the REST API fits
  • What your device would read at the scan
  • Who on our team you would work with
All Partner Types

Become a Partner

Start the message box with 'Hardware', so it reaches the right person.

Send Message

The form loads from HubSpot. If it does not appear, the button takes you to the contact page.

Questions

Questions Hardware Companies Ask First.

Does ComplyFlow make access hardware?

No. Physical barriers are not part of the product. ComplyFlow holds whether the person or the plant item is cleared, and your hardware acts on that answer where the site is set up that way.

Is our system already connected?

If it is listed as a native connector on the integrations page, yes. Today that is KeyWatcher Australia, Unicard, and Torus for access and keys. Every other device connects through the REST API, and we say so plainly rather than call it a connector.

What can our device read?

Worker compliance, the site sign-in book, and plant and vehicle records with their sites, through the endpoints in the API documentation. Inspections can be added through the API from the field.

Does a site need special hardware to sign people in?

No. A QR code on a post, a tablet at reception as a kiosk, or the app all work, as the site access page shows. Your hardware is for the sites that want the door to act on the answer.

Where is the data hosted?

Data is hosted on AWS in Australia. ComplyFlow has held ISO 27001 since 2019, and the security page sets out the rest.

Your Device Decides. Let It Decide on a Verified Record.

Tell us what you make and where it is installed. The integrations page shows what connects today.

Become a Partner See the Connectors
  • ISO 27001
  • Hosted on AWS
  • Native Access Connectors
  • REST API