Open-source project
EliteProTech/ELITE-PRO-V1 avatar
EliteProTech/ELITE-PRO-V1

ELITE-PRO-V1: A Feature-Rich WhatsApp Bot for Termux and Cloud Panel Deployment

Project brief: A rich-feature WhatsApp bot built for speed and versatility. FOR PANEL DEPLOYMENT Click on DOWNLOAD to get zip file.

367 stars1,699 forksJavaScriptMIT

At a glance

What is it?
ELITE-PRO-V1 is a Node.js WhatsApp bot built on a custom Baileys fork. Version 1.1.1 bundles media conversion, Google Translate integration, YouTube search, QR code handling, and Google TTS, and deploys on Termux, Render, Heroku, or bot-hosting panels.
Who is it for?
ELITE-PRO-V1 works for individuals who want a WhatsApp automation bot on Termux or a free hosting panel without building one from scratch. Before deploying, read WhatsApp's terms of service: the bot uses Baileys, an unofficial WhatsApp client, and WhatsApp actively terminates accounts that use unofficial clients.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository last received commits 4 days ago.
What is it written in?
Mainly JavaScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on September 30, 2026, and from our analysis. They are not legal advice.

Editorial analysis

What ELITE-PRO-V1 Is and Who It Is For

ELITE-PRO-V1 is a WhatsApp bot packaged for deployment on Termux (Android), server panels, and free cloud hosting services like Render and Bot-Hosting.Net. It is aimed at individual developers and hobbyists who want to run automated commands and responses on a WhatsApp account without writing a bot from scratch.

The bot is built on a custom fork of Baileys called [email protected], listed as an npm package in the package.json. Baileys is an unofficial Node.js library that connects to WhatsApp by simulating the WhatsApp Web client. The bot wraps this library with a set of features for media processing, translation, text-to-speech, and web searches.

Version 1.1.1 is the current release. The main entry point is index.js, with a secondary entry at ElitePro.js. The Procfile and app.json files configure Heroku deployment.

Feature Set Visible in package.json

The README describes the bot as feature-rich but does not enumerate specific commands. The package.json dependencies reveal the categories of functionality available.

Media processing: the bot includes fluent-ffmpeg for video and audio conversion, jimp and sharp for image manipulation, and node-webpmux for WebP sticker creation. imagemagick must be installed separately for some operations. These dependencies support sticker creation, image editing, and audio/video format conversion commands typical in WhatsApp bots.

Translation and TTS: @vitalets/google-translate-api and translate-google-api provide translation, and google-tts-api provides text-to-speech output as audio messages.

Search and web interaction: yt-search handles YouTube video searches. cheerio and jsdom provide HTML parsing for web scraping commands.

Utilities: qrcode and jsqr handle QR code generation and scanning. awesome-phonenumber and libphonenumber-js handle phone number parsing. gifted-btns suggests support for interactive WhatsApp button menus. moment-timezone handles time zone-aware date formatting.

Persistence: the database/ directory implies some form of local data storage, though the implementation details are not documented in the README.

Installing and Starting the Bot on Termux

The README provides a Termux installation sequence for Android. Extract the downloaded ZIP archive to the internal storage Downloads folder before running these commands:

bash
pkg install nodejs -y
pkg install ffmpeg -y
pkg install imagemagick -y
pkg install yarn

Then install the Node.js dependencies and start the bot:

bash
yarn install
npm start

For a persistent session that survives Termux restarts, install pm2 and configure it as a process manager:

bash
npm i -g pm2 && pm2 start index.js && pm2 save && pm2 logs

Before starting, the bot requires a session ID obtained from eliteprotech-pair.zone.id. This session ID must be added to the SESSION_ID variable in the .env file or config.js. The README documents that the .env file holds this and other configuration values. The top-level repository entries list .env as a file in the repository root, which means the file exists in the repository structure and should be verified as gitignored before committing any local changes to a fork.

For panel or cloud deployment, the README documents download of the ZIP archive and upload to a hosting panel, plus deployment to Render, Bot-Hosting.Net, Katabump, Optiklink, Heroku, and two paid services.

