Skip to content

Verified presence, in real time for people, robots and drones

Axborg tracks presence to the boundary.

Not just on site or off site. Axborg knows exactly which space someone or something is in, the moment it changes, from a whole building down to a single room.

One verified record your systems can read and act on.

Built for machines first

Most check-in systems were built for people and had machines bolted on later. Axborg starts the other way around. A robot authenticates and checks itself in through the API. A drone reports its entry and exit on launch and recovery. A fleet of autonomous units crosses from one cell to the next and every crossing is recorded, verified, and timestamped. No badge, no turnstile, no human in the loop. Just a clean, signed event that says which machine is where, and when it got there.

API-native check-in

Machines authenticate with a signed key and check themselves in and out. No hardware to mount, no reader to wire.

Batch ingestion

A fleet reports thousands of movements at once and each one lands as its own verified event.

One record for people and machines

A robot and a cleaner checking into the same site write to the same presence record, in the same shape, read the same way.

Night shift at a logistics Depot: forty robots check in over the API while the human crew checks in by passkey. Neither queue touches the other. One record holds both.

One verified record, read by everything

A check-in is only useful if the rest of your stack can trust it and act on it. Axborg holds one live record of who and what is present, verified at the moment of entry and updated the moment they leave. Your fleet manager reads it to know which robots are in which cells. Your access system reads it and acts when someone is cleared. Your dashboards, your compliance logs, your automations all read the same source. Axborg does not try to be your fleet manager or your access controller. It is the record they all rely on, exposed through one API, honest about what it knows and when it knew it.

A facility manager opens one view and sees the morning cleaning crew, the cleaning robots working the same floors, and the inspection drone that surveyed the roof at 06:40. One record. No stitching.

How verification works ↓

One hierarchy, any space, every in and out

Axborg models any operation as a hierarchy: Organization, Location, Site, Unit. Check-in and check-out happen at any level, so the same platform describes a warehouse of zones, a hive of cells, a hotel of rooms, or a worksite of areas without changing shape.

The worldSiteUnitWho checks in and out
Robot fleetthe flooreach cell or dockrobots crossing cell to cell, read by the fleet manager
Warehousethe warehouseeach zoneautonomous units entering and leaving zones
Drone operationthe siteeach pad or airspace boxdrones on launch and recovery
Hotelthe hoteleach roomcleaning crews, room by room
Worksitethe siteeach areacrews, contractors, and machines

One system. One hierarchy. Any actor. Every in and out.

Presence your systems subscribe to — and act on

Verified presence flows out the way it flows in: machine-readable, in real time. Axborg exposes a Presence API and a live event stream, so the systems you build — including your agents and automation — can read what's on site and act on it, without a human polling a dashboard.

Presence API

Read presence, check resources in and out, and manage Sites and Units programmatically.

Real-time event stream

Subscribe to check-in and check-out events as they happen. A verified check-out at a client Site can trigger your next dispatch the moment it lands.

Bring your own systems

Feed verified presence into your Salesforce, WMS, EHS, or payroll systems — you build the integration, on your terms.

A workforce-orchestration agent subscribes to the stream. A verified check-out event arrives; the agent assigns the next job. Nobody refreshed a screen.

Verified before it's recorded — evidence, not an honour system

Software acting on presence data can't afford maybes — and neither can your auditors. Axborg checks every event before it counts.

Signed QR codes

Every QR code is cryptographically signed. A scan proves the code came from your Site — a screenshot or a copy doesn't.

Single-use tokens

Check-in tokens are single-use and expire. A captured code can't be replayed to fake a presence event.

Location and assignment checks

Each check-in is verified against the expected location and the person or resource's assignment before it's recorded.

Where teams put this to work ↓

Where Axborg runs

For people, machines, or both — one verified record.

Robot fleets

Every robot checks in and out of every cell, dock, and zone. Your fleet manager reads Axborg to know the live state of the floor, verified and in one place.

Drone operations

Drones check in on launch and check out on recovery. Every sortie leaves a signed record of where it went and when.

Security

People and patrols check in across sites and units. One verified record of who was present, when, and where, ready for audit.

Cleaning

Crews check in room by room and site by site. Proof of presence per unit, without paperwork.

Construction

Crews, contractors, and machines check in across a worksite of areas. One record of everyone and everything on site.

Healthcare

Staff and equipment check in across a building of rooms and zones. A live, verified map of presence where it matters most.

Built for machine-scale traffic. Fails safe, never silent.

Fleets don't check in one at a time. Axborg is designed for a check-in scale target of up to 40 million — and engineered to degrade gracefully under load, never to drop data quietly.

Queued, never blocking

Check-ins are accepted and queued the moment they arrive. A burst of traffic never blocks the people or machines checking in.

Indexed for instant lookups

“Who is on site now” runs on indexed keys and stays fast as your data grows.

Fails safe under load

A durable write path and graceful degradation: the system sheds load rather than dropping presence data.

Frequently asked questions

What is Axborg?
Axborg is a unified, verified presence layer. People, robots, and drones check in and out of any space you run, on one real-time record your other systems read and act on.
Does Axborg use AI?
No. Axborg is a presence layer that machines and their software agents consume through the API. It is built to be read by automated systems, not to be one.
Is Axborg a fleet manager?
No. Your fleet manager reads Axborg. Axborg holds the verified record of which machine is in which cell and when it crossed. Your fleet manager, WMS, or hive controller uses that record to make its decisions.
Is Axborg an access-control system?
Axborg does more. It is the verified check-in record for people and machines across every space, and an authorized check-in can drive your access control the moment someone is cleared.
What scale is Axborg built for?
Axborg is built for a concurrent check-in scale target of up to 40 million across people and machines. That is the architecture it is designed around.
Which markets does Axborg serve?
Denmark, Norway, Sweden, Germany, and the United States, each in its local language.

See Axborg on your sites

Book a demo and we'll show you verified presence for your people, your machines, and the systems that act on them.