Octet vs GeoComply

Comparison

Octet vs GeoComply.

GeoComply’s servers analyse data collected on the user’s device and return a decision, while Octet’s check runs on the phone and returns a yes or no signed in the phone’s hardware, which anyone can verify offline.

Both answer the same question: is this user where they need to be? They answer it in different places, and that changes what you get back.

	Octet	GeoComply
Where the proof is built	On the phone, at the moment of the check, from satellites, the cell network, motion sensors and other on-device signals	GPS, Wi-Fi, cellular and IP data collected on the device and analysed by GeoComply’s servers (source)
VPNs and proxies	Users can leave the VPN on. The verdict does not depend on the IP address	Detected and blocked. Users turn the VPN off to continue (operator help page)
What you get back	A yes or no, signed by the phone’s secure hardware	A location decision from GeoComply
Checking it afterwards	Anyone, at any later date, with open-source octet-verify. It shows whether the proof was changed after it was signed	GeoComply does not publish a way for a third party to check a decision independently
What leaves the device	The answer. No coordinates	Location and device data
Precision	Answers for the region you define, from a country down to a building	“Within meters,” by GeoComply’s own account (source)
Pricing	Usage-based and published at octetproof.com/pricing	Sales contract. Pricing is not published
Friction for users	None for country checks in the browser: no permission, no prompt. In an app, country and state checks with no permission are available on request. The public SDK asks for location permission once	Location services on, VPN off, and an install on desktop (operator help page)
Dependence on a live service	None. Proofs verify offline, with no call to Octet	Every check runs through GeoComply’s servers

GeoComply is described from its own published material and, where marked, an operator’s help page for installing it. Checked 16 October 2026. Trademarks belong to their owners.

What that means in practice

Nothing to install beyond your app. The check runs passively inside the app your users already have.
No precise location to hold. The verdict leaves the phone and the coordinates do not, so neither you nor Octet stores where your users were.
Proof made where the event happens, on the device being checked. It is built at the moment of the check, so the data it rests on never travels to a server first. Afterwards, anyone can run the open-source octet-verify on it, at any later date, to see whether it was changed. See proof of location.
Your rules, in plain language. You bring your business rule to Magistrate, Octet’s policy engine, and write it in plain language, such as “withdrawals only from the UK, never from an OFAC-sanctioned region.” One click pushes it to the SDK. On each check, the SDK returns a signed verdict against that rule (for example: in the UK, not in an OFAC-sanctioned region), and your app determines the action.

What this does not establish

This is not a claim that Octet is more accurate than GeoComply. No vendor’s accuracy is externally audited, Octet’s included. And an Octet verdict answers for a device, not a person: it belongs alongside identity verification, not in place of it.