Centralized Automation Platform with Dashboard
Budget / Salary$250–750
TypeFreelance project
LocationRemote
Posted2 hours ago
## JavaScript / Node.js Developer Needed to Build an Automation System with Dashboard and Executable Application
I am looking for a developer with experience in **JavaScript, Node.js, web automation, and desktop application development** to build from scratch a centralized automation platform with a **graphical dashboard**, designed to be usable even by people with no programming knowledge.
The goal is to develop a system from which the user can start, control, monitor, and manage different automated registration, onboarding, and profile management processes across different platforms and testing environments related to services such as:
* Google / Gmail / YouTube
* Facebook
* Instagram
* TikTok
* Spotify
The application must have a simple, visual, and professional interface, so that the end user does not need to use commands, terminals, or manually modify programming files.
## Main Features
The platform should include:
* Web-based dashboard or graphical administration interface.
* Administrator login system.
* Selection of the platform or module to be executed.
* Ability to define the number of processes to be started.
* Automatic generation of first names, last names, and fictitious data with a Latin American or Colombian format.
* Automatic execution of configured workflows.
* Real-time display of the status of each process.
* Execution statuses such as:
* Pending
* Queued
* Running
* Completed
* Failed
* Stopped
* Database record for every execution.
* Complete history of executed processes.
* Logging system to identify errors.
* Ability to retry failed tasks.
* Buttons to start, pause, stop, and restart processes.
* Simultaneous execution of multiple tasks.
* Queue system to properly manage processes.
* Result export functionality.
* General statistics panel.
* Filters and search function within the dashboard.
* Modular architecture that allows new platforms or workflows to be added later.
* API integrations when available.
* Browser automation for authorized workflows that require it.
* Configuration system directly from the graphical interface.
* Parameter management without needing to modify source code.
## Dashboard
The dashboard should clearly display, at minimum:
* Total number of processes.
* Completed processes.
* Pending processes.
* Running processes.
* Failed processes.
* Recent history.
* Platform used.
* Execution date and time.
* Individual status of each task.
* Logs and error messages.
* General system statistics.
The interface must be easy to use even for a person without technical knowledge.
## Preferred Technologies
The project should be developed mainly using:
* JavaScript
* Node.js
Experience with the following will also be valued:
* Playwright
* Puppeteer
* Electron
* React
* Next.js
* Express
* NestJS
* REST APIs
* OAuth 2.0
* SQL
* PostgreSQL
* MySQL
* MongoDB
* Redis
* Queue systems
* WebSockets
* Docker
* Browser automation
* Creation of executable Windows applications
## Expected Architecture
The project should be built from scratch using a clear, modular, and scalable structure.
Ideally, the architecture should separate:
1. Graphical interface or dashboard.
2. Backend.
3. API.
4. Automation engine.
5. Database.
6. Queue system.
7. Task management.
8. Logging system.
9. Independent modules for each platform.
10. Administration panel.
11. General configuration.
12. Statistics.
13. Application packaging and installation system.
The architecture should allow new modules to be added later without needing to rebuild the entire system.
## Executable Application for Non-Technical Users
An important requirement of the project is that the system must not be delivered only as source code.
The developer must also provide an **executable or installable version for Windows**, preferably through an:
**.exe file**
The application must be prepared so that a person without programming knowledge can use it.
The user should be able to:
* Download or receive the installer.
* Run the installation file.
* Install the program through a graphical interface.
* Create a Windows desktop shortcut.
* Open the application by double-clicking.
* Access the dashboard directly.
* Configure the system from the interface.
* Start and stop processes using buttons.
* View results and errors from the dashboard.
The end user should not need to:
* Manually install Node.js.
* Use CMD.
* Use PowerShell.
* Open a terminal.
* Run npm commands.
* Modify JavaScript files.
* Manually edit configuration files.
* Install dependencies one by one.
All components required to run the system should either be included or installed automatically.
If **Electron, Tauri, or another similar technology** is used, the developer may propose the architecture they consider most suitable.
## Installer
The final delivery should include a professional installer that allows the user to:
* Install the application.
* Select the installation location if necessary.
* Create a desktop shortcut.
* Automatically install the required dependencies.
* Launch the application.
* Properly uninstall it from Windows.
The installer should preferably work with:
* Windows 10.
* Windows 11.
## Configuration from the Interface
The main settings should be configurable directly from the application.
For example:
* Number of processes.
* Platform.
* Execution parameters.
* Directories.
* Database.
* Concurrency limits.
* Module configurations.
* General settings.
The goal is to prevent the user from needing to open or modify internal project files.
## Update System
Preferably, the architecture should be prepared to support future implementation of:
* Automatic updates.
* Manual updates through a button.
* Downloading new versions.
* Updating modules without completely reinstalling the system.
The complete update system does not necessarily need to be implemented in the first version, but the architecture should make it possible to add it later.
## Mandatory Deliverables
The developer must provide:
1. Complete project source code.
2. Fully functional dashboard.
3. Complete backend.
4. Configured database.
5. Automation engine.
6. Agreed modules.
7. Queue system.
8. Logging system.
9. Statistics panel.
10. Configuration system.
11. Executable Windows application.
12. `.exe` installer file.
13. Desktop shortcut.
14. Automatic dependency installation system.
15. Uninstaller.
16. Basic installation documentation.
17. Basic user manual.
18. Architecture documentation.
19. Organized and commented code.
20. Instructions for rebuilding the project.
21. Instructions for generating the executable again.
22. Full application functionality tests.
## Delivery Condition
**The project will not be considered completed with the delivery of source code alone.**
The final delivery must include a version that is **fully installable, executable, and usable by a person with no programming knowledge**.
The main system functions should be accessible through buttons, forms, and options available within the graphical interface.
## Source Code
In addition to the executable application, the developer must provide **100% of the source code** used to build the application.
The code must be organized so that another developer can later:
* Review it.
* Modify it.
* Add features.
* Create new modules.
* Fix bugs.
* Generate new versions of the executable application.
A closed application without access to the source code will not be accepted.
## Project Ownership
Upon completion of the project and corresponding payment, all code developed for the project must be delivered together with:
* Source files.
* Database.
* Scripts.
* Configuration files.
* Documentation.
* Files required for compilation.
* Installer.
* Executable application.
## Development by Milestones
Preferably, the project may be divided into stages or milestones.
### Stage 1 — Architecture and Dashboard
* General structure.
* Dashboard.
* Database.
* Backend.
* User system.
### Stage 2 — Automation Engine
* Task system.
* Queues.
* Execution.
* Logs.
* Process control.
### Stage 3 — Modules
Development and integration of the agreed modules.
### Stage 4 — Desktop Application
* Dashboard and backend integration.
* Windows application.
* Installer.
* Executable file.
### Stage 5 — Testing and Delivery
* Complete testing.
* Bug fixes.
* Documentation.
* Source code.
* Final executable application.
## When Submitting Your Proposal
Please include:
1. Your experience with JavaScript and Node.js.
2. Your experience with Playwright or Puppeteer.
3. Your experience developing automation systems.
4. Your experience developing dashboards.
5. Your experience creating executable Windows applications.
6. Your experience with Electron, Tauri, or similar technologies.
7. Examples of similar systems you have developed.
8. The architecture you recommend.
9. The database you recommend.
10. How you would convert the project into an installable application.
11. Your estimated fixed price for developing the complete project.
12. Whether the project can be divided into milestones or staged payments.
I am preferably looking for a developer with **real experience in JavaScript / Node.js, automation, dashboards, and desktop applications**, who can build a stable, well-organized, and easy-to-use solution for non-technical users.
A **competitive fixed-price proposal** and the possibility of dividing the project into verifiable partial deliveries will be highly valued.
I am looking for a developer with experience in **JavaScript, Node.js, web automation, and desktop application development** to build from scratch a centralized automation platform with a **graphical dashboard**, designed to be usable even by people with no programming knowledge.
The goal is to develop a system from which the user can start, control, monitor, and manage different automated registration, onboarding, and profile management processes across different platforms and testing environments related to services such as:
* Google / Gmail / YouTube
* TikTok
* Spotify
The application must have a simple, visual, and professional interface, so that the end user does not need to use commands, terminals, or manually modify programming files.
## Main Features
The platform should include:
* Web-based dashboard or graphical administration interface.
* Administrator login system.
* Selection of the platform or module to be executed.
* Ability to define the number of processes to be started.
* Automatic generation of first names, last names, and fictitious data with a Latin American or Colombian format.
* Automatic execution of configured workflows.
* Real-time display of the status of each process.
* Execution statuses such as:
* Pending
* Queued
* Running
* Completed
* Failed
* Stopped
* Database record for every execution.
* Complete history of executed processes.
* Logging system to identify errors.
* Ability to retry failed tasks.
* Buttons to start, pause, stop, and restart processes.
* Simultaneous execution of multiple tasks.
* Queue system to properly manage processes.
* Result export functionality.
* General statistics panel.
* Filters and search function within the dashboard.
* Modular architecture that allows new platforms or workflows to be added later.
* API integrations when available.
* Browser automation for authorized workflows that require it.
* Configuration system directly from the graphical interface.
* Parameter management without needing to modify source code.
## Dashboard
The dashboard should clearly display, at minimum:
* Total number of processes.
* Completed processes.
* Pending processes.
* Running processes.
* Failed processes.
* Recent history.
* Platform used.
* Execution date and time.
* Individual status of each task.
* Logs and error messages.
* General system statistics.
The interface must be easy to use even for a person without technical knowledge.
## Preferred Technologies
The project should be developed mainly using:
* JavaScript
* Node.js
Experience with the following will also be valued:
* Playwright
* Puppeteer
* Electron
* React
* Next.js
* Express
* NestJS
* REST APIs
* OAuth 2.0
* SQL
* PostgreSQL
* MySQL
* MongoDB
* Redis
* Queue systems
* WebSockets
* Docker
* Browser automation
* Creation of executable Windows applications
## Expected Architecture
The project should be built from scratch using a clear, modular, and scalable structure.
Ideally, the architecture should separate:
1. Graphical interface or dashboard.
2. Backend.
3. API.
4. Automation engine.
5. Database.
6. Queue system.
7. Task management.
8. Logging system.
9. Independent modules for each platform.
10. Administration panel.
11. General configuration.
12. Statistics.
13. Application packaging and installation system.
The architecture should allow new modules to be added later without needing to rebuild the entire system.
## Executable Application for Non-Technical Users
An important requirement of the project is that the system must not be delivered only as source code.
The developer must also provide an **executable or installable version for Windows**, preferably through an:
**.exe file**
The application must be prepared so that a person without programming knowledge can use it.
The user should be able to:
* Download or receive the installer.
* Run the installation file.
* Install the program through a graphical interface.
* Create a Windows desktop shortcut.
* Open the application by double-clicking.
* Access the dashboard directly.
* Configure the system from the interface.
* Start and stop processes using buttons.
* View results and errors from the dashboard.
The end user should not need to:
* Manually install Node.js.
* Use CMD.
* Use PowerShell.
* Open a terminal.
* Run npm commands.
* Modify JavaScript files.
* Manually edit configuration files.
* Install dependencies one by one.
All components required to run the system should either be included or installed automatically.
If **Electron, Tauri, or another similar technology** is used, the developer may propose the architecture they consider most suitable.
## Installer
The final delivery should include a professional installer that allows the user to:
* Install the application.
* Select the installation location if necessary.
* Create a desktop shortcut.
* Automatically install the required dependencies.
* Launch the application.
* Properly uninstall it from Windows.
The installer should preferably work with:
* Windows 10.
* Windows 11.
## Configuration from the Interface
The main settings should be configurable directly from the application.
For example:
* Number of processes.
* Platform.
* Execution parameters.
* Directories.
* Database.
* Concurrency limits.
* Module configurations.
* General settings.
The goal is to prevent the user from needing to open or modify internal project files.
## Update System
Preferably, the architecture should be prepared to support future implementation of:
* Automatic updates.
* Manual updates through a button.
* Downloading new versions.
* Updating modules without completely reinstalling the system.
The complete update system does not necessarily need to be implemented in the first version, but the architecture should make it possible to add it later.
## Mandatory Deliverables
The developer must provide:
1. Complete project source code.
2. Fully functional dashboard.
3. Complete backend.
4. Configured database.
5. Automation engine.
6. Agreed modules.
7. Queue system.
8. Logging system.
9. Statistics panel.
10. Configuration system.
11. Executable Windows application.
12. `.exe` installer file.
13. Desktop shortcut.
14. Automatic dependency installation system.
15. Uninstaller.
16. Basic installation documentation.
17. Basic user manual.
18. Architecture documentation.
19. Organized and commented code.
20. Instructions for rebuilding the project.
21. Instructions for generating the executable again.
22. Full application functionality tests.
## Delivery Condition
**The project will not be considered completed with the delivery of source code alone.**
The final delivery must include a version that is **fully installable, executable, and usable by a person with no programming knowledge**.
The main system functions should be accessible through buttons, forms, and options available within the graphical interface.
## Source Code
In addition to the executable application, the developer must provide **100% of the source code** used to build the application.
The code must be organized so that another developer can later:
* Review it.
* Modify it.
* Add features.
* Create new modules.
* Fix bugs.
* Generate new versions of the executable application.
A closed application without access to the source code will not be accepted.
## Project Ownership
Upon completion of the project and corresponding payment, all code developed for the project must be delivered together with:
* Source files.
* Database.
* Scripts.
* Configuration files.
* Documentation.
* Files required for compilation.
* Installer.
* Executable application.
## Development by Milestones
Preferably, the project may be divided into stages or milestones.
### Stage 1 — Architecture and Dashboard
* General structure.
* Dashboard.
* Database.
* Backend.
* User system.
### Stage 2 — Automation Engine
* Task system.
* Queues.
* Execution.
* Logs.
* Process control.
### Stage 3 — Modules
Development and integration of the agreed modules.
### Stage 4 — Desktop Application
* Dashboard and backend integration.
* Windows application.
* Installer.
* Executable file.
### Stage 5 — Testing and Delivery
* Complete testing.
* Bug fixes.
* Documentation.
* Source code.
* Final executable application.
## When Submitting Your Proposal
Please include:
1. Your experience with JavaScript and Node.js.
2. Your experience with Playwright or Puppeteer.
3. Your experience developing automation systems.
4. Your experience developing dashboards.
5. Your experience creating executable Windows applications.
6. Your experience with Electron, Tauri, or similar technologies.
7. Examples of similar systems you have developed.
8. The architecture you recommend.
9. The database you recommend.
10. How you would convert the project into an installable application.
11. Your estimated fixed price for developing the complete project.
12. Whether the project can be divided into milestones or staged payments.
I am preferably looking for a developer with **real experience in JavaScript / Node.js, automation, dashboards, and desktop applications**, who can build a stable, well-organized, and easy-to-use solution for non-technical users.
A **competitive fixed-price proposal** and the possibility of dividing the project into verifiable partial deliveries will be highly valued.
Apply on Freelancer →
Project sourced from Freelancer.com. Applications happen directly on the original platform — we never collect your data.