Is IP-Atlas a drop-in alternative to ipgeolocation.io?

Yes. Swap the base URL from api.ipgeolocation.io to api.ip-atlas.io, move the key from the query string to the X-API-Key header, and rename a few response fields (country_code2 to country, state_prov to region, zipcode to postal).

Why does IP-Atlas use a monthly quota instead of daily credits?

Real production traffic is spiky. Daily credits force you to size for the worst day; monthly quota lets you size for the average and burst into spikes. Overage is a flat $0.40 per thousand requests, transparent and predictable.

Is VPN and proxy detection included at the Plus tier?

Yes. Every paid plan on IP-Atlas (Plus, Pro, Business) includes VPN, proxy, and datacenter flags in the standard response. No add-on tier.

Does IP-Atlas include the MMDB database?

Yes. Plus gets monthly MMDB downloads, Pro gets weekly, Business gets daily. ipgeolocation.io sells the database as a separate product.

Compare · ipgeolocation.io

IP-Atlas vs ipgeolocation.io: every signal in one call, no add-ons.

ipgeolocation.io gates VPN/proxy detection behind paid tiers, sells the MMDB as a separate product, and meters by daily credits. IP-Atlas bundles every signal (geo + ASN + VPN/proxy/datacenter) on every paid plan, includes monthly MMDB downloads, and meters by a single monthly request quota.

Get started — free up to 2k req/mo See the migration guide

At a glance

	IP-Atlas Plus	ipgeolocation Starter
Monthly price	$19/mo	$19/mo
Included requests	150,000 / month	~150,000 / month (daily credits)
Quota window	Monthly — burst freely	Daily credits — hard reset at midnight UTC
City, region, coordinates	Included	Included
ASN, organisation	Included	Included
VPN / proxy / Tor detection	Included on every plan	Included from Starter; gated for Free
Datacenter / hosting detection	Included on every plan	Mid-tier add-on
Batch endpoint	100 IPs / call, included	Bulk API on higher tiers
MMDB self-hosted database	Monthly, included	Sold as a separate product
Free tier (commercial)	2,000 req/mo, all fields (non-commercial)	1,000 credits/day (non-commercial, no VPN/proxy)
Overage	$0.40 / 1k (transparent)	Hard cap or upgrade required

ipgeolocation.io pricing per ipgeolocation.io/pricing (2026-04-14). Quota model is daily credits, not monthly requests — see "Daily credits, not monthly requests" below.

What's different

Monthly quota, not daily credits

ipgeolocation.io's daily-credit model penalises traffic spikes — a Monday-morning batch job can blow a whole day's budget at 09:00 and 503 your users until midnight UTC. IP-Atlas meters a single monthly quota you can burst into freely. When you cross the line, you pay $0.40/1k overage, not a 24-hour outage.

Every signal at every paid tier

No "add VPN detection" upgrade, no "add Tor list" add-on, no "add residential proxy" line item. You pick a request volume; everything else is included. The same response shape on Plus, Pro, and Business.

MMDB included

If self-hosted enrichment matters — sub-millisecond lookups, no network round-trip, no leaks — every paid plan ships monthly MMDB downloads. Pro gets weekly; Business gets daily. See MMDB docs →

Daily credits, not monthly requests

This is the single biggest operational difference. With ipgeolocation.io's daily credits, you size your plan for your peak day — a single fraud-review batch or a marketing-event spike can exhaust a day's budget in minutes. With IP-Atlas's monthly quota, you size for the month and burst freely.

Example: 150,000 requests/month is roughly 5,000/day evenly distributed. A real production workload doesn't spread evenly — a 10× spike on a single day is normal. Under daily credits, you either size for 50,000/day (10× the cost) or you 503 on the spike. Under monthly quota, you spend 50,000 of your 150,000 monthly bucket on the spike day and the rest of the month rolls on.

Migrating from ipgeolocation.io

1. Swap the base URL and auth

# before — ipgeolocation.io
curl "https://api.ipgeolocation.io/ipgeo?apiKey=$KEY&ip=8.8.8.8"

# after — IP-Atlas (key moves to header)
curl https://api.ip-atlas.io/json/8.8.8.8 \
  -H "X-API-Key: $IPA_KEY"

2. Field name mapping

ipgeolocation.io field	IP-Atlas field	Notes
`ip`	`ip`	Identical
`country_code2`	`country`	ISO-2
`country_name`	`country_name`	Identical
`state_prov`	`region`	Renamed
`city`	`city`	Identical
`zipcode`	`postal`	Renamed
`latitude` / `longitude`	`latitude` / `longitude`	Identical (numeric)
`time_zone.name`	`timezone`	Flattened
`isp` / `organization`	`org`	Single org field
`asn`	`asn`	Integer
`security.is_vpn`	`is_vpn`	Boolean at top level
`security.is_proxy`	`is_proxy`	Boolean at top level
`security.is_threat`	—	Not currently exposed (roadmap)

3. Bulk migration with the batch endpoint

Backfilling? POST /v1/batch takes 100 IPs per call. 1 million IPs = 10,000 batch calls = a single Pro-month quota — one atomic preflight, order-preserving results, per-IP errors inline. See batch docs →

Frequently asked

Why monthly quota instead of daily credits?

Real production traffic is spiky — fraud reviews, marketing events, bot waves. Daily credits force you to over-provision for the worst day. Monthly quota lets you size for the average and absorb spikes. If you cross the line, overage is a flat $0.40 / 1k — predictable and uncapped (or capped on request).

How does accuracy compare?

For country, ASN, and organisation: effectively identical — both source RIR delegations and BGP feeds. For city / coordinates: competitive in major metros, improving on long-tail ranges. Methodology in the docs.

Is VPN/proxy detection accurate?

We maintain a curated list of ~50 VPN/proxy/datacenter operators plus algorithmic detection on ASN signals. False-positive rate is published per release. Residential-proxy detection (the hardest case) is on the Q3 2026 roadmap.

Does IP-Atlas support TLS / HTTPS endpoints?

All endpoints are HTTPS-only with HSTS + preload. There is no HTTP fallback.

Can I self-host?

Yes. Every paid plan includes a monthly MMDB download. Pro: weekly. Business: daily. ipgeolocation.io's MMDB is a separate product line. MMDB docs →

How long does migration take?

Under an hour for most teams: base URL swap, move the key from query string to X-API-Key header, rename two fields. Email support if you'd like a hand.

Switch in under an hour.

Monthly quota, every signal, MMDB included. $19/month for 150k requests.

Get started Read the docs