How GetPassive developer earnings work

App developers want to know how they get paid before they ship a new SDK. This is a plain explanation of how GetPassive calculates developer earnings, why country tiers matter, and how the live dashboard reflects what is happening on your install base.

You earn from customer demand routed through your devices

GetPassive pays developers monthly for the customer demand served by their opted-in devices. When a business customer routes traffic through the network and that traffic is fulfilled by a device in your approved app's user base, that activity contributes to your monthly earnings. The model is built on actual demand, not a per-install promise or a fixed bounty per gigabyte.

This matters because demand is what generates real revenue. A device that is online but never receives a request earns nothing. A device that is online in a region with strong demand, with healthy uptime and clean activity, earns more. The closer your install base is to where customers want IP coverage, the better the model performs for you.

Rates are set per country tier

Not every country produces the same demand. Customers pay more for IPs in some regions than others, because supply, regulation, and network quality differ. GetPassive groups countries into tiers and sets earning rates accordingly. US, UK, and EU regions sit at the top of the tier table and produce the strongest per-device earnings. Other regions earn at lower published rates.

This is an industry-standard structure. It is also why publishing a single global headline number would be misleading: a developer whose audience sits mostly in a Tier 1 country sees one set of results, and a developer whose audience sits in a lower-tier country sees another. The tiered model keeps the maths honest without forcing every developer into the same headline figure.

Earnings depend on uptime, valid activity, and demand mix

Three factors do most of the heavy lifting in any month:

• Uptime. A device that is offline cannot serve demand. Long-running apps, launchers, and TV devices tend to perform best because they stay reachable.
• Valid activity. Only clean, in-policy activity is counted. Disallowed activity, duplicates, and signals that fail quality checks are excluded before finalisation.
• Demand mix. The kind of demand routed in a given month moves the dial. Demand changes month to month based on what business customers are buying and where.

During the month, your dashboard shows estimated earnings. Estimates can move as activity, region mix, uptime, and demand change. After the period closes, earnings are reviewed and finalised. The finalised number is what you get paid.

Payouts run monthly via Stripe Connect or USDC

You choose how to get paid during onboarding. Stripe Connect is the default option and works in most supported developer regions: you connect a Stripe account, complete the required identity and tax steps, and Stripe handles the bank transfer once the monthly cycle settles. For developers outside Stripe’s supported list, GetPassive offers USDC payouts via CoinGate.

The minimum payout is $10. If your finalised earnings for a month are below the minimum, the balance carries forward to the next cycle. The console shows whether each payout is pending, processing, paid, failed, or waiting for action.

The live dashboard is the source of truth

The developer console shows accruing earnings in near real time. You can break the number down by app, by device, and by country to understand which parts of your install base are doing the work. You can also see opt-in rate, uptime, and the regional mix of your active devices so you can compare what you expected to what is actually happening.

This is the part of the model that most developers ask about. The dashboard exists so you do not have to guess. If a number changes, you can trace it. If demand falls off in a region, you can see it. If a particular app outperforms another, you know which one to invest in.

What this means for planning

For a developer modelling whether to integrate, the practical questions are: what regions does my audience live in, how long do my users keep the app running, and how clean is my install base. A small audience in a strong region with high uptime can outperform a much larger audience that sits in a low-demand region or that churns quickly.

If you want to walk through expected earnings for your specific app, sign up and we will review your category, expected rollout, and audience mix before inviting integrations.