Custom Workflow Engine Development
Budget: $30 – $250 USD
The goal of this project is to build a flexible workflow engine that lets me model, execute, and monitor business processes from a single interface. Once the core system is in place, new workflows should be configurable—either through a drag-and-drop editor or concise JSON/YAML definitions—without touching the underlying code.
Core requirements
– Modular architecture in an easily maintainable open-source stack (Node.js, Python, Java, or Go).
– REST and webhook endpoints so other internal services can trigger, pause, or query workflows.
– Persistent storage of execution history with dashboards for status, SLA metrics, and error logs.
– Authentication hooks compatible with our existing OAuth/OIDC single-sign-on.
Deliverables
• Technical blueprint with the proposed design, libraries, and deployment plan.
• Running MVP in Docker that ships with one sample workflow featuring parallel branches and an approval gate.
• Source code in a private Git repository plus concise hand-over documentation.
Acceptance criteria
– A new workflow can be added or edited without redeploying the service.
– Tasks process in the correct order, support retries, and surface errors through the API.
– All code passes unit tests and linting.
Please include examples of similar engines or process automation tools you have created and suggest the technology stack you believe best meets these needs, along with a proposed timeline and milestone breakdown.
Core requirements
– Modular architecture in an easily maintainable open-source stack (Node.js, Python, Java, or Go).
– REST and webhook endpoints so other internal services can trigger, pause, or query workflows.
– Persistent storage of execution history with dashboards for status, SLA metrics, and error logs.
– Authentication hooks compatible with our existing OAuth/OIDC single-sign-on.
Deliverables
• Technical blueprint with the proposed design, libraries, and deployment plan.
• Running MVP in Docker that ships with one sample workflow featuring parallel branches and an approval gate.
• Source code in a private Git repository plus concise hand-over documentation.
Acceptance criteria
– A new workflow can be added or edited without redeploying the service.
– Tasks process in the correct order, support retries, and surface errors through the API.
– All code passes unit tests and linting.
Please include examples of similar engines or process automation tools you have created and suggest the technology stack you believe best meets these needs, along with a proposed timeline and milestone breakdown.
Related categories:
Business, Accounting, Human Resources & Legal
Python
NoSQL Couch & Mongo
Node.js
JSON
OAuth
Docker
REST API