i2Coalition Member Spotlight: DataImpulse

DataImpulse started in 2022, built by a team with deep data infrastructure product experience—and deep understanding of buyer needs—who wanted to deliver big service without big headaches. We connected with Oleksandra Kozyr, COO of DataImpulse, to talk about AI, compliance, and the price of sticking to your principles.

i2Coalition: Can you give us the elevator pitch for DataImpulse?
Oleksandra Kozyr: DataImpulse makes public web data accessible to everyone. We provide an ethical, first-party proxy network of over 90 million residential, mobile, and datacenter IPs across more than 195 countries. Our pay-as-you-go start from $1 per GB, no subscriptions, no expiring traffic, and 24/7 human support. 

Over 500,000 customers use DataImpulse for web scraping, AI training data, price and SERP monitoring, ad verification, and QA testing : anything that needs to see the web from a specific location, or simply needs enough IPs at volume to avoid being blocked.

i2Coalition: Has the rise of agentic AI impacted what customers are asking for?
OK: Yes, and the shift is visible from two sides. On the demand side, AI assistants have become a discovery channel for us. Developers building agents find us through them as well as through search, which is a route that did not exist two years ago.

The use cases have shifted too. Our messaging now speaks directly to AI builders: feeding models clean public web data, giving agents live web access, and monitoring how brands appear in AI-generated answers. The people reviewing us publicly are increasingly building agentic workflows rather than classic scrapers.

Technically, the shape of the request has changed. A crawler fetches a million pages overnight and cares about cost per gigabyte. An agent fetches five pages right now and cares whether all five come back. That pushes the whole category toward per-request reliability instead of cheap bandwidth, and it raises the bar on rendering JavaScript-heavy pages and passing anti-bot challenges the way a real browser does. That is where infrastructure work in this market is heading.

What about how AI is influencing your own product roadmap?
OK: It reordered our priorities more than it added items to the list. Internally, the metric we use to judge engineering work changed. It used to be pool size, which this industry has always emphasized. Now it is success rate on hard targets, with latency as the secondary concern. Pool size is a means to that end, not the headline metric.

i2Coalition: What impact do you think recent geopolitical events have had on your more recent growth?
OK: The visible effect has been on where we choose not to operate, more than on the growth curve. Part of our restricted list is simply law: Cuba, Iran, North Korea, Syria, the occupied territories of Ukraine. Any provider taking sanctions seriously does the same. Russia and Belarus are our own decision, not a sanctions requirement. We are a team with Ukrainian roots, and we were not going to sell infrastructure into those markets. They are not small markets for this product, so the choice cost us something, and we accepted it.

Where geopolitics does touch growth is trust. Buyers now ask much harder questions about who runs a proxy network and where its IP supply comes from. Two years ago that was a procurement formality. Today it decides deals.

i2Coalition: Why did your team find it important to join the i2Coalition?
OK: Two reasons, both concerning the category rather than us. The first reason is that this industry has grown up without a shared standard for how public web data is collected and how residential networks are built. Every provider describes its own practices in its own words, and a buyer has no common yardstick. That is not a sustainable place for a maturing market, and no single company can fix it alone. 

The second reason is that the rules for our category are being shaped right now, and the voices in that conversation are mostly the platforms being collected from rather than the infrastructure side. We would rather be part of that discussion than receive its conclusions. i2Coalition is the one place where the people who actually build this layer of the internet are organised, and EWDCI is where that specifically applies to how data is collected. For us, being in that room is the point.

i2Coalition: Which i2Coalition initiatives connect most deeply with your team’s ethos?
OK: EWDCI is the obvious one, and for us it is the whole reason we are here. It is the only place where how data is collected and how a residential network is sourced gets checked against a shared standard rather than described by each vendor in its own words. Our product rests on a sourcing claim, and a claim that only we can vouch for is worth less than one someone else has checked.

The second is the policy work: the briefings and the Fly-In. Scraping legality, intermediary liability and sanctions screening are not abstract questions for us, they are operational ones, and they are decided by people who mostly hear from the platforms being collected from. Seeing where those debates are heading before they land is worth the membership on its own.

i2Coalition: Where does government policy interface with your work on a daily basis?
OK: Policy touches more layers of our work than people expect from a proxy company.

Data protection is the most constant. We run a full GDPR framework: data processing agreements built on the EU Standard Contractual Clauses, set procedures for data subject requests and breach notification, and consent that is recorded rather than assumed. We store consent state for every participant, which runs to millions of records. We also hold ISO certification, which brings its own audit cycle.

Financial compliance runs on every transaction. Payments pass through fraud-pattern screening, a review queue for anything suspicious, and manual verification for high-risk cases. It is KYC and AML logic applied to a global, high-volume customer base.

Acceptable use is a governed process. Access to specific sites and ports is closed by default and opened per customer only after human review. We keep blocklists and abuse prevention running, and the ethical sourcing commitment only holds if we keep watching how the network is actually used.

So regulation is not something we react to occasionally. Data protection, payment screening, and acceptable use are built into the product and run in the background every day.