Our company uses the solution to handle deployments for new releases. Whenever there is a new release, the solution creates a new provision template for deployment. We also orchestrate and manage all users.

We integrate with other tools like GitHub, Jenkins, or Digital.ai Deploy to manage processing or deployments. 

We currently have 160 users with no plans to increase capacity in the next year. 

Our organization utilizes Digital.ai Release to manage and coordinate the releases of our large integrated system, which includes SQL database upgrades, web application servers, Windows servers, and IIS web services. Digital.ai Release is responsible for orchestrating these releases as they progress from development and testing, through pre-production and eventually to production.

We tested it, but in the end, we didn't purchase it.

We were using it to orchestrate our releases. We wanted to use it for deployment, builds, backfilling, etc.

We were having a hard time determining who would be the practitioners of the product. In the end, one of the things that drove the cost up was the need for so many people to be able to use the tool. There was probably a little learning curve with some of them, but predominantly, our technical leads and perhaps some senior developers were going to use this solution — also, on the infrastructure side, the DevOps team, too. Someone's got to build the release, so the infrastructure DevOps has to set the environment, and then the leads and the senior developers can build the release and supply all the build information to go with it.

We're evolving quite substantially at the moment. Right now, we're probably doing some releases a couple of times a week and we're also moving into some microservices. That probably would have increased our usage with this solution to some degree.