The initial setup was easy. I rate the ease of setup an eight out of ten. The deployment takes close to two weeks.

The solution is deployed on an on-premises model since my company has its own network.

The initial setup is moderately hard because the documentation is not available. If someone is gathering the documentation and creating custom documentation for the organization, explaining how to connect to the CI/CD pipeline and create an account and everything in between, then it's not difficult. The initial investment in developing the documentation is quite tedious.

We provide an initial onboarding period of two weeks to the deployment team. The team can deploy the solution at its own pace, provided it follows the documentation. The team also has early life support throughout these two to three weeks, in which the team members also get trained and understand how to make the best of the tool’s features.

The deployment time depends on the organization’s application architecture, where they keep their projects, and how they are organized. These variables can extend or decrease the timeline for implementation. We need one or two technical resources to deploy the product.

Black Duck is easy to install. The full implementation took a couple of hours.

The initial setup for this solution is straightforward. It is Dockerized, and very easy if you use Linux. If you have a server on Azure then you can just go to the Azure marketplace and spin it up straight from there.

If you are using an instance on Google Cloud, for example, we've done deployments where you simply spin up the application and it deploys by itself in about four minutes. If you have to deploy by yourself, you have to wait for Linux to completely finish, etc. But if you're using a cloud service provider then it is automatic. You put in your license and you integrate it with whatever you want to do.

Once it is deployed, it is again straightforward. You can easily take your build, use the Hub Detect to scan it and get a JSON file, then upload it to the server. It will do the analysis and it is usually fast, except sometimes when you want to check code snippets. 

It does not require more than one person for deployment and maintenance.

We didn't do the setup. They did the setup. My guess is that it is not so easy because it's done in the docker environment. For its maintenance, we need two people.

The initial setup is super simple for the user because it is set up on the cloud. You just get an account and upload the code. You don't have to install it. There is no deployment. You just access the service from the cloud.

The complexity of setup depends on the scale. If it's an out-of-the-box scan, it's basically scaled for the port, but once we started to utilize it, we wanted a system that automatically scaled up, so we moved to Upper Shift. It was challenging and required some support from their R&D. Then we applied integration, which required consulting with experts. You can use their documentation and set up your own software, it works smoothly. but depends on the size of the setup.

The product requires someone familiar with the tool. It's not that complicated, but it's not intuitive to find your way through the tool easily. There are two kinds of setup that I am aware of in Black Duck. One is a complete SAS solution where you upload your software to the cloud. Alternatively, you have your on-premise hub, which is attached to the knowledge base. This is a secure solution and can be compared with the knowledge base. The way this hub communicates outside is very important because it needs a stable and wide metro connection.

The initial setup is complex. It is installed and configured on a Linux-based system, and the on-premises database needs to be updated.

Upgrading our version of Black Duck to the most recent is a tedious process. It is very step-by-step and very manual.

I rate the tool's deployment a seven out of ten. 

The initial setup isn't too difficult. It's a pretty straightforward, simple process. We have only installed it once, and I cannot recall how long the deployment actually took. It was a long time ago.

The initial setup is unique. We're actually migrating from our current Hub to Black Duck Hub. It has its own specific challenges.

The initial setup is complex.

We had some issues finding the report.

The length of deployment is different, it varies on the requirements.