SnapLogic Intelligent Integration Platform (IIP) Pricing Overview

What I like most about SnapLogic is how easy it is to set up and start using—it doesn’t take much time or technical skills, which is perfect for smaller teams or just a few users. We use it pretty often because it saves time and simplifies connecting different apps and data sources. The ease of integration is a big plus—it works smoothly with a wide range of systems, and that really helps non-technical users get things done faster without needing help from developers. The built-in tools and smart suggestions make building workflows quick and smooth. Plus, their customer support has been really helpful whenever we had questions, which makes the whole experience even better. Review collected by and hosted on G2.com.

One thing I dislike about SnapLogic is that the pricing is a bit high for individual like me. Also, while the platform is user-friendly, some of the more advanced features can take time to learn. Occasionally, error messages aren’t very clear, which makes troubleshooting a bit tricky. It would be great if there were more in-depth tutorials or guides for complex use cases. Review collected by and hosted on G2.com.

It is very versatile product, easy to get started and create integrations with many different systems and integration platforms, cloud and on premise solutions.

Time to market is very respected among the business representatives.

Very good possibilities to bridge cloud and on-premise infrastrucutures.

Stable products, having nodes which are headless is a benefit during implementation, easy to scale and move nodes if needed.

Extensibility with custom snaps is also positive where partners can expand with new functionality.

Customer support comes back in a timely manner and helps to resolve issues and provide patches.

We use the product for many different integrations continously, business critical flows are running well. Review collected by and hosted on G2.com.

Structuring objects in pipelines and tasks is not effecient for integrations, it is good for API based flows.

I would prefer a possibility to structure having each integration in an "agreement" which could hold together detection from input channel polling, transformation steps (pipelines) and possibly send/output steps.

In the current setup we have to construct message queue consumers, file pollers and other input channels in pipelines which are either continously running and allocating a lot of resources and slots (due to many sub pipelines in the flow) or executed on schedules.

It would be good to break out and add possibility to have lightweight input channels which can consume from all the possible sources (maybe based on pipelines) and then route the data picked up in to specific agreements/integration pipelines based on detection rules.

I would prefer to have more support for unit testing of pipelines, such as creating test cases for pipelines or parts of pipelines which could be used for validating after changes are done to further strengthen safe deployments in to production.

It is a bit slow to process and develop, we have long processing times of validations which is not very effecient during development.

Further strengthen the integration with git and other source control.

Enable support for backing up data outside snaplogic in the solution. Review collected by and hosted on G2.com.