Risk: Unofficial WhatsApp API and External Session Service

Baileys implements WhatsApp connectivity by reverse-engineering the WhatsApp Web protocol. WhatsApp's terms of service prohibit using unofficial clients or automation tools that simulate human behavior on the platform. Accounts that run Baileys-based bots are subject to temporary and permanent bans at WhatsApp's discretion, without advance notice.

This is not a theoretical risk. WhatsApp periodically bans accounts using unofficial clients as part of its anti-automation enforcement. The account associated with the session ID is the account that bears this risk. Individual users who deploy this bot on their personal WhatsApp number should consider the possibility of losing that number's access to WhatsApp.

The session ID itself comes from eliteprotech-pair.zone.id, an external pairing service. The README does not document what data this service collects or retains from the pairing process. A session ID for a WhatsApp account represents ongoing access to that account; sharing it with an external service has corresponding security implications that the README does not address.

Limitations and Alternative Approaches

The README does not document the specific commands the bot supports. The feature scope must be inferred from the package.json dependencies and the lib/ directory structure, which is not documented. An engineer evaluating this bot for a specific use case cannot confirm whether that use case is implemented without reading the source code.

The bot uses a custom npm package ([email protected]) that is not the standard @whiskeysockets/baileys. This means updates to the upstream Baileys library do not automatically apply, and compatibility with WhatsApp protocol changes depends on the fork's own maintenance.

whatsapp-web.js is an alternative unofficial WhatsApp library that also uses the WhatsApp Web API and is more widely used in the open-source community, with more extensive documentation. It carries the same terms-of-service risk as Baileys. The choice between them for a custom bot depends on which has better coverage for the commands required.

For official, terms-of-service-compliant WhatsApp automation, Meta provides the WhatsApp Business API through cloud-hosted and on-premises deployments. The Business API requires a business account and has throughput limits and message template restrictions that a hobbyist bot typically bypasses, but it does not carry account ban risk.

Maintenance and License

The last push to this repository was on 2026-09-26. The repository is not archived. The project carries an MIT license. It has no GitHub releases; the current version is tracked in the package.json version field (1.1.1) and in the README's version display.

The README invites users to fork and star the repository and provides links to a WhatsApp group, a WhatsApp channel, and a Telegram contact at @eliteprotechs for support. The repository also links to a second project, Elite-Pro-V2, suggesting the bot is under continued development. The YouTube channel at @eliteprotechs suggests the project includes video tutorials for deployment steps not covered in the README text.

Editorial conclusion

ELITE-PRO-V1 works for individuals who want a WhatsApp automation bot on Termux or a free hosting panel without building one from scratch. Before deploying, read WhatsApp's terms of service: the bot uses Baileys, an unofficial WhatsApp client, and WhatsApp actively terminates accounts that use unofficial clients. The session ID comes from an external service at eliteprotech-pair.zone.id that is not operated by the repository owner. The .env file is listed in the repository's top-level entries rather than in a gitignore, which means credentials could be committed to a fork if not removed manually before pushing. Verify that the .env file is excluded from version control before cloning and configuring the bot.

Frequently asked questions

How do I get a session ID for ELITE-PRO-V1?

Visit eliteprotech-pair.zone.id to generate a session ID through the pairing web interface. Add the session ID to SESSION_ID in the .env or config.js file before starting the bot.

What hosting platforms does ELITE-PRO-V1 support?

The README documents deployment on Termux (Android local), server panels via ZIP upload, Bot-Hosting.Net (free), Render (free), Katabump (free), Optiklink (free), Heroku (paid), and two paid services linked in the README.

Is ELITE-PRO-V1 allowed by WhatsApp's terms of service?

No. The bot uses Baileys, an unofficial WhatsApp client library. WhatsApp's terms of service prohibit unofficial clients, and accounts using them risk temporary or permanent bans. The README does not address this risk.

Official sources

  1. Official documentation
  2. Official README
  3. Project repository
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/eliteprotech-elite-pro-v1.svg)](https://hysenlabs.com/projects/eliteprotech-elite-pro-v1)