Decide where and when devices can be trusted
Define go and no-go zones for company devices and set off-grid time limits. When a device crosses a boundary or stays dark too long, Tether can notify your team or trigger a Device Containment action automatically.
with entry and exit rules
limits on time off the grid
enforcement, online or not
When device location becomes a security or contractual issue
Your organization sets rules for where employees can work. Your customers restrict where their data can be. Governments and industries restrict where devices can travel. And employees relocate without telling anyone. Rules like these are routinely broken without anyone noticing.
Drift produces no alert
A device that travels outside its approved region keeps checking in normally. Nothing in a standard fleet view distinguishes it from a device sitting at a desk.
Discovery happens after the fact
By the time anyone reviews location history, the window to act has usually closed. The device is gone, the data has been accessed, or the reporting deadline has passed.
Dark devices are beyond reach
A device that stops checking in can't be told to do anything. Whether it's offline by accident or by design, it needs to be tracked down or disabled, and a remote command can't reach it. Tether enforces the rule on the device itself.
Real-time detection, automatic action
A geofence breach or an expired curfew is a trigger, not just a log entry. Tether runs the action you preconfigured: notify your team, lock the device, or contain the data. No analyst has to step in, and curfews fire on the device without a network connection.
Zones with entry and exit conditions
Draw the areas a group of devices is expected to operate in — a campus, a metro, a country, an operating region — and state what should happen on entry or exit.The console reports which devices are inside each zone right now, so the policy doubles as an inventory of where your fleet actually is.
A limit on how long a device may stay dark
A device that stops reporting is the hardest case: you cannot see it, and you cannot send it a command. A curfew turns that silence into the trigger.
The rule is evaluated on the endpoint, so keeping a device offline to avoid a response is what causes the response to fire.
The rules teams write first
Every fleet has a handful of movements that are never legitimate. These are the ones customers turn on in the first week.
Device Geofencing and Curfews FAQ
No. The curfew threshold is evaluated on the device. If the agent has been unable to check in for longer than your limit, the configured RemoteKill action executes locally, with or without a network connection.
Rules are set per group, and each rule chooses its own response. Most teams start with notify-only on exit conditions, keep lockouts for embargoed countries and curfew expiry, and grant travel exceptions ahead of time.
That attempt is itself a signal. Tether compares reported position against network egress country and connection reputation, so a mismatch raises an alert rather than passing silently as a valid location.
No. Zones and country policy are useful as reporting alone — they tell you where your fleet actually operates, which is often the first time that question has a documented answer.
Geofencing turns location into a security policy. When a laptop leaves its approved zone, connects from a denied country or hides behind a VPN, Tether can alert your team or contain the device automatically, before data is exposed.
Geofences alone can be spoofed with a VPN or defeated by keeping a device offline. Tether adds network-egress checks and Offline Curfew to close both gaps.
Yes. Tether combines Wi-Fi, GPS, cellular and IP location, so geofences work indoors and on hardware without a GPS radio.
Get started
Stand up a proof-of-concept within minutes, or book a demo with one of our IT experts.