Share your experience using Plutora

Akuity Platform is our main platform for CI/CD, as all deployment and everything is done on Akuity Platform for our whole product.

We use Akuity Platform daily. I am on the software side, but I have also worked with it, mostly observing DevOps people working on Akuity Platform. They configure new features on Akuity Platform, and on a day-to-day basis, whenever there is any change in our product, the CI/CD gets triggered, and that is how we use it daily.

In our case, having a great UI on Akuity Platform is something that we love. We have also used the open-source version, but Akuity Platform, the paid version, has a very great UI and user experience through which we can easily do whatever we want to, and that is what I love most about Akuity Platform.

The UI and user experience of Akuity Platform is better than the open-source version because the open-source version has only the bare minimum on the UI, but in Akuity Platform, they have almost all the features that we want. I have seen that on the open-source version, for the source we just give the GitHub link where the Argo CD workflow is specified, but on the UI of Akuity Platform, we connect our organization there, and they give all the options for the projects that we want to tag on, so that is one of the features that I love on Akuity Platform version.

Overall, Akuity Platform has impacted our organization positively as the DevOps team is quite happy because first, they do not have to manage their own Argo CD, and second, it is quite user-friendly for them as well as for the developers, saving time for us. For the DevOps folks using Akuity Platform, they have saved a good amount of time considering they do not have to deploy Argo CD and they just get everything working, so that is quite helpful.

In our case with Akuity Platform, we observed that we required less time due to the DevOps team needing less time to manage things, so for us, it was a time saving.

Akuity Platform has most of the features, but I think they should include some more features, such as the feature where we specify the URLs of the Argo CD workflow, which I liked, but it would be good if they include more of those features on the platform.

Integration with Akuity Platform is quite good as they have integrations with almost all the related CI/CD products, but I think in terms of performance, they can improve upon that because sometimes it does get laggy, maybe due to high pressure, and anything can be the reason for that, but they can improve on the performance part.

We have been using Akuity Platform for around three years now.

Akuity Platform is stable for our team. Till now, we have not faced any downtime.

Akuity Platform handles scalability well and can handle growth and changes in our workloads easily.

Customer support for Akuity Platform is quite good as they are really helpful whenever we get stuck.

We were using the open-source version earlier, but we found that it was taking quite an amount of time for us to manage, which was a constraint, so we switched to Akuity Platform to avoid management and just use it directly.

I think the pricing of Akuity Platform is a bit high, and we have a budget constraint at our company, but I think it was worth the price that we pay to get it working.

Before choosing Akuity Platform, we evaluated another CI/CD tool called Flux CD, which we found useful, but it was not that helpful in our case, so we just went with Akuity Platform.

I would rate the customer support of Akuity Platform on a scale of one to ten as an eight. Akuity Platform team is really helpful, so there is not much difference there. My overall rating for Akuity Platform is eight.

My main use case is accelerating full-stack app development. For example, I built a React app that needed user sign-in, a GraphQL API, and S3 storage. AWS Amplify allowed me to set up all of that quickly. Authentication with Cognito, AppSync for the API, and S3 for media cut down back-end setup time drastically.

AWS Amplify has positively impacted my organization by significantly reducing our development cycles. In one case, we shortened time to market by about 30% for a web app. It allowed our team to focus more on features rather than infrastructure. We also saw better collaboration between front-end and back-end developers. Overall, AWS Amplify helped us iterate faster, which ultimately improved customer delivery timelines.

AWS Amplify improved collaboration between my team members by bridging the gap between front-end and back-end teams. Front-end developers could easily define data models and authentication without waiting on custom back-end code. It fostered quicker feedback loops. Front-end changes could be deployed rapidly for testing. Also, the shared environment management meant we had clear separation between dev and production. The result was that teams worked in parallel, sped up iterations, and reduced bottlenecks in the process.

Another standout feature of AWS Amplify is its DataStore. It simplifies working with distributed data by offering real-time and offline capabilities out of the box. It automatically syncs data between your app and the cloud, making it ideal for apps that need to work offline or handle real-time updates. It ties into AppSync and GraphQL, so data management becomes even easier.

