SnapLogic vs. TeamDynamix iPaaS

Snaplogic is unique from other IPASS tools if you're very sensitive about data security as they have an on-premise option where your data never needs to leave your data center. And data pipelines can be quickly created if Snaplogic has the requisite connector to your data sources. On the downside, if you're transforming a large amount of data for example in training machine learning models, a tool with elastic compute capability is more appropriate.

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.

• Easy access to any type of source system. Data could be in any format.
• Very beautiful visual representation of transforms that makes it super easy to use it by any non developer.
• It can be run in cloud or on-premise. helping you choose your comfort of security.
• Has pretty good customer support and have recently started their community forum as well.

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

• They need to have a way to connect to GitHub to allow the users to maintain their version control in GitHub. This is a missing functionality.
• As pipelines become complex, it's difficult to have all the snaps stitched together - just like to see it done differently.
• They do not have a way to start/stop a preview. This is hard to use, especially if you have to stop an accidental preview invocation.

Incentivized

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

This has been hands down the BEST software company I have ever used and dealt with. I am a 25 year IT veteran at this college. They go above and beyond in soliciting our feedback/input and proactively follow up about bugs, issues, etc. I have given multiple potential clients my thoughts and after seeing the SL demo they all sign up. I appreciate their support model, it's REFRESHING!

Incentivized

It is very powerful but has a steep learning curve

Incentivized

Intuitive "Pill-Based" Data Transformation: Moving and formatting data across disparate platforms has traditionally been a syntax headache. TeamDynamix simplifies this by utilizing selectable data "pills," allowing users to click and visually bind fields—such as stitching a "First Name" and "Last Name" payload together—in seconds.

They can be prompt but they have not been as useful as I've wanted. We had a bug that affected many of our customers through an API connection between SnapLogic and our platform. Eventually they were able to figure it out, but it took a long time of negotiating between our engineering team and theirs. Additionally, we installed the SnapLogic groundplex for our customers and we've run into a bunch of problems of connectivity. If SnapLogic offered to be on those calls with our clients to troubleshoot how to fix these problems, I would give them a better grade here.

Incentivized

The groundplex in our VPC is very nice for security reasons and the SnapLogic team was extremely helpful during our implementation

Incentivized

We opted for SnapLogic due its ease of use and the flexibility it offers, it was the platform that was strongest in both application integration and data integration and both were use cases we wanted to be able to cover.

Boomi is expensive, has limited connector licenses, and is harder to write an integration.

• We have cut development time down by at least 70%
• The software was more on the expensive side at renewal which required some further approvals to be sought for the spend
• More developers are able to build and use Snaplogic pipelines in their projects

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).