How it works.

Two apps, one subscription, and one decision about where your data lives. Every screen below is an unretouched capture of the shipping build, on both machines. The iPhone frames used to be renderings and said so; they are photographs now.

From nothing to an auditable register

  1. 01

    Set it up on whichever device you are holding

    Name the organisation, answer the regulated-data and framework questions, and choose where the register lives. You can do all of that from the iPhone with no Mac in the building, or from the Mac. Neither device is an accessory to the other.

  2. 02

    Choose where the register lives, once

    This Mac and my devices, or Starkive Cloud. It is a decision you make at setup with the consequences written next to it, and it governs every sync afterwards. It is never worked out at runtime, because “it depends what was reachable” is not an answer you can give an auditor.

  3. 03

    Bring in what you already have

    Import a spreadsheet and the columns are matched for you, including ones you invented, which become typed custom fields. Or connect Intune, Entra, Jamf Pro or Okta and let devices sync straight in. Every integration shows exactly what it maps to before you connect it.

  4. 04

    Work it from the desk or from the rack

    Lifecycle, contracts, licences, compliance and reporting are desk work on the Mac. Standing at a machine, the phone reads the asset tag, cross-checks the serial by barcode and OCR, and records custody on the spot, whether or not the Mac is awake.

  5. 05

    Let the two machines agree, or do not

    On a local workspace the Mac and the phone sync straight to each other over your own network, on TLS with a pinned certificate. Whether the Mac answers on that network at all is a switch that starts off, and turning it off closes the port rather than hiding the button. On a cloud workspace they agree without sharing a network, and the fields that matter most are encrypted before they leave the device.

  6. 06

    Hand the auditor a pack, not a spreadsheet

    Your inventory is mapped to 66 controls across 12 standards, with 15 evidence reports kept ready. When someone asks, you generate one Audit Evidence Pack: full inventory, audit trail, sanitization certificates and worklists, every artifact mapped to its control.

On the Mac

The larger of the two builds: every area, the full compliance surface, and anything that reads the whole register at once.

The Manifest home screen on macOS: what needs attention, the request queue, and what is running low
The day's manifest: what is asked of you, before you go looking for it.
The Manifest assets table with customisable columns and filters
Every device from purchase to retirement, with columns you choose.
The Manifest compliance portal showing frameworks, controls, the audit evidence pack and what the register is missing
Frameworks derived from your answers, the pack ready, and the gaps named.
A Studio dashboard on macOS with a status donut, assets by type and spend over time
Ask for a dashboard in plain English. It is built on the Mac, by the Mac.
The Lifecycle screen on macOS: composition, the pipeline from on-order to disposed, and what needs attention
On order to disposed, and the three ways a machine gets stuck.

On the iPhone

A smaller build of the same product, not a scanner for the Mac. It holds the register itself, so it works in a basement with no signal and catches up later.

Starkive Manifest on iPhone: 500 assets held on this device, four rooms past their sweep cadence, and a fleet worth $1,112,279
What is asked of you, on the device in your hand.
The Manifest asset list on iPhone: 500 records with tag, model, holder, location and status
The register itself, searchable by tag, serial, model or person.
A Manifest asset record on iPhone, grouped into identity and assignment, with Verify and Flag ceremonies and a warranty gauge
One machine, grouped the way you check it.
The People tab on iPhone, listing sixteen people no longer in the directory who are still holding kit
Sixteen leavers, still holding kit. Standing, not a report you run.
Settings on iPhone: the register reads On this iPhone and this network reads Not allowed
Where the register lives, and whether it answers on the network. Two rows.

These are captures, not renderings. Taken from a standalone register of 500 assets on an iPhone with no Mac and no account anywhere near it, which is the route a phone-only customer actually takes. Scan is the one screen missing, because a simulator has no camera and a blank viewfinder would tell you nothing.

What needs the Mac

Some work genuinely wants the bigger screen: the full compliance surface, and anything that reads the whole database at once. Those screens say so on the phone rather than pretending otherwise. The phone has capability the Mac does not, too: a camera in the room with the hardware, an NFC radio that writes and reads asset tags, a sweep you can start from the Action Button, and a Live Activity that keeps the count in the Dynamic Island while you walk the aisle.

Next: what it costs or the guides.