Frequently asked questions.

A real-time location system that runs UWB and BLE through the same anchors and tags, on one platform and one map. Start with what you need today, then add zones, BLE assets or Pick-to-Light later, without re-cabling or a second system.

RFID tells you a tag passed a fixed reader. An RTLS follows assets and people live across the whole site, raises alerts on where they are, and lights up the tag you select (Pick-to-Light, on tags with an LED).

With UWB TDoA, under 50 cm in industrial or complex environments and under 20 cm in controlled ones. BLE gives a zone-level position, 2 to 5 m, and BLE angle-of-arrival anchors reach 0.5 to 2 m under high ceilings. To find one item, Precision Finding guides you to within about 10 cm through an iOS app.

Up to ten times a second: the location engine computes positions every 100 ms. A moving UWB tag reports six to seven times a second, BLE about once a second, and a tag goes quiet when its asset stops. The rate is set per site.

UWB where a process needs a precise position: work orders at a workstation, anti-collision zones. BLE for zone-level presence across large, multi-floor buildings. Most sites use both, each where it pays. For outdoor or wide-area tracking, Ubudu offers compatible LoRaWAN and GPS trackers from partners.

AI agents that work on your live location data. Ask the RTLS AI Assistant where things are, in plain language. The Flow, Safety and Asset agents watch for congestion, collision risks and idle equipment.

No. Describe what you need and the agents build it: a rule (Rule Agent), a script (Script Agent) or a dashboard (Dashboard Copilot). Agents can also act, from an alert to a tag lighting up.

Your choice: a cloud model, or an open-weight model running on your own infrastructure.

Two ways: off-the-shelf Plug & Play kits you self-install, and tailor-made deployments scoped with our team.

The return comes from less time spent searching and better use of equipment, typically within 6 months to 1.5 years.

On the benefits side, evaluate the time spent searching for assets and the productivity gains, and set those KPIs early so you can weigh them against your budget. On the cost side, account for investment costs (devices, anchors, installation, integration with your systems, and licences and servers for an on-premise deployment) and recurring costs (device maintenance, licence maintenance or SaaS fees, and support).

Your accuracy and update-rate requirements drive the architecture, the investment and the project's complexity, so size them before you buy.