FAQ

How Does It Work?

The tool runs a series of applications in a stack in a containerized environment isolated from the host to generate passive income. By essentially selling your internet bandwidth which you have already paid and never utilised 100%, it can be monetized to earn back some of the expenses.

What's The Purpose Of This Project?

The goal and intention is to monetise resources that we rely on daily and turn into a form of passive income source, with little to no effort. Additionally for anyone looking for that little extra boost, without needing any form of initial investment, including the less technicals.

I run it myself hence the idea. To build myself an extra income source.

What Information Is Required?

• The only information that is required for registration is usually just the email and password.
• When configuring, the email, password or API keys are required. This is stored and configured locally.
• For payout withdrawal, the required information can be of your choice depending on the platform's supported withdrawal method. This is usually PayPal, WebMoney, Payeer, and Cryptocurrencies.

Is It Safe?

• Your credentials, API keys etc used to load the applications are all stored locally within the tool folder in a .env file. This information is only available to you when you run the setup configuration to configure the applications. The file is dynamically generated when the tool runs and no file exists. It also doesn't get replaced when performing an update to the latest tool version.
• All of the applications are run within a containerized docker environment called containers which is isolated from the host system, increasing security and privacy.

How Much Resource Does It Use?

Resource used are typically minimal both in terms of hardware usage (CPU, RAM, Disk space) and in terms of internet bandwidth. With testing on a Raspberry Pi 4 and Cloud Server, the start-up phase will spike up as everything is starting, but the CPU is negligible after the start-up phase.

RAM resource usage has always remained below 500MB and if the usage exceeds the limits set, the application is automatically restarted ensuring a clean state. This is all managed by Docker.

Network usage isn't continuous but sporadic as the applications are only pinged when required, therefore never exceeding 1 Mbps bandwidth.

What's The Monthly Income?

This will vary based on multiple factors:

• The type of IP address used and the region.
• The number of devices/IP addresses.
• The internet speed and network quality.
• Demand for data from the application. No demand means no earning.
• Device uptime.

Typically if the device is running 24/7 with enough traffic then the earnings will go up. You could expect to earn around $10-$20 per month. This is being on the modest side. A good example is to run it on a Raspberry Pi 3/4, which uses very little resources and electricity, making it perfect to run 24/7.

This tool aims to provide another form of passive income that doesn't require any form of investment or effort put in whilst utilising existing hardware that's either in use or dormant and an internet connection that's already an expense. Treat this type of income as beer money, dividends, or interest earned from savings in a bank. With a mindset like that, you'd get a lot more out of this tool if you approach it this way. Of course, you can withdraw the money and grow it further elsewhere.

It isn't designed to make you rich overnight. Think of it as a little extra help when you need it.

Some Apps Aren't Working. Is This Normal?

Sometimes, some of the applications despite being deployed successfully and shown as running when viewing the status, might not be running properly when we inspect the logs.

Unless it's unsupported on your device due to hardware constraints, usually we'd have to wait for a new version to be pushed out and there's not much we can do unless we tamper with the application and build a new image ourselves.

As long as the stack is running fine, eventually when a new image is available from Docker Hub, the tool stack will automatically fetch the new image and apply the update changes. Just give it some time.

Why You Don't Support Proxies?

Yes, technically you can use proxies to increase the potential income revenues as the stack deployed under a proxy is technically treated as a separate IP location, and there are versions out that support proxies. However, I don't recommend that.

My reasoning is, that if you get caught spoofing, not only are you at risk of getting your accounts banned, IP blacklisted, you're ruining it for the rest of the community. The idea is to be smart here, if you're greedy, you're only going to risk losing one or many of your sources of income.

There are cases where an entire country was banned due to abusive use. I won't name the country but was it worth it? In the long term being able to keep the income source is far more important than short-term gains. Passive Income or getting rich is never an overnight thing.

It's better to maintain account preservation, with consistency, even if it takes longer to earn for payouts. It's fully passive at the end of the day and money you don't need but a nice addition.