What I appreciate most about the DataStore feature in AWS Amplify is its offline capability, which is a game-changer. Being able to seamlessly sync data once the connection is restored means users get a smooth experience. Plus, the real-time updates mean collaborative apps stay in sync. Combined, these two elements are what make DataStore shine for modern, responsive apps that can handle network instability without custom logic.

AWS Amplify could improve by offering more flexibility in complex enterprise scenarios. For example, when you need advanced custom authentication flows or fine-grained access control, it can be limiting. Also, some debugging around auto-generated resources could be clearer. Another area is deeper integration with existing infrastructure as code, so larger teams can blend it into broader pipelines more seamlessly.

One pain point I have is when I outgrow the default patterns in AWS Amplify. As apps scale, having more granular control over back-end infrastructure, like custom VPC setups or complex network configurations, is not as straightforward. I would love to see tighter integration with CloudFormation or CDK for smoother transitions when custom infrastructure is needed. Also, improved visibility and debugging of AWS Amplify-generated resources would be welcome.

A smaller improvement I would love to see in AWS Amplify is more intuitive error handling during deployments. Sometimes AWS Amplify deployments fail without clear messaging, especially with build configurations. Better visibility into detailed logs would help. Also, more built-in CI/CD customization options for multi-stage environments would be a welcome addition.

I have been using AWS Amplify for roughly two years.

AWS Amplify is stable. In our experience, it is reliable for production use. We have not faced major outages and AWS keeps improving it. It is a managed service, so it scales well and maintains consistent performance.

AWS Amplify scales well for typical web and mobile apps. It leverages AWS infrastructure, so resources scale as traffic grows. For customer support, it is AWS standard. There is a lot of documentation, but for direct support, you will rely on AWS support plans. In short, it is solid, though direct, personalized help depends on your AWS support tier.

I would rate the customer support of AWS Amplify around a 7. The documentation and community resources are strong, but direct personalized support really depends on your AWS support plan.

We previously relied on a combination of manual CloudFormation, Lambda setups, and custom CI/CD pipelines. We switched to AWS Amplify for its streamlined workflow and the speed of integrating front-end and back-end. AWS Amplify's abstraction reduced boilerplate, allowing us to move faster on smaller projects.

AWS Amplify helped me speed up the back-end setup by simplifying things through automation and out-of-the-box components. The CLI let me create authentication flows with Cognito in minutes, with no need to manually configure user pools or federations. Similarly, defining a GraphQL schema and letting AppSync auto-generate resolvers was a huge time-saver. The pre-configured CI/CD pipeline for hosting meant every git push triggered a build and deployment automatically. This all reduced the need for deep infrastructure provisioning, letting me focus more on app logic.

We saw a clear return on investment with AWS Amplify, especially in time saved. In one project, we reduced back-end setup by roughly 40%, cutting weeks of work. That meant fewer engineering hours, allowing us to deliver faster. While we did not reduce headcount, we avoided needing extra back-end specialists on smaller apps. In terms of cost, the quicker development cycles meant earlier launches, which in turn boosted revenue sooner.

The pricing model of AWS Amplify is straightforward pay-as-you-go, which worked well for us. Setup cost was minimal since it is fully managed, with no large upfront investment. Licensing is not really a factor as it is part of the AWS service lineup. The biggest factor is scaling costs. If your app grows, storage, API calls, and hosting can add up. But early on, it is cost-effective and predictable.

We evaluated other options including Firebase for rapid development and using raw AWS services such as API Gateway and Lambda. We chose AWS Amplify because it balanced ease of use with the flexibility of AWS. Firebase was simpler, but we wanted stronger AWS ecosystem integration and more control over scaling.

I would advise starting with smaller projects or prototypes to grasp AWS Amplify's capabilities. Leverage its strengths in rapid setup, but ensure you understand when you might outgrow it. Plan ahead for more complex infrastructure needs. And definitely align your team on AWS basics; it is smoother if you are already comfortable in the ecosystem.

AWS Amplify shines when speed matters, especially for front-end heavy apps. But always keep an eye on when your complexity might need deeper AWS control. I would give AWS Amplify an overall rating of 8.