GetPassive SDK for set-top boxes

If you ship software on a set-top box or distribute firmware to OEM hardware, the GetPassive SDK adds a quiet background revenue stream that pays 80% of net revenue back to you, monthly.

Why set-top box apps are a good fit

Set-top boxes are some of the best-suited devices for passive bandwidth revenue. They are mains-powered, always-on, and connected to a stable home network. Many sit on the same router for years. There is no battery to drain, no signal to lose, and very little app churn after the user finishes initial setup.

Most set-top box vendors and software builders have limited monetization choices today. Banner ads do not fit the form factor, subscription models are often already in place for content, and many devices are commodity hardware where margin is thin. A background revenue layer that runs without any user-facing interface is a much better fit than another ad placement.

The economics are usually attractive too. Because set-top boxes contribute reliably and predictably, revenue per device tends to be more stable than on mobile, where uptime and connection quality vary by user.

How GetPassive works on set-top box

You apply for access, we review the device and distribution model, and approved partners get an SDK key. The SDK is integrated into the firmware build, an Android launcher, or a primary app depending on how your devices ship. Start in test mode, confirm the integration is reporting correctly, then promote to live mode.

On set-top boxes the SDK runs as a quiet background contributor. It is network-aware, throttles when the user is actively streaming, and pauses on low-resource events. No on-screen UI is required. Many vendors put the participation toggle into an existing settings menu so users can review or change the choice at any time.

Vendors who ship to many regions usually start with one device family in test mode, validate the reporting, then expand to the rest of the fleet.

What you keep

Set-top box partners receive 80% of net revenue, monthly, through Stripe Connect. There is no per-GB bounty and no opaque rate card. The percentage is the same for every partner, regardless of fleet size.

Revenue scales with the number of active devices, the region those devices are in, and bandwidth availability. Earnings are estimates and depend on real-world demand and uptime. Fleets in regions with strong demand tend to see steadier results than fleets in low-demand regions.

Consent model

Consent is handled inside the device’s existing Terms and Conditions. You add a plain-language clause that explains the device may use a limited amount of idle bandwidth in the background and that this revenue helps support the device or service. Users accept it the same way they accept the rest of your terms during setup.

No personal data is collected from end users by GetPassive. See the consent reference on our docs for sample wording.

FAQ

Can we integrate at the firmware level?

Yes. Many set-top box partners integrate the SDK at the firmware or launcher level rather than per app, so participation is consistent across the device.

Do we need a minimum fleet size?

No. There is no hard minimum to start a conversation. Larger fleets usually see more consistent monthly revenue because uptime averages out.

Does background contribution affect streaming?

The SDK is network-aware and backs off when the device is actively streaming, so impact on user-facing playback should be minimal on a healthy connection.

How are payouts handled?

Through Stripe Connect, monthly. You connect a Stripe account once during onboarding and earnings clear on the monthly cycle.