Cloud Elements (discontinued) vs. TeamDynamix iPaaS

Areas where it would be appropriate:

1. If you want a really 'deep' integration with a third party software, and you want all the control over how it interacts with your software
2. If you want a totally white-labeled solution, that is totally invisible to your customers.
3. if you care more about a well thought out/useful API, rather than a pretty UI

Areas where it is less appropriate:

1. If you want a Zapier-esque hands-off integration for YOU.
2. if you want your customers to do more of the work, pay for it/etc.
3. if you're a really small business, it could be too expensive. But it depends on your individual contract with them.

Incentivized

Its great for enhancing integration and automation capabilities. It has a relatively friendly interface, though needs some improvement. It can feel overwhelming at times. It empowers both IT and business leaders to drive digital transformation effectively.

• Customer Support -- They have a knowledgeable team and are very responsive.
• Communication -- Most questions are addressed quickly
• Documentation -- The API documentation is well organized and easy to follow.

Incentivized

• Makes development possible for those without code experience.
• Lays out options for the team to utilize.
• Provides a visual view of a flow for use.

Incentivized

• There weren't really many cons to our experience. The only slight downside was the cost but they worked with us on that to make it work.

Incentivized

• More documentation for starters using iPaaS.
• Let us use our own HTML.
• Chat bot to ask questions while working in iPaaS.

As developers, we have found that the components provide the same meaning as the programming language construct. We haven't used many of the provided connectors, but the standard connectors are easy to configure for vendor API endpoints that differ slightly from one another.

MuleSoft is also a similar product to Cloud Elements, but is not available as an option in this form.

Workato and MuleSoft are competing cloud API connector platforms that perform a similar function to Cloud Elements. We chose Cloud Elements over them because CE provided a more robust path to unifying the behavior of connected systems.

Zapier is a workflow automation tool that I feel draws erroneous comparison to Cloud Elements that I need to highlight. Workflow automation tools (Zapier, IFTTT, Microsoft Flow) do provide multiple integrations, but for simplistic scenarios where only a handful of explicitly described steps need accomplished. Cloud Elements is a platform for developers to deliver faster and with higher reliability than making integrations one-by-one in complex systems that solve demanding problems.

Incentivized

No real comparison.

• We are able to build integrations in HALF the time we could build them from scratch.
• They allow our development team to spend more hours focused on developing our core product, not connections to other products.
• Their large catalog of services to connect to allows us to spend much less time researching other platform integration endpoints and increases our R&D speed a considerable amount.

Incentivized

• Save time on ticket response.
• Create automated and tailored responses to tickets.
• Gain insights and data on our device activation tickets (we found that 25% of our tickets are for a single ticket, and we created a better-worded KB to facilitate fixes).