Share your experience using Plutora

My main use case for Digital.ai Release is to release Azure-related cloud resources like Azure Key Vault and Application Insights to support any cloud integration on the Azure side.

A specific example of how I use Digital.ai Release for one of those Azure resources is that we normally do an annual release to update the certificate for the Azure Key Vault because the certificate expires every year, so we use Digital.ai Release in combination with Jenkins and Terraform to release the new certificate.

In addition to that, I use Digital.ai Release for most Azure resources we use to support our API like Azure Key Vault and Application Insights, application registration, and Redis Cache.

Digital.ai Release has impacted my organization positively because almost all the teams that handle cloud resources related to Azure are using Digital.ai Release in combination with Jenkins. It has become a standard way for us to release cloud-related resources, although we also use Microsoft Azure DevOps for other code releases. For Azure-related resources, this has become the standardized way.

The best features that Digital.ai Release offers are that through the template, I can view the different phases of my release, so everything is streamlined when I use Digital.ai Release, and the integration with Jenkins is very good.

The integration between Digital.ai Release and Jenkins is seamless. If there are any issues and anything goes wrong for a particular environment, I will see a red flag from Digital.ai Release. From there, I am able to have a link which leads me to the log file of Jenkins to view the details about the release, which is very convenient.

I appreciate the way I can create the template using standard artifacts. I have a section for Terraform and a section to define my release using the YAML file, and it is standardized.

Since using Digital.ai Release, one of the benefits is standardizing the way I release to my Azure environment. I could manually do everything, but that is very error-prone, and everybody might do it differently. By following Digital.ai Release, I am following the naming convention already by using a certain configuration file with variables. The best part is standardizing things, which in the long term will help me reduce costs and improve efficiency.

To improve Digital.ai Release, I think the user interface could be improved. For example, I have a plan phase before my build phase, and sometimes the toggle button is hidden. I have to toggle it before the step can be executed, or it will be skipped. Many people who did not use Digital.ai Release before do not even know there is a toggle button, and the first time when they run into that phase, they will definitely skip that step.

Regarding needed improvements, I did not do extensive reading on documentation or training material directly from Digital.ai Release. My knowledge comes from the team who has been using it. However, I would appreciate standardized training material that would give me hands-on experience.

I have been using Digital.ai Release for four to five years.

Digital.ai Release's scalability seems to be adequate, but I do not think we have done anything challenging in terms of capacity for the framework since we are only releasing a few cloud resources at a time, so we might never run into a bottleneck.

Customer support is good, and we did not run into any issues directly with Digital.ai Release's customer support because we have a release team to help us with Digital.ai Release. If we have any issues, we work with that team directly.

Before choosing Digital.ai Release, we changed many different vendors for release management over the years, but Digital.ai Release is definitely the choice for releasing cloud-related resources.

I did not think we used anything else before Digital.ai Release because this has been the standard way of releasing cloud resources from the beginning, especially since we have team members who had this experience to help us establish the framework.

Since using Digital.ai Release, one of the benefits is standardizing the way I release to my Azure environment. I could manually do everything, but that is very error-prone, and everybody might do it differently. By following Digital.ai Release, I am following the naming convention already by using a certain configuration file with variables. The best part is standardizing things, which in the long term will help me reduce costs and improve efficiency.

My advice to others looking into using Digital.ai Release is that it seems very flexible. I understand we are using Digital.ai Release's Jenkins integration, and for the Jenkins component, potentially I could switch to other solutions. It seems to me it is a flexible framework to release cloud-based resources, so it is a good option for this purpose.

I would like to see more AI capability in Digital.ai Release because AI has improved our productivity in different areas of our daily working environment. When we do development using Copilot, I see improvements when we use the cloud to help us in our development. However, in Digital.ai Release, since I am not a frequent user, I do not see much integration with AI yet, and that is an area where I would like to see further development.

I would rate this review as a nine out of ten.

