Personalise, route, and gate your product by location from the first request — no prompt, no friction.
Great SaaS feels local from the first click. IP geolocation gives you country, timezone, and region up front — so language, pricing, routing, and compliance all default to the right thing, and the user can still override anything.
From day-one personalisation to routing and compliance.
Detect country and timezone to set the right language, date format, units, and local contact details before the user touches a setting.
New user → 213.55.x.x
country: Germany · timezone: Europe/Berlin → de-DE UI, 24h clock, €
Use country and continent to send each user to the closest endpoint or data region, trimming latency without asking them to pick a server.
Request → 54.66.x.x
continent: Oceania → routed to the AU region endpoint
Tag sign-ups, sessions, and events with country and ASN so product and growth teams can see where usage actually comes from.
Event → 102.89.x.x
country: Nigeria · asn_org: MTN → attributed to NG / mobile cohort
Show region-appropriate plans, currencies, and feature availability, and keep beta or regulated features scoped to the right markets.
Pricing view → 102.0.x.x
country: South Africa · currency: ZAR → ZAR plans, region feature set
Know which jurisdiction a user operates from to apply the correct data-handling, retention, and consent rules — EU-status included out of the box.
Session → 92.40.x.x
is_in_eu: true → EU data-residency path + consent handling
Every one of these ships in the standard response — no add-ons, no tiers.
country / region Locale, pricing, feature gating, compliance timezone Correct times, schedules, and formatting continent Nearest-region routing decisions currency Localised plan and billing display is_in_eu Data-residency and consent rules connection (ASN) Usage analytics by network / carrier IP geolocation gives you a sensible default on the very first load — correct language, currency, timezone, and region — with no prompt and no round-trip. Users can still override it, but most never need to, which removes friction from onboarding.
Country and continent are highly reliable, which is what routing and residency decisions depend on. For anything legally binding, use it as the fast first signal and confirm with the user's account settings or billing country of record.
No. It's a single call with a median response under 50ms, typically done once per session or at sign-up, then cached against the account — negligible overhead for a large personalisation and routing payoff.
Free tier: 2,000 lookups/day, no card. Paid plans from $2.50/month. One call per session, under 50ms median response.