For software publishers
If they'll never convert, they can still pay their way
Most of your users will never subscribe and won’t click your ads. They still cost you infrastructure, support and traffic. AI Gateway as a fourth revenue layer earns from retained, opted-in sessions
If users keep your app open, you can earn from it
Utility & PC tools
Open in the background all day
Browsers & launchers
The window that never closes
Gaming apps
Menus, lobbies and idle time
VPN & security
Running whenever the device is
Mobile apps
The sessions users come back to
Freemium & SaaS
Where the free tier finally pays
Other · custom builds
If it holds a session, bring it
Every other layer charges your users something
on every session
Ads rely on attention. Subscriptions and in-app purchases rely on spend. Each monetization layer creates value by asking something of the user, often repeatedly, every time they open the app
What the ad layer costs
Advertising creates revenue, but additional placements can negatively affect engagement and retention
What the subscription layer misses
Only a portion of users will subscribe, leaving much of the retained audience unmonetized
What the fourth layer asks
With a single opt-in, existing sessions can generate incremental revenue without changing the user experience
Asked once, never again. It is the only layer on that list that does not re-charge the same user every session
Routes connections, not identities
No tracking identifiers, no behavioural data, no content profiling. The module carries none of it, which is why the consent screen can say plainly what is routed and who it reaches
Where this works,
and where it depends
Store policy is the first thing a publisher’s legal team asks about. Rather than a support matrix, here’s the honest shape of it, because for most platforms the answer isn’t the operating system, it’s how you distribute
Supported
Windows, macOS, Linux, iOS
The module is suitable for direct distribution and storefronts that permit disclosed background network use. Submissions should clearly explain how it operates, as that disclosure is central to review
Depends on the build
Android without Google Mobile Services - AOSP, forked Android, Fire OS and similar
The relevant constraint is typically the storefront, not the operating system. Direct Android distribution, OEM preinstalls, alternative stores, and TV platforms are each governed by different policies, so eligibility is best assessed by channel
Not currently
Any Google-certified Android build or browser extensions
The module is disabled in Google Play builds. Where Play is one of several channels, other builds can participate independently. Where it is the only channel, the module is not currently a fit.
One clear opt-in,
presented within your product
The module remains inactive until the user opts in. Consent is presented within your product with clear information on routing, recipients, and opt-out controls. Users can withdraw consent at any time, from the same location
Installed
Present, dormant, no network activity
Opted in
Routes a capped share of unused capacity during sessions
Withdrawn
Returns to dormant
Fixed by us
The ceiling
- What is routed
- Who it reaches
- That opting out works
- That it keeps working
Yours to design
The offer
An ad-free tier for opted-in users, trading a layer you are already fighting for one that does not interrupt
Feature access that would otherwise sit behind a paywall
Storage, exports or limits raised for participants
The rule that keeps it clean: opting in should add something. Declining should cost nothing the user would otherwise have had. A screen offering a genuine exchange converts better than one that argues, and it stays defensible under scrutiny.
Live in production with real publishers
Shipping inside utility tools, freemium apps and mid-tier publishers — paying out monthly, surviving quarterly store-policy updates, and showing up in retention reports as a non-event.
100M+
Devices on the network you join
190+
Countries
+60%
Lowest blended ARPU lift measured across partners
3 of 5
Top LLM labs among buyers
How a rollout runs
Ship the module in your build, dormant. No change to your release process.
Users opt in through consent surfaced in your UI, in whatever form you’ve designed. Participation builds across the release; it doesn’t switch on at once.
Steady state is the opted-in share routing during sessions, with the dashboard reporting throughput, consent rate and revenue per platform – each traceable to inputs you can check.
Retention curves don't move
Across partners, the module has not produced a measurable change in retention or session length.
Store ratings don't move
No partner has attributed a ratings change to the integration.
The revenue comes from users who weren't paying
The lift concentrates in the free tier – users who don’t convert and don’t engage with ads.
A real module, not a wrapper
Native libraries for every major app runtime. Drops into your existing build, asks for consent through your UI, runs in the background of opted-in sessions. Most partners ship within a single release cycle.
Swift · Kotlin · C++ · Electron · Unity · Unreal
Built to survive compliance review
ISO/IEC 27001 · Penetration testing · EWDCI
Network monetization carries category baggage. The product is built for partners whose legal, security and brand teams will look hard at it — consent integrity, independent penetration testing, audited enforcement, and KYC on every commercial counterparty.
The demand end is contracted, not open market
Routed traffic terminates with vetted counterparties. Since 2021, demand has been served through an exclusive partnership with Oxylabs — a Warburg Pincus-backed infrastructure company whose supplier standards your traffic is held to.
Stop choosing between revenue and retention
Tell us about your product: category, DAU, platforms, region mix. A person reviews it and comes back to you.
