Suggestions appear as you type. Use the up and down arrows to choose one and Enter to open it.

This page's audience our own tag's counts — open to see them
–Visits
–Page views
–Clicks to vendors
–Time on page
–Reading now
Clicks to vendors, by tool
  • –
Top countries
  • –
Devices
  • –

– · visits, page views and clicks counted by our own tag, which counts more than our checked analytics; every figure rounded down · how we count

Polyfence review

Free#7 of 17 in Geofencing Software

Free, cross-platform geofencing with mobile, IoT, REST, and self-hosted options.

8.5/10Editor score
Polyfence8.5 Visit Polyfence

Reviewed by iTechGuides Editors · Editorial team · Updated Oct 2026

Polyfence provides geofencing for mobile applications, IoT hardware, and server software. Developers can create circle or polygon zones, then detect entry, exit, and dwell events. Evaluation can run locally through mobile SDKs, on IoT hardware through an embedded C library, or on servers through a REST API. Its documented use cases include fleet and delivery operations, agriculture, perimeter security, compliance, retail, and personal safety. Small and mid-market teams building across mobile, Linux, API, or self-hosted environments are the clearest fit.

Pricing is straightforward: Polyfence is free during Early Access, and the documentation states there is no zone-count limit during that period. The product has no paid tiers to compare, so teams can assess its capabilities without a license fee. Its feature set also includes GeoJSON zone import and persistence of zone definitions and state across app restarts. Adaptive GPS polling can respond to movement, activity, zone proximity, and battery state, giving developers controls for location-heavy applications where polling behavior matters.

Deployment flexibility is a central strength. Polyfence supports cloud, self-hosted, and mobile deployment, with Linux and API access alongside iOS and Android platforms. The main trade-offs are its Early Access status, email-and-documentation support model, and the absence of web geofencing in its category specification despite a web platform listing. Teams needing a focused geofencing layer across devices and servers should consider Polyfence; organizations requiring a mature release process, broader support channels, or browser-native geofencing should evaluate alternatives.

Polyfence pros and cons

  • Where it wins
    • Circle and polygon zones with entry, exit, and dwell events
    • Mobile SDKs, embedded C, and REST API evaluation paths
    • Adaptive polling and restart persistence support field deployments
  • Where it doesn't
    • Early Access status may not fit teams seeking a mature release
    • Support channels are limited to email and documentation
    • Web platform support is listed without web geofencing capability

Polyfence fact sheet, pricing and score →

Advertiser disclosure: iTechGuides is reader-supported. Vendors can pay for top positions in our rankings and for a place on other products' pages, and we may earn a commission when you click some links. Bought places stand at the number bought; this page and our disclosure say so. Paying vendors may get a fuller, more detailed review from our editors, and that review can change their score. How we rank.

Last updated · How we research and update