The initial setup is straightforward. It usually takes around three months. 

I rate the ease of setup a six out of ten. It depends on our technical maturity. If someone hasn’t been exposed to technically challenging solutions and scenarios, Saviynt will be difficult. The product is deployed on the cloud.

The initial is very straightforward. It takes a day to complete. The deployment process involves requesting Saviynt to fetch a tenant and download the component we need to install for the on-premise version. We can also deploy it on the cloud and integrate it as per requirements. We can use it once the connectivity is done and firewall ports are open.

We require one manager, one senior consultant or senior architect, and two to three developers to execute the process. However, the number of technical staff members depends on the use cases and time frame.

Saviynt handles all aspects of installation and deployment for us. As a SaaS product, we have no control over product upgrades or installations.It's a SaaS product, not deployed as SaaS. A tenant is essentially an instance created for each of our customers, provided by Saviynt itself.

It is difficult to implement Saviynt. The challenge is that it's very hard to find people who are experienced in the use of this product.

The initial setup is easy. We use a SaaS-based model. 

Saviynt's setup was easy and took two months to complete. Setup is fast but took time for us because we are not a small organization. 

The initial setup to open the connectivity between Saviynt and the client requires the networking team to be onboarded properly. They have to understand both environments. It's a pretty standard process. 

The initial setup for Saviynt is pretty straightforward. It's not a complex setup. 

How long the deployment of the tool would take depends on the application level. If any of the applications need background checks, whether it's for the database or it's for the services, most of them you can do in a day. If everything is set up, meaning all the firewalls have been set up and the background checks have been done, then most of the time, it only takes a few hours to complete the deployment. That is apart from RESTful because with RESTful, you might face some issues based on recent access token issues. If there are no issues, deployment won't take up that much time.

The initial setup is quite difficult but does not take much time.

This solution is easy to implement, although our requirements were bulky so it took about four months to deploy.

Saviynt has a complex design. I rate the initial setup process a seven out of ten.

It was easy. It was not that complex.

It was an easy implementation because it is a SaaS product. You just have to click and plug in place. You can get a tenant directly from the Saviynt, which can be a working one. Then, you have to work on the networking, and it will work.

It takes one to two weeks to deploy if we get a good tenant from Saviynt. Then there are always firewall settings, and everything generally takes time in the SaaS product, depending on whether there is a need for a multi-tenant or a JD. Those things take a little time since we only work as a service. Therefore, how we deploy depends on the client.

How complex the initial setup is mostly depends on the size of the organization. The more complex the organization, the more complex the initial setup. The level of difficulty is also related to scoping - for example, how do you define your manual viable product, et cetera? That's quite difficult to answer. That said, the implementation is not that difficult. It's more about configuration.

We have our own internal team that handles deployment and maintenance. 

I would say that the setup was of medium complexity but it was not difficult. There are more complex products available, like Oracle, IBM, and others, so it's definitely better than those.

The setup is as complex or straightforward as the customer needs it to be. It's generally easy to get started, but like any system, if the client is complex in requirements, then generally it takes a lot more effort to get set up. Saviynt is good if you've got fairly straightforward requirements. It goes in quickly and easily. But as soon as you get some variations and complexity from the customer, then that takes customization, which is always involved. That's not a criticism of the platform, it's just the nature of the project.

You would certainly need specialist skills to deploy the solution.