instagram-reels-warmup
Instagram Reels warmup campaigns on antidetect Cloud Phone
Community SDK — not affiliated with Multilogin GmbH. Requires your own Multilogin subscription.
Why this package
7–14 day warmup plans — MIN50 on Cloud Phone minutes.
| Problem | This tool |
|---|---|
| Scattered scripts for Multilogin workflows | Typed helpers + CLI you can import in CI |
| Unclear browser vs Cloud Phone choice | ig-warmup recommend --use-case mobile_instagram |
| Partner offers hard to verify | Structured disclosure via ig-warmup affiliate |
Install
pip install instagram-reels-warmup
export MLX_API_TOKEN="your_token" # from Multilogin dashboard
ig-warmup doctor
Quick start
ig-warmup plans
ig-warmup plan reels_7d
# Library usage
from instagram_reels_warmup import __version__
import instagram_reels_warmup.core as core
CLI reference
| Command | Purpose |
|---|---|
ig-warmup doctor |
Token, env, package health |
ig-warmup recommend |
Browser vs Cloud Phone guide |
ig-warmup affiliate |
Partner disclosure + SAAS50 / MIN50 |
ig-warmup seo --json |
PyPI / docs metadata |
Run ig-warmup --help for domain-specific commands.
Account group (acc-3)
Publish these four packages on the same PyPI account:
| Package | Role |
|---|---|
| tiktok-mobile-farm | Companion on same PyPI account |
| shopee-seller-mobile | Companion on same PyPI account |
| adb-cloud-bridge | Companion on same PyPI account |
Related: Cloud Phone stack
| Package | Role |
|---|---|
| mlx-cloud-phone | Mobile SDK + mlx-phone |
| cloud-phone-geo | Country / proxy presets |
| cloud-phone-warmup | Mobile warmup |
| cloud-phone-fleet | Bulk fleet |
Partner disclosure
We publish independent tooling for Multilogin users and may earn a commission when you use partner offers. Always verify discount lines at checkout.
| Product | Code | Where |
|---|---|---|
| Multilogin X browser plans | SAAS50 | SaaSVerdict |
| Cloud Phone minutes | MIN50 | SaaSVerdict |
| Scripts & alerts | — | @Multilogin_Scripts_Bot |
ig-warmup affiliate --json
ig-warmup recommend --use-case mobile_instagram
License
MIT — see LICENSE.
Metadata
Release files for instagram-reels-warmup 2.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| instagram_reels_warmup-2.0.0.tar.gz | 10.6 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| instagram_reels_warmup-2.0.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 21.0 kB
Release files / instagram_reels_warmup-2.0.0.tar.gz
| Download URL | instagram_reels_warmup-2.0.0.tar.gz |
|---|---|
| Size | 10.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
414dd130f607a84af19e0af80f17793ff89ceb8def876013e950274f989487a2
|
|
BLAKE2b-256 checksum How to use checksums |
59bbd7aa054b5483871ce9256a2033ab0462d2227a1b23dbb157a837b4cde8e8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Release files / instagram_reels_warmup-2.0.0-py3-none-any.whl
| Download URL | instagram_reels_warmup-2.0.0-py3-none-any.whl |
|---|---|
| Size | 10.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
84d837ccc7d846862bd7db3bdea619ac2578c7f17e8e13265a8e5b762ce1f0d9
|
|
BLAKE2b-256 checksum How to use checksums |
1d77eed092827704c47302c70cd498c4c1cf1d2e7c2650a9b435f59baeb52cc3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.14.3
|
Security for instagram-reels-warmup 2.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.