Instagram Bot and the SMM Provider Journey

TheGlobalSeller

Regular Member
Joined
Oct 5, 2021
Messages
224
Reaction score
44
I’ve just finished setting up my project, and I wanted to share the starting point of this journey.

I built the system using 7 Pixel 7 Pro ( GrapheneOS ) devices. Each device runs automation for 32 profiles × 5 accounts — that’s 160 accounts per device, and multiplied across 7 devices, it became a solid foundation.

I integrated it with Perfect Panel as the provider, so now everything works 100% automatically with SMM panels.

At the moment, the system only works on Instagram and supports follow, like, and comment actions.


It took me about 2–3 months to get it all running smoothly.

Technologies I used along the way;
  • Python, Docker, uiautomator2, ADB
  • FastAPI, Celery, Flower
You can ask what you are curious about ❤️

1758075141893.png1758075158241.png
 
Interesting project.

I've some tech questions.

How many proxies? Or you use 4g sim card proxy?
What is the rate ban ?

You use clean graphene OS? or you modified it?

Did you try or use AirTest?
 
Interesting project.

I've some tech questions.

How many proxies? Or you use 4g sim card proxy?
What is the rate ban ?

You use clean graphene OS? or you modified it?

Did you try or use AirTest?

It only supports 4G SIM, has some 4G configurations, profile switching, waiting in airplane mode even for Instagram account selection, doing too many operations within the same account, queuing, re-connect, async task distribution — it has technical details like these.
My ban rate is lower than 1%
 
It only supports 4G SIM, has some 4G configurations, profile switching, waiting in airplane mode even for Instagram account selection, doing too many operations within the same account, queuing, re-connect, async task distribution — it has technical details like these.
My ban rate is lower than 1%
So you dont change OS?
Just automations and change between profiles? Or do you have deep android/grapheneOS modifications?
 
Running 7 Pixels on GrapheneOS with 160 IG accs each sounds like a solid farm setup. Curious if you’ve noticed any major difference in account trust score compared to virtualized setups like emulators or cloud devices?
The biggest bottleneck imo isn't in scaling actions but monitoring when accounts silently hit soft bans for example. Do you have any system to auto-detect those before wasting tasks?
 
Running 7 Pixels on GrapheneOS with 160 IG accs each sounds like a solid farm setup. Curious if you’ve noticed any major difference in account trust score compared to virtualized setups like emulators or cloud devices?
The biggest bottleneck imo isn't in scaling actions but monitoring when accounts silently hit soft bans for example. Do you have any system to auto-detect those before wasting tasks?
Each mechanism is logged from start to finish, and the current setup easily scales to 10 or even 100 devices. The statuses pending, processing, failed, completed are passed through to the SMM panel via concurrent APIs. It can even identify which device, which profile, and which Instagram account is problematic.

I haven’t had the chance to experience the operations of other providers before. Methods such as cookie, Selenium, or HTTP are also available, but since I’m familiar with the technical details, I tried to get involved down to the most critical points within the device flow. To ensure speed, during testing I developed methods that accelerated the process by 4–5x while keeping 4G reconnects to a minimum.
 
Last edited:
how much u making per month now from these 160 accs
It's just a secret, but I want to share that instead of making a bot account, I do everything like a real account to make it look 99% organic. I made the 4-6 sharing, pp, usrrname selection of each account completely with the team. That's why I give expensive services and it's a special country as a geo
 
Impressive system, must’ve been a headache getting ADB + uiautomator2 stable across devices.
 
I haven’t had the chance to experience the operations of other providers before. Methods such as cookie, Selenium, or HTTP are also available, but since I’m familiar with the technical details, I tried to get involved down to the most critical points within the device flow. To ensure speed, during testing I developed methods that accelerated the process by 4–5x while keeping 4G reconnects to a minimum.
It's interesting that you focused specifically on API optimization and 4G recon. I would say that on such a scale, the bottleneck is more often in trust in accounts.
Methods such as Selenium and HTTP are really convenient, but you went through bare device flow optimization. I'm curious: if we put 4G recon aside, what would you call the most problematic element of the entire system? Where do you feel the most pain when scaling if you can tell
 
following your journey .
In the mean time , the question i want to ask is are you profitable ? You made all this bot just for selling or you have other source of income through botting as well ?
 
following your journey .
In the mean time , the question i want to ask is are you profitable ? You made all this bot just for selling or you have other source of income through botting as well ?

The only cost of this job is sim cards, you can calculate the cost on the 40-60 gb internet package prices of your country. Of course, there is a profitability dimension of the business.

I'm interested in multiple sectors, that's not my only job.
 
It's interesting that you focused specifically on API optimization and 4G recon. I would say that on such a scale, the bottleneck is more often in trust in accounts.
Methods such as Selenium and HTTP are really convenient, but you went through bare device flow optimization. I'm curious: if we put 4G recon aside, what would you call the most problematic element of the entire system? Where do you feel the most pain when scaling if you can tell

Processes and scenarios, they were the areas that caused the most difficulty
again again again…
 
Back
Top