For the past 5 days I’ve been working on a SaaS product based on ProcessMaker.
Riverflow is a service that allows you to manage ProcessMaker instances on-demand, making it easy for users to work on BPM.
I have to admit that ProcessMaker is a great product. It virtually allows you to automatize any process you can think about. As the product evolves, the user base gets bigger and more people start converting their business processes.
But there’s one catch: You need a server with specific needs in order to make it work. Some people have tried to install it on shared hosting servers, but without much success. The product structure and architecture is quite different from other open-source products.
That’s where Riverflow comes in. By using Amazon’s EC2 instances, two servers (one for the application and the other for the database) are working and serving ProcessMaker. Also, there’s a control panel that allows you to create ProcessMaker instances, so you have a subdomain and a workspace by default.
The architecture of Riverflow will allow users to use their own domains to point to an IP and get a ProcessMaker instance as response. Regarding the technical details, it’s a Ruby application, using Sinatra. User data is saved using Redis and a LNMP (Linux, Nginx, MariaDB, PHP-FPM) stack is used to serve ProcessMaker.
Currently, it’s invitation-only. I’ll start rolling out some invites later.
You can always reach me on twitter @yamilurbina or Google plus