The setup and administration for SnapLogic were taken care of by a different team, but in terms of development work where the solution was involved, we can prepare pipelines and from a lower environment those can be moved to other environments, so deployment-wise, it was quite easy particularly when we can export the pipeline into an XML file and upload it into the other environments. That portion was easy and won't take up much time. Deployment activities for SnapLogic are quite easy and doable and won't take much time depending on the number of pipelines in the project folder.

The initial setup is very straightforward. You just need to provision some servers. It's a UE-based tool, so you don't need to install it. Nothing is required. It's ready anytime, anywhere, any place. This is the tag which is given by SnapLogic. As it says, you just need to get your server and put the SnapLogic application inside that server.

Once it is done, you can create your number of users, and they can develop with multiple access levels, like ACL in Azure. Everything can be configured. It's very straightforward. It's not like the older days when you created a software limitation. It's an iPaaS tool, it is an integration platform as a service.

The initial setup for SnapLogic was pretty easy. There were self-explanatory documents available, so setting the solution up was pretty easy. The deployment took less than half a day.

It's both easy and difficult to set up. Sometimes, there are some issues and something which we can't fix. Only SnapLogic can fix certain platform issues. Sometimes issues will be made by the developers, integration developers, et cetera. If we get an issue with the code or something else, then we can fix it, however. If it's something we can handle, then it is very smooth. Otherwise, we have to wait and reach out for help. 

The integration is straightforward, it's easy, and based on the use cases I have dealt with. The setup is very easy.

That said, you need to know what you are doing. There are different user roles that need to be taken into account. 

Often, to finalize the deployment, we need to raise a request and they can action it within a day or within a week. That's typically how long it takes to set up the user roles. 

The deployment was very quick, and very easy.

For the installation part, if you have separate software within SnapLogic and you are able to download the tool from the cloud, it will be best.

One person can manage the product's deployment phase.

The solution can be deployed in five to ten minutes.

I wasn't fully involved in the setup. We have it in the cloud, installed on AWS and we have it installed on GCP. My team says that the initial setup is pretty easy and there is good documentation available. Deployment takes a couple of hours because we do some testing. Upgrading takes a couple of minutes and there's no problem when that happens, we're not even aware of it.

When it is a marketplace, it is seamless, but when it is on our own infrastructure, it involves the launching of the node configurations. If it is a general installation, I do not think it is complex.

The setup is seamless. It just involves a few phone calls and some training. The interface can take a few hours to get comfortable with. While the GUI looks simple, proactive technical problem solvers are needed to really shine.

The initial setup is a five out of ten, so if the staging layer, target, and permissions are all in place when we begin work on a project, then it should take no more than two weeks to deploy.

The initial setup is really simple compared to other tools and technologies. It takes about ten minutes to complete automatic migrations. There is also an option to utilize other tools such as GitHub to directly sync code between environments. 

There are multiple deployment choices that are based on the data and endpoints. 

The full cloud option is maintained by the solution with execution machines that sit in the cloud and require no maintenance. 

If you want to maintain the execution machines and call notes, you have the option to use the solution on-premises behind your firewall. 

The hybrid architecture is a combination of the cloud and on-premises deployment options. 

The initial setup of the solution is very easy. We didn't find any complexities.

We have CSV leaders and have continuous integration for continuous deployment. We put all of our pipelines into the central system and go into production.

The time it takes to deploy the solution depends on the company. The volume of data, latency, or other factors will dictate the amount of time it will take.

The user interface is friendly for initial setup. It is a low-code and very intuitive platform.

Everything seems easy and simple in terms of the initial setup. You're accessing that platform via a browser, therefore, you don't need to set up anything. You can use a predefined environment on the cloud and you can easily install your own ground techs. That means you can install your organization on your server. It's all quite straightforward. It's not particularly difficult or complex.

The deployment is pretty fast and typically takes less than an hour or so.

The initial SnapLogic setup is fairly straightforward. You can set it up in less than one hour. Even 30 minutes could be enough to create an on-prem SnapLogic environment.

There are several potential SnapLogic deployment strategies. Which an organization chooses will depend on its resources. You can create different SnapLogic deployments if you want to have logical separation of different projects or different environments, or you can use different organizations within SnapLogic. An organization is a workspace in the SnapLogic world. You can have physical and logical separation of different environments within SnapLogic.

The solution can be deployed and managed by a single administrator in a small or medium-sized company. Up to three administrators are enough for an enterprise company.

The initial setup for SnapLogic was straightforward.

There was no real initial setup. I went to SnapLogic for a day of training, received credentials, and started.

The initial setup was easy and it took one to two hours to build and deploy it.

It only takes one engineer to maintain this solution.

The initial setup was straightforward.