Common questions

Yes. Forager was designed for regulated environments from day one — not retrofitted for compliance after the fact. MAC addresses are hashed before storage so raw device identifiers are never retained. Row-Level Security enforces strict tenant isolation so no user or administrator can access data outside their own organization. No personally identifiable information is collected beyond the asset records your organization explicitly defines. Every update carries a full audit trail: who confirmed it, when, and what RF evidence supported the match. Auditable exports are available on demand for compliance reviews.

Zero trust in Forager means the system never assumes data is safe — it enforces protection at every layer. Device data is hashed before it leaves the mobile app. The cloud backend enforces Row-Level Security so each tenant's records are completely isolated, even within a shared infrastructure. No data is transmitted in plaintext. Access is governed by role and organization at the database level, not just the application layer. This posture was intentional from the start because our target customers — healthcare providers, financial institutions — operate in environments where a data exposure isn't just a liability, it's a regulatory event.

Enrollment is straightforward: set up your organization in Forager Cloud, establish your locations (facilities, zones, rooms), and provision your users. That's it. Field technicians can begin snapshotting assets on day one — no hardware purchases required, no AP surveys, no network changes. Forager reads the RF signals already present in your facility. Asset Beacons, Forager Agent for smart devices, and CMDB integrations like ServiceNow are all available when your team is ready to add them — none are prerequisites to getting started.

Whenever you're ready — CMDB integration is not a prerequisite to using Forager. Many organizations start snapshotting immediately and connect their ServiceNow instance or other CMDB once the pilot has proven value and the integration work is scheduled. Forager Cloud exposes a PostgREST API, making it straightforward to push asset location updates to external systems on a schedule or in response to events. We can work with your team on the integration design during or after the pilot.

Asset Beacons are small, battery-powered devices that you attach directly to the equipment you want to track — an anesthesia cart, an IV pump, a case of calibration tools. They broadcast a continuous BLE signal but have no network connection of their own. When any Forager-equipped device passes nearby, it picks up the beacon's signal and can report the asset's location to the cloud. The beacon never needs to be configured again after initial pairing. Attach it and forget it.

Forager Agent is a lightweight utility for smart devices — laptops, iPads, iPhones — that turns the device itself into a self-reporting asset. Install it, set a check-in schedule, and the device automatically reports its own location to the Forager Cloud without any action from a field tech. It's ideal for tracking shared tablets, laptops, AV equipment, and any other smart device that's already running an OS.

Forager Mobile runs on standard Android devices with Wi-Fi and BLE radios — the phones your staff already carry. No proprietary hardware or dedicated scanners needed. Asset Beacons and Forager Agent are optional additions for equipment that benefits from automatic check-ins without active scanning.

Forager supports configurable MAC address hashing and rotation so raw device identifiers are never stored in plain text. We don't collect cellular identifiers or personal data beyond what your organization explicitly records for an asset. Explainable RF scoring shows exactly what signals were used to make a match, enabling audits without exposing raw data.

Yes. Forager Mobile queues captures and updates locally and syncs them reliably when connectivity is restored. Operators can complete full workflows in areas with poor or no coverage — basement equipment rooms, shielded areas, loading docks — without losing any work.

Most asset location updates complete in ≤ 2 taps from the Forage screen — often under five seconds — thanks to passive RF pre-matching and one-tap confirm. If the asset has a Beacon attached or runs the Forager Agent, it may have already reported itself in before the tech even opens the app.

A 90-day engagement across 3–5 zones in one facility. We baseline your current Mean Time-to-Locate (MTTL) and update adherence, instrument Forager with your asset types and zones, and measure locate-in-two-minutes throughout the pilot. At the end you get a full data package to make the case for a facility-wide rollout.

Exports are available in JSON and HTML on demand, suitable for audits, CMDB feeds, and BI tools. The Forager Cloud backend uses PostgREST, so teams with engineering resources can query it directly. Row-Level Security keeps each organization's data fully isolated in multi-tenant deployments.