For hardware manufacturers
If it's still online, it's still an asset
Your fleet earned you revenue once. One firmware module makes it recurring without touching the user experience, the BOM, or your warranty obligations
If it's always on, it can always earn
Router · modem · mesh
The connection every other device runs through
Set-top · streaming
One device, a household’s whole evening
NAS · home server · mini PC
Built to stay on, by definition
Mobile device (OEM)
Your fleet, from the factory forward
Smartphone · tablet
Already in hands, reachable by update
Other · custom builds
If it’s connected and stays on, bring it
The device outlives the sale
Every unit you ship has two lifetimes. The commercial one ends at checkout. The operational one runs for years
Day 0 - revenue lands
The margin is booked. It’s thin, it was set by a market that competes on specs and price, and it’s final. There’s no lever left in the BOM
Month 18 - the line is flat
Still online most of the day. Still receiving OTA updates and security patches. Still generating support tickets. Revenue from this unit since checkout: nothing
Year 4 - costs compound
Support and firmware engineering scale with fleet size. They protect revenue already booked; they create none. The fleet is an operating cost that used to be a sale
A routing module changes which lifetime you get paid for. It runs at the firmware layer, not the unit-economics layer — no change to component cost, retail price, or competitive positioning. Revenue accrues per opted-in device, for as long as that device stays online
This isn't only about the next production run
The module goes into devices you haven’t built yet. It also goes into devices you shipped years ago, by firmware update. The installed base you currently only spend money on — patches, support, warranty — is addressable now, not from the next hardware cycle onward
Ships dormant
Activates only when the owner says yes
The module is present in firmware and does nothing. No routing, no connection, no traffic until the device owner is shown a consent screen and opts in. A device that is never opted in never participates, for its whole operational life. Opt-out stays available afterwards, in the same place, permanently
Fixed by us
The ceiling
- What is routed
- Who it reaches
- That opting out works
- That it keeps working
Yours to design
The offer
Extended warranty on opted-in devices
Subscription credit — for products where recurring service revenue already outweighs hardware margin, the most direct lever available
Feature access that would otherwise sit behind a tier
The rule that keeps this clean: opting in should add something. Declining should cost nothing the customer would otherwise have had. A consent screen that offers a genuine exchange converts better than one that argues — and it stays defensible, which a pressured screen does not.
The infrastructure is already shipping
Live across CTV, IoT, smart home and embedded categories – audited fleets, paying out
100M+
Devices on the network you join
190+
Countries
7 yrs
Operating the network
3 of 5
Top LLM labs among buyers
How a rollout runs
Firmware ships with the module included and dormant – no change to factory test or the OTA pipeline.
Owners opt in through consent surfaced in your UI, in whatever form you’ve designed. Activation builds across the rollout; it doesn’t switch on at once.
Steady state is the opted-in share routing continuously, with the dashboard reporting throughput, consent rate and revenue per device class — each traceable to inputs you can check.
Case study · Tier-1 CTV manufacturer
VP, Connected Platforms
Anonymized at partner's request
Year 1 net revenue
A firmware module, not a wrapper
A single static library that drops into your build system. No background services, no init at boot, no impact on factory test or OTA. Teams with engineering capacity ready have gone from kickoff to shipping build inside a sprint.
C · C++ · Rust · AOSP HAL · Linux / embedded · RTOS · Custom builds on request
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
Your installed base is already online. Let's see what it's worth
Tell us about your fleet: device categories, installed base, region mix, platforms. A person reviews it and comes back to you.
