Camunda vs. Celigo

Camunda Platform is well suited for scenarios where there are different stages in a business flow and the flow is driven by user action at each stage. For example placing of an order on an ecommerce platform. Depending on whether user was able to make the payment or not the workflow would go to dispatch or retry stage. Now the retry stage would trigger further actions like sending follow up emails etc. Likewise, dispatch stage would have a different set of actions. Since every order is important and we need to know where it stands, using Camunda Platform is imperative. Camunda Platform might not be a right choice where just a one off thing needs to be done. For example, uploading of product information by user or periodic processing of heavy images by a worker. These are all either one step processes or periodic automated processes where we can track the status without using a business modeler like Camunda Platform.

Incentivized

Celigo is great for transaction-based integrations (which is most), but not great for when you want to replicate data from one system to a database. For example, if you are trying to get all of your NetSuite data into a Snowflake database. However, if you are trying to get data out of NetSuite and create transactions in another system, it's perfect.

• Task orchestration
• Freeware
• Graphical interface allows normal users to understand business process model diagrams more intuitively

Incentivized

• Error Management is better than anything you can build on your own
• Celigo makes visibility of your data between platforms very nice
• Broad Capabilities. Anything with an API can be connected.

Incentivized

• Documentation - It is usually daunting for beginners because of lack of good documentation
• Simplified setup on local machine for Camunda Server would help developers test changes quickly
• Easier migration from one deployment version of a Camunda process to another deployment version would help in making changes and deploying them faster.
• Heap memory management becomes issue at times resulting in stuck processes. This needs to be resolved.

Incentivized

• EDI transactions are difficult to setup and use
• FTP transactions can be slow when using them for a lot of volume

There is a bit of a learning curve, but not bad. Once you get a flow or two under your belt, there will be no stopping you. You will start to see possibilities and ways to apply automation and integration throughout your business. It becomes fun to look for additional ways to save money, time, and improve accuracy

Incentivized

Camunda provides pretty standard product support offerings.

Had some rough patches in the beginning, but they were resolved.

Incentivized

We demoed some of these other integration options. The learning curve seemed a bit steeper and the offerings less robust, so we did not pursue very far. I cannot speak to the others much. We have not had a reason to stray from Celigo.

Incentivized

• We've built a good business around developing and deploying Camunda for our clients over the last 7 years.
• Our clients are finding it a cost-effective way to try before they buy.
• There's an over-reliance on big offshore outsourcing shops, which hurts ROI and success rates.

• Quickly Sync Sales Order from Shopify to NetSuite
• Sync back order fulfillments from NetSuite to Shopify
• Import order from Amazon Seller Central to NetSuite
• Sync customer information from Shopfiy to Saleforce

Incentivized