reNgine-ng is a (detached) fork of reNgine.

reNgine-ng is your go-to web application reconnaissance suite that's designed to simplify and streamline the reconnaissance process for security professionals, penetration testers, and bug bounty hunters. With its highly configurable engines, data correlation capabilities, continuous monitoring, database-backed reconnaissance data, and an intuitive user interface, reNgine-ng redefines how you gather critical information about your target web applications.

Traditional reconnaissance tools often fall short in terms of configurability and efficiency. reNgine-ng addresses these shortcomings and emerges as a excellent alternative to existing commercial tools.

reNgine-ng was created to address the limitations of traditional reconnaissance tools and provide a better alternative, even surpassing some commercial offerings. Whether you're a bug bounty hunter, a penetration tester, or a corporate security team, reNgine-ng is your go-to solution for automating and enhancing your information-gathering efforts.

reNgine-ng 2.0 is out now, you can watch reNgine-ng 2.0 release trailer here!

reNgine-ng 2.0 would not have been possible without @ocervell valuable contributions. @ocervell did majority of the refactoring if not all and also added a ton of features. Together, we wish to shape the future of web application reconnaissance, and it's developers like @ocervell and a ton of other developers and hackers from our community who inspire and drive us forward.

Thank you, @ocervell, for your outstanding work and unwavering commitment to reNgine-ng.

Checkout our contributors here: Contributors

You can find detailed documentation in the repository Wiki

• Workflow
• Quick Installation
• Updating
• What's new in reNgine-ng 2.0
• Screenshots
• Contributing

Note: Only Ubuntu/VPS

1. Clone this repo

   git clone https://github.com/Security-Tools-Alliance/rengine-ng && cd rengine-ng

2. Edit the dotenv file, please make sure to change the password for postgresql POSTGRES_PASSWORD!

   nano .env

3. In the dotenv file, you may also modify the Scaling Configurations

   MAX_CONCURRENCY=80
   MIN_CONCURRENCY=10

   MAX_CONCURRENCY: This parameter specifies the maximum number of reNgine-ng's concurrent Celery worker processes that can be spawned. In this case, it's set to 80, meaning that the application can utilize up to 80 concurrent worker processes to execute tasks concurrently. This is useful for handling a high volume of scans or when you want to scale up processing power during periods of high demand. If you have more CPU cores, you will need to increase this for maximized performance.

   MIN_CONCURRENCY: On the other hand, MIN_CONCURRENCY specifies the minimum number of concurrent worker processes that should be maintained, even during periods of lower demand. In this example, it's set to 10, which means that even when there are fewer tasks to process, at least 10 worker processes will be kept running. This helps ensure that the application can respond promptly to incoming tasks without the overhead of repeatedly starting and stopping worker processes.

   These settings allow for dynamic scaling of Celery workers, ensuring that the application efficiently manages its workload by adjusting the number of concurrent workers based on the workload's size and complexity

4. Run the installation script, Please keep an eye for any prompt, you will also be asked for username and password for reNgine-ng.

   sudo ./install.sh

   If install.sh does not have execution permissions, please grant it execution permissions: chmod +x install.sh

Detailed installation instructions can be found at https://github.com/Security-Tools-Alliance/rengine-ng/wiki/Installation#-quick-installation

1. Updating is as simple as running the following command:

   cd rengine-ng && sudo ./update.sh

   If update.sh does not have execution permissions, please grant it execution permissions: sudo chmod +x update.sh

   NOTE: if you're updating from 1.3.6 and you're getting a 'password authentication failed' error, consider uninstalling 1.3.6 first, then install 2.x.x as you'd normally do.

Detailed update instructions: https://github.com/Security-Tools-Alliance/rengine-ng/wiki/Installation#-quick-update

Please find the latest release notes and changelog here.

See the Contributing Guide to get started.