Basic Node.js Automation Script
Budget: $10 – $30 AUD
Project Overview:
I've built an automated Discord monitoring system. Its purpose is to run 24/7 on a VPS for a small, private subscription service I'm starting. The system is already built and working.
Here's a quick summary of how it functions:
The Core: A Node.js script using discord.js-selfbot-v13 logs in with a user token and listens for messages in specific, pre-configured channels.
The Logic: When a valid message is detected, the script extracts the URL, sanitizes it (follows redirects, strips tracking tags), and then relays it to a private Discord server via a webhook.
The Resilience: I've also built a separate Manager.js script that provides an automated failover system, switching to a backup "sleeper" account if the primary one is banned.
What I Need Your Expertise For:
The system works, but as I'm preparing to deploy it, I want a professional to ensure it's as "bulletproof" as possible. My budget is tight as this is a personal startup, so I'm not looking for a full rewrite—just your expert guidance and implementation on these specific points:
Code Review: A quick review of my scripts (Manager.js and the main monitor script) for any obvious bugs, race conditions, or performance improvements.
Security Hardening: The most important task. Help me implement the best practice for storing my secret tokens (e.g., moving them from my JSON config to environment variables on the server).
Reliability (PM2 Setup): Configure a PM2 ecosystem.config.js file to properly manage both the Node.js monitor and my separate .NET relay executable, ensuring they both restart automatically on crash or server reboot.
Stealth Validation: A quick check of my current stealth measures (residential proxy use, idle status, random delays) to confirm they are sound.
The goal is to have peace of mind that the system is secure and reliable before I start onboarding paying members.
Given that the core architecture is already complete, I'm hoping we can agree on a fixed price for this review-and-refine project that fits within a startup budget.
If this sounds like a project that interests you, I would be happy to share the full codebase with you and discuss a quote, what would you charge for something like this
Here are some rough improvemts I also want to make *I may decide not to proceed with these*
Ensuring it is compatible and easy to introduce and get working for Linux oprating systems such as Ubuntu, aswel as compartible with windows
Ideally use PM2 as discussed before.
Secret Management: All secrets (Discord tokens, webhook URLs, SMTP credentials, proxy credentials, etc.) must be removed from all JSON configuration files. They must be loaded exclusively from Environment Variables (via a .env file for ease of use).
Proxy Integration: The Node.js Monitor must have proxy support fully integrated. It should be configured to route all of its traffic through a residential/ISP proxy defined in the environment variables.
Automated Failover: The AccountManager's failover logic is critical. It must work seamlessly with the new environment variable system, allowing the Manager.js (or a similar PM2-managed script) to restart the worker with a different set of credentials (TOKEN_2, PROXY_2) upon detecting a ban.
* I will likely only have 1 proxy for multiple tokens/accounts so it needs to be able to handle all of that*
Unified Configuration: All configuration settings (monitored channels, routing rules, alert templates, etc.) must be merged into a single, master config.json file.
Live Reloading: The Node.js Monitor and the .NET Relay must be able to reload their configuration without a full restart. The .NET ConfigControlService should handle this by watching the file for changes and broadcasting an update event, or the scripts can be configured to restart gracefully via PM2 upon a config change.
I also want a heart beat system, maybe a dashboard I can access/probably just be in the vps.
I want the dashboard to show me everything I catorgioes so I can see what I want to see easily such as products/links its forwared, events, time to next heart beats, everything.
I want email notifcations specifically reguarding major actions within the system/not the actual discord notifications just for me to manage.
I want advanced ban detection
I want a smart, intelligent and logic system.
I want plently of logging.
To be able to easily stop and start the system.\
I want to be able to easily configure which discord channels and servers to check *include author checks aswell*,
were they forward to, they will each forward to there own seperae channel, some may overlap.
Most importantly it needs to be bulletproof, intelligent and easy to manage.
I've built an automated Discord monitoring system. Its purpose is to run 24/7 on a VPS for a small, private subscription service I'm starting. The system is already built and working.
Here's a quick summary of how it functions:
The Core: A Node.js script using discord.js-selfbot-v13 logs in with a user token and listens for messages in specific, pre-configured channels.
The Logic: When a valid message is detected, the script extracts the URL, sanitizes it (follows redirects, strips tracking tags), and then relays it to a private Discord server via a webhook.
The Resilience: I've also built a separate Manager.js script that provides an automated failover system, switching to a backup "sleeper" account if the primary one is banned.
What I Need Your Expertise For:
The system works, but as I'm preparing to deploy it, I want a professional to ensure it's as "bulletproof" as possible. My budget is tight as this is a personal startup, so I'm not looking for a full rewrite—just your expert guidance and implementation on these specific points:
Code Review: A quick review of my scripts (Manager.js and the main monitor script) for any obvious bugs, race conditions, or performance improvements.
Security Hardening: The most important task. Help me implement the best practice for storing my secret tokens (e.g., moving them from my JSON config to environment variables on the server).
Reliability (PM2 Setup): Configure a PM2 ecosystem.config.js file to properly manage both the Node.js monitor and my separate .NET relay executable, ensuring they both restart automatically on crash or server reboot.
Stealth Validation: A quick check of my current stealth measures (residential proxy use, idle status, random delays) to confirm they are sound.
The goal is to have peace of mind that the system is secure and reliable before I start onboarding paying members.
Given that the core architecture is already complete, I'm hoping we can agree on a fixed price for this review-and-refine project that fits within a startup budget.
If this sounds like a project that interests you, I would be happy to share the full codebase with you and discuss a quote, what would you charge for something like this
Here are some rough improvemts I also want to make *I may decide not to proceed with these*
Ensuring it is compatible and easy to introduce and get working for Linux oprating systems such as Ubuntu, aswel as compartible with windows
Ideally use PM2 as discussed before.
Secret Management: All secrets (Discord tokens, webhook URLs, SMTP credentials, proxy credentials, etc.) must be removed from all JSON configuration files. They must be loaded exclusively from Environment Variables (via a .env file for ease of use).
Proxy Integration: The Node.js Monitor must have proxy support fully integrated. It should be configured to route all of its traffic through a residential/ISP proxy defined in the environment variables.
Automated Failover: The AccountManager's failover logic is critical. It must work seamlessly with the new environment variable system, allowing the Manager.js (or a similar PM2-managed script) to restart the worker with a different set of credentials (TOKEN_2, PROXY_2) upon detecting a ban.
* I will likely only have 1 proxy for multiple tokens/accounts so it needs to be able to handle all of that*
Unified Configuration: All configuration settings (monitored channels, routing rules, alert templates, etc.) must be merged into a single, master config.json file.
Live Reloading: The Node.js Monitor and the .NET Relay must be able to reload their configuration without a full restart. The .NET ConfigControlService should handle this by watching the file for changes and broadcasting an update event, or the scripts can be configured to restart gracefully via PM2 upon a config change.
I also want a heart beat system, maybe a dashboard I can access/probably just be in the vps.
I want the dashboard to show me everything I catorgioes so I can see what I want to see easily such as products/links its forwared, events, time to next heart beats, everything.
I want email notifcations specifically reguarding major actions within the system/not the actual discord notifications just for me to manage.
I want advanced ban detection
I want a smart, intelligent and logic system.
I want plently of logging.
To be able to easily stop and start the system.\
I want to be able to easily configure which discord channels and servers to check *include author checks aswell*,
were they forward to, they will each forward to there own seperae channel, some may overlap.
Most importantly it needs to be bulletproof, intelligent and easy to manage.