The initial setup was straightforward; maybe a bit uncomfortable because you have to build your own ConfigMap application so that you're able to produce all these configs. They don't have any support tool or similar.

The product's initial setup phase is very easy.

My company has taken NGINX App Protect's license from F5, so we received the necessary support for installation. The installation of the tool was very easy for our company.

My company could take care of the deployment of NGINX App Protect with some .deb files. The Debian file was available on the website of F5 that we installed on one or two machines in our environment, after which some configurations were required to be done so that we could use NGINX App Protect.

The solution is deployed on an on-premises model.

The solution is easy to deploy. Its scalability and integration capabilities depend on its performance and the extent to which you want to integrate it into your development process. It doesn't necessarily cost more money beyond the initial setup.

You need to identify the placement. You must understand your application. Lastly, you should assess which NGINX features are suitable for the functionality you wish to implement. This initial phase involves analysis.

Following the analysis, you proceed to the test deployment stage. Subsequently, you enter alert mode and finally enable NGINX App Protect. It's a simple deployment. A single engineer can do the job.

The setup of NGINX App Protect is complex. The full process took one week to complete. Additionally, we had to change the network infrastructure platform which took one month.

I rate the setup difficulty of NGINX App Protect a four out of five.

The product's initial setup phase was easy.

The initial setup was complex in terms of deployment and fine-tuning.

We have more than ten applications so it took us between four and five months to deploy.

The initial setup is straightforward. For deployment, we configured basic configuration, and after mounting, We observed our application for almost four months. After that, we proceed to enforcement blocking mode. Typically, all our applications are live, so we can't block it on day one. We observed it for a long time, like six months, and then we went into step-by-step blocking mode.

Three people are required for the solution's deployment.

The initial setup of NGINX App Protect is basic. The full deployment took approximately one day.

The initial setup was simple and took three to four days.

The initial setup of NGINX App Protect is easy. It took us a couple of days maximum.

The initial installation is very simple. However, there is one issue with security certificates.

Any system that you publish that is a secure system needs to have a certificate implemented, and that is always a struggle. We have plenty of customers with this solution, and every time that we get to the step involving the certificate, extra work is required. It never works smoothly. You always have to go and manipulate the certificate and the system just to set it up. I'm not sure about the latest systems, but in the old models, this could not even be done through the GUI. You had to use the command line, even though the certificate is visible in the GUI. A combination of commands is required just to make it work.

The length of time to deploy a basic system is very short. For more complex scenarios, it can be a long process.

Initial setup was easy. For the implementation, it takes no time, but it takes some time to learn, understand the traffic, and to build the policies according to the traffic of the applications already implemented.

We have two employees for maintenance. 

The implementation process is not simple. If you have more than one, the policy must be created from scratch in YAML files, which is not automated and takes time.

The initial setup was straightforward but I am well versed in this implementation. If I was a novice, it would be difficult. We have pretty much automated all our deployments, and then we schedule a downtime for our apps and deploy the patches or the new versions through automation so it'll take a lot less time.

The initial setup of NGINX App Protect is simple.

Yes, it was pretty easy as far as I remember. So this company, everything was previously set up and we had all the predefined user scripts so even though we had come to set it up from scratch.