Pi nebenbei
More providers

TraffMonetizer and Pawns.app on a Raspberry Pi

These two are more pleasant on a Pi than Honeygain because they ship genuine arm64 images. No translation layer is needed, and with TraffMonetizer not even an account password ends up on the device.

Requirement: Docker

Both services run in containers. If Docker is still missing:

Install Docker
curl -fsSL https://get.docker.com | sh
sudo usermod -aG docker $USER
newgrp docker

No translation layer needed Unlike Honeygain, both providers ship images for arm64. The binfmt detour is unnecessary and the container starts straight away.

TraffMonetizer: token-based login

Instead of an email and password you supply a token from your dashboard. No account password ends up on the Pi – if somebody gains access to the device later, that is a noticeable difference.

Start TraffMonetizer
docker run -d --name tm \
  --restart unless-stopped \
  traffmonetizer/cli_v2:arm64v8 \
  start accept \
  --token [YOUR_TRAFFMONETIZER_TOKEN] \
  --device-name [NAME_FOR_THE_PI]

You will find the token in the dashboard after signing up, under “Your application token”. Copy it and paste it above.

  • Payout from 10 US dollars
  • Several devices possible, traffic is then split between them
  • Genuine arm64 image

Pawns.app: the lowest payout threshold

The 5-dollar threshold is the lowest of the field – it is where you find out fastest whether anything arrives at all. Paid surveys you can fill in on a computer come on top.

Start Pawns.app
docker run -d --name pawns \
  --restart unless-stopped \
  iproyal/pawns-cli:latest \
  -email=[YOUR_PAWNS_EMAIL] \
  -password=[YOUR_PAWNS_PASSWORD] \
  -device-name=[NAME_FOR_THE_PI] \
  -accept-tos

Here the password does sit on the device Pawns.app authenticates with an email and password that stay readable inside the container. Use a long, unique password you do not use anywhere else.

  • Payout from 5 US dollars
  • One device per network
  • Paid surveys on top

Why a second Pi on the same network barely helps

Pawns.app allows one device per network, Honeygain likewise, and EarnApp caps the yield per IP. The reason is obvious: what is sold is not bandwidth but access from a real household, and that stays singular no matter how many devices you connect.

What actually counts is different connections. That is why it is worth running the apps on your phone over mobile data as well – that is a different IP.

Getting rid of them again

Remove both containers
docker rm -f tm
docker rm -f pawns
Frequently asked

Questions about this topic

Do TraffMonetizer and Pawns.app need the binfmt translation layer?

No. Both ship genuine arm64 images and run without the detour. Only Honeygain needs the translation layer on a Pi.

Which of the two pays out sooner?

Pawns.app at 5 US dollars. TraffMonetizer sits at 10. Both thresholds can change – what the dashboard says is what counts.

Why is token-based login safer?

Because no account password sits on the device. A token can be revoked in the dashboard without you having to change your password.

Can I run both alongside Honeygain and EarnApp?

Technically yes, the system load is small. Just remember that EarnApp has to run natively rather than in a container, and that several services share the same connection.