Simple licensing terms, pick your database.
No metering, no limits. You license the databases you actually use, for a term, under one of two grants, and the price follows the scope.
Use the data inside your own product, service and operations — fraud and risk engines, trust and safety, abuse handling, network operations, research.
Resell it forward in your own product, even directly as a database, or to power your own IP data API — for vendors and platforms whose customers consume the answer.
What each license lets you do.
A standard license ends at your internal boundaries, and a redistribution license lets you move it forward to your customers.
Tailor the license to you.
You choose the databases, how far they travel, how long you hold them and how you pay for them. Tell us the shape you want and the quote follows it.
License only what you actually use. VPN and the three proxy sets carry most of the cost to produce; hosting, CDN, Tor and relay are cheaper and usually ride along.
Databases get cheaper together. The proxy and VPN group is the common bundle, and the whole catalog is its own discounted line.
Internal use, one product surface, a whole platform, or onward publication. You pick how far the rows travel and the price follows that — never your revenue.
Annual is the default. A multi-year term fixes the price and the schema commitments for longer, and an evaluation term comes before either.
Pay the way your budget works, staged across a multi-year term if that suits you better. The term and the payment schedule are separate decisions.
Need extra fields, richer metadata, or a cut that is not in the catalog yet? We build separate databases to spec under either license.
No loose ends.
Why is nothing priced on the page?
Because two customers taking the same database can be doing completely different things with it — one scoring their own checkout, one shipping it to ten thousand downstream accounts. A list price would either overcharge the first or undercharge the second. Tell us the scope and the quote comes back inside two working days.
What exactly counts as redistribution?
Any path where our rows, or a per-address answer derived from them, reach someone outside your organization. Returning "this IP is a residential proxy" through your own API is redistribution. Declining a transaction because of it is not.
Is there a free tier or a trial key?
The databases marked Open, Tor IP, Relay IP, ASN, IP Country Flag, IP Country Currency, Anycast IP, Bogon IP and Bogon ASN, are free with an account. For the rest there is no free tier and no trial key, but there is an evaluation license: a full build, time-boxed, under NDA, with an engineer on the other end of it. It is more useful than a trial key and it does not oblige you to anything.
Do you charge per lookup or per record?
Never. You hold the database; counting how often you read a file you already own would be a strange way to price it. The license covers datasets, scope and term.
What happens at renewal if our scope changed?
We re-scope rather than auto-escalate. If you added a product surface or dropped a dataset, the next term reflects that. Price changes are notified before the renewal window, not inside it.
Can we spread the payments out?
Yes. The term is annual by default; how you pay for it is a separate question — monthly, quarterly or annual invoicing, whichever fits your budget cycle. Multi-year terms hold the price for longer and can be staged the same way.
Test the real build first.
An evaluation license puts a full current build in your hands — every row, every column, no sampling — so you can measure it against your own traffic before anyone talks about terms.