Revenue and payouts
GetPassive uses a tiered earnings model. Approved developers earn from customer demand served by their devices, with rates set by country tier.
How earnings are computed
Earnings are based on the supply your approved app installs contribute: the number of eligible active devices, how long each device stays online and available, connection reliability, IP variety, and the country tier each device sits in. The calculation considers verified device activity, quality checks, regional demand, platform rules, and invalid activity removed during review. Earnings are not calculated from the volume of data transferred.
Monthly payout cadence
Payouts are processed monthly through Stripe Connect. Your console shows pending earnings during the month, finalized earnings after review, and payout status once the transfer is sent.
| Field | Meaning |
|---|---|
| Estimated earnings | A live estimate for the current month. |
| Finalized earnings | The reviewed amount eligible for payout. |
| Active devices | Approved devices with recent valid SDK activity. |
| Active device-days | Eligible online device-days — the primary input to the earnings calculation. |
| Bandwidth activity | Aggregated data volume served by your devices. Reported for visibility only; it is not an input to the earnings calculation. |
| Payout status | Pending, processing, paid, failed, or action required. |
No fixed public rates
We do not publish fixed RPM or per-device promises because earnings depend on real activity, region mix, uptime, quality, and demand.
Last updated June 11, 2026