AWS Amplify is utilized in my workflow to streamline application lifecycle development uniquely. I push the code to the Git repository, and AWS Amplify automatically handles the testing and deployment. AWS Amplify is utilized to simplify development and deployment for cloud-based applications, especially in front-end, CI/CD, authentication, and API connectivity. AWS Amplify reduces complexities and streamlines development across both development and production environments.

AWS Amplify has positively impacted my organization by automating building, testing, and deployment, which has reduced manual effort and development errors. It has streamlined collaboration between developers and development teams, accelerating releases and improving application reliability. As a result, we deliver features faster, maintain consistency across environments, and focus on development rather than infrastructure and management.

Specific outcomes I have noticed include faster release cycles, fewer bugs, and increased productivity. AWS Amplify has improved team efficiency through automation in the build and development workflow, with key outcomes including faster release cycles, fewer detectable bugs, and increased developer productivity by reducing manual processes while ensuring consistency in development. My team can now deliver new features more quickly while maintaining application quality and reliability.

The standout features that AWS Amplify offers are the ability to build and deploy applications quickly due to its CI/CD capabilities and seamless integration into AWS services. This integration provides automation in build and development processes, which improves workflow by eliminating manual deployment, ensuring consistency across releases, and allowing developers to focus more on coding. Automated releasing, connected authentication, and APIs provide strong expansion options. AWS Amplify delivers a platform that enhances developer productivity by reducing operational overhead and enables faster application development.

While AWS Amplify is a strong platform, it could improve by offering more granular control, deeper monitoring, debugging capabilities, and clearer troubleshooting guidelines for complex build management and large-scale applications. This would provide optimization for performance and improve efficiency in cloud management. Enhancements such as advanced monitoring, debugging tools, clearer messaging for builds, better cost visibility, and greater flexibility for complex enterprise applications could further support efficient application management at scale.

I have been using AWS Amplify for approximately three to three and a half years.

AWS Amplify is stable in my experience. The platform has provided reliable hosting for front-end development and efficient integration with AWS services. I have experienced minimal downtime, and the automated build and development processes have consistently worked, making it a reliable solution for supporting my development and release workflows.

As my team and projects have grown, AWS Amplify has effectively handled increasing application traffic and a larger codebase without significant issues. The platform's management of infrastructure and integration with AWS services has allowed us to scale efficiently while maintaining performance, reliability, and developer productivity.

I have needed to contact AWS support only a few times for configuration and troubleshooting. The experience has generally been positive, with knowledgeable support, detailed documentation, and timely responses. In most cases, issues have been solved through AWS documentation and community resources, which has reduced the need for direct support engagement.

I used GCP before switching to AWS Amplify.

AWS Amplify delivers a positive return on investment by reducing development and management overhead. My team estimates a thirty to forty percent reduction in development time and a faster release cycle, resulting in higher development productivity. Automation has helped alleviate development tasks, allowing the team to focus on feature development rather than manual operational tasks.

My experience with AWS Amplify pricing has generally been positive, as the pricing model is suitable for small to medium workloads. The cost is based on usage, including hosted services and database data, and there are no complex licensing requirements. This provides better visibility into usage trends and helps my team manage budgets more efficiently as my application scales.

Before choosing AWS Amplify, I evaluated alternatives such as AWS, GCP, Vercel, Netlify, and Firebase. I selected AWS Amplify because of its seamless integration with AWS services, built-in CI/CD scalability, and simplified management for both front-end and back-end resources, which best fit my existing AWS-based architecture and development workflow.

I would recommend AWS Amplify for organizations looking to enhance application development on AWS. It is particularly valuable for teams that want to simplify hosting, automate builds, and ensure seamless integration with AWS services. The platform helps reduce operational overhead, improve developer productivity, and deliver applications faster while maintaining scalability and reliability.

AWS Amplify's AI capabilities are generally accurate and reliable for common development tasks, such as code generation, application scaffolding, and integration assistance. However, outputs require human review and testing for complex business logic, as these features need flexibility in development.

I would rate this review nine out of ten.