DuploCloud | Agentic AI DevOps Platform on AWS logo

    DuploCloud | Agentic AI DevOps Platform on AWS

    Sold by
    DuploCloud is the agentic AI DevOps platform for AWS, powered by Amazon Bedrock. Pre-built agents for Kubernetes, CI/CD, observability, security, and compliance, self-hosted in your AWS account. Integrates natively with the AWS MCP Server.

    Ratings and reviews

    4.5
    49 ratings
    78%
    18%
    0%
    2%
    2%
    4 AWS reviews
    |
    45 external reviews
    External reviews are from G2 .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (49)
    Pedro V.

    Great for DevOps support and better Security

    Reviewed on Nov 12, 2026
    Review provided by G2
    What do you like best about the product?
    That we always have someone available to report devops/security issues related to infrastructure

    And also the help we have had developing our devops configuration in our own repositories (CI/CD, SOPS for secrets, etc)

    We like that we don't need to provide a huge amount of context everytime we report something
    What do you dislike about the product?
    Downsides are mostly related to having the extra security layer that is required for our company, since it involves relying in VPNs and short lived tokens for more of developers day to day, but I assume is expected
    What problems is the product solving and how is that benefiting you?
    It's helping us maintain security at the level we need for SOC2 and HIPPA compliance, and also on devops features in general
    Information Technology and Services

    DuploCloud Speeds Up Infrastructure and Compliance for Our Small Fintech Team

    Reviewed on Nov 10, 2026
    Review provided by G2
    What do you like best about the product?
    What I like most about DuploCloud is how much it takes off our plate on infrastructure. As a developer on a small fintech team, I don’t have to write and maintain Kubernetes manifests for every change. I can spin up services, set environment variables and check logs from the DuploCloud UI without waiting on a DevOps engineer. That has cut the turnaround on things like creating a new environment or changing a service config from days to hours.

    The compliance controls built in at the infrastructure level are another big plus for us. Since we handle lending data, it helps that things like encryption, access controls and audit logging are set up by default and not left for us to remember. Their support team has also been quick to respond on Slack when we hit an issue, which matters when something is blocking a deploy.
    What do you dislike about the product?
    Login experience has sometimes been bad for me, I get stuck on the login page. Terminal inside a pod also gets stuck very often.
    What problems is the product solving and how is that benefiting you?
    Before DuploCloud, our infrastructure work depended on a few people who knew the cloud setup well. Creating a new environment, changing service settings or troubleshooting a deployment often meant waiting on them, and every change needed hand-written infrastructure code and careful review. For a lending platform that has to stay secure and compliant, that was slow and risky.

    With DuploCloud, developers can do most of this themselves through one interface: deploying services, updating configs and env variables, checking logs and setting up new environments. Security and compliance settings come built in, so we spend less time on audit prep and worry less about a misconfiguration slipping through.

    The result is that we ship faster and our engineers spend more time on product work than on infrastructure.
    Jocelyn K.

    Fast, Responsive DevOps Team with White-Glove Slack Support and Great Value

    Reviewed on Nov 09, 2026
    Review provided by G2
    What do you like best about the product?
    Extremely fast and responsive and very knowledgeable about devops infrastructure. Their team is lean and flat which is great to work with especially when you are a fast paced startup, as they move very quickly. Their CTO and Chief Customer Officer are constantly involved in Slack with us which is very impressive to me, and feels like white glove treatment. Great price and value considering you are essentially getting an on-demand DevOps team while also benefitting from their infrastructure and managed service. All their engineers seem knowledgeable and are pleasant to work with.
    What do you dislike about the product?
    No major dislikes really. They are iterating on their product line and have been trying to pitch an AI tool they built inhouse to us, but I haven't seen the ROI or value add of this yet. However they are definitely not obnoxious about it and are very transparent about what they are doing, which I appreciate it. No disruption of their core offerings to us.
    What problems is the product solving and how is that benefiting you?
    DevOps and security. This is extremely important to us as we work with very high profile clients that have strict security demands, and so we had to move fast and effectively in order to service them as a small company. They gave us an entire managed platform almost out of the box and handled our entire deployment. They are also on hand for any production or security issues.
    Travis C.

    Effortless, Secure Cloud Infrastructure Provisioning with Fast, Helpful Support

    Reviewed on Nov 09, 2026
    Review provided by G2
    What do you like best about the product?
    I really like how easy it is to quickly wire up new cloud infrastructure. If I need a new database, message queue, blob storage, etc. in a specific tenant, I can get it up and running securely with very little effort. Duplo also makes it possible for less experienced engineers to contribute to our Cloud Ops work, which helps the team move faster without sacrificing consistency.
    What do you dislike about the product?
    I honestly don’t have any dislikes or pain points. I’ve been working extensively in the system over the past year, and whenever I’ve run into a speed bump, the team at Duplo has been quick and happy to help resolve it.

    I can say at times the Documentation can be slightly out of step with our version of the UI/System.
    What problems is the product solving and how is that benefiting you?
    We don’t have a dedicated DevOps/CloudOps team, and our engineers aren’t very experienced with Ops. Duplo lets us move quickly by focusing on what we do best: software development and delivery.
    Ryan B.

    Easy Infrastructure Management with Attentive Support

    Reviewed on Nov 09, 2026
    Review provided by G2
    What do you like best about the product?
    I find DuploCloud very useful. The people are great and attentive, the work is top notch, and the product continues to grow in its offerings. I value the main app and CLI, and setup was very easy. I suspect my use case doesn’t even scratch the surface of DuploCloud’s offerings.
    What do you dislike about the product?
    I haven’t had any issues in my experience. Setup was very easy, though it took longer than the discussed deadline, which I expected was too aggressive.
    What problems is the product solving and how is that benefiting you?
    I use DuploCloud to manage our startup’s infrastructure and compliance.
    reviewer2817048

    Migration has stalled and billing and support issues have forced us to resume managing infrastructure

    Reviewed on Jul 29, 2026
    Review from a verified AWS customer

    What is our primary use case?

    I undertook the migration of our production application to AWS, with DuploCloud handling DevOps, infrastructure setup, and ongoing support.

    How has it helped my organization?

    It did not improve our organization. We contracted DuploCloud to migrate us to AWS and manage the infrastructure. After nearly two months of onboarding, we never reached a working production environment.

    What is most valuable?

    No features reached production for us. The individual engineers were capable, but the platform and the engagement model did not deliver.

    What needs improvement?

    There should be transparent, contract-consistent billing, right-sized environments for startup workloads, and support SLAs that are actually met. A testing and validation process should be followed before anything is called delivered.

    For how long have I used the solution?

    I experienced roughly two months of active onboarding; the contract dispute has now run over a year.

    Which solution did I use previously and why did I switch?

    We managed our own infrastructure previously. We engaged DuploCloud to accelerate the AWS migration and have since gone back to doing it ourselves.

    What other advice do I have?

    Startups should be especially cautious. In our experience, the platform was not production-ready for our use case. Support disappeared mid-engagement, and disengaging was far harder than signing up. Verify every commercial term in writing and confirm delivery milestones before any payment obligation begins.

    If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

    Amazon Web Services (AWS)
    Arka Sarkar

    Self-service cloud automation has transformed our compliant microservice delivery speed

    Reviewed on May 22, 2026
    Review from a verified AWS customer

    What is our primary use case?

    The main use case for DuploCloud in my organization is to enable developer self-service for infrastructure provisioning and application development without sacrificing our security and compliance posture. Before DuploCloud, if a development team needed a new microservice environment, an AWS RDS database, or an S3 bucket, they had to open a ticket with the central DevOps team. This created a bottleneck that could take days or weeks. With DuploCloud, we can provision these resources independently in minutes through a simplified UI and low-code Terraform, while DuploCloud automatically handles the complex and low-level cloud architecture behind the scenes.

    DuploCloud uses the concept of a tenant, which is an isolated workspace and trust zone, and we use tenants to instantly spin up isolated sandbox, staging, and production environments. These are the primary use cases for my organization.

    The no-code interface has transformed our ticket-driven team into a self-service team, particularly in our charging domain as a boss product, because at Ericsson, we only deal with telecom charging products in our case. It eliminated the repetitive low-level configuration hurdles and allowed us to focus entirely on feature code. Before DuploCloud, every piece of infrastructure required writing manual scripts or waiting on a DevOps engineer.

    The UI democratized cloud access. It did not eliminate the underlying complex infrastructure such as VPCs, IAM roles, or namespaces. Instead, it turned DuploCloud into an automated expert that does the heavy lifting based on simple forms we fill out. If my team needed to spin up a new microservice earlier, that required a secure backend container, an Amazon S3 bucket for file storage, and an AWS RDS database. Previously, we would open a Jira ticket for the infrastructure team, and a DevOps engineer would spend hours on that task. If a single configuration role was missed, the deployment would fail or worse, create a compliance violation. The loop took anywhere from three to eight days. When using DuploCloud's graphical interface, we can do the exact same thing safely in under ten to fifteen minutes without needing a dedicated DevOps engineer. We just create a tenant and provision the database, bind the S3 bucket, and deploy the container. That is all that is required. The biggest shift is that we no longer babysit infrastructure or log into cloud consoles to stitch things together from a single pane of glass with reduced risk.

    For service malfunctions or component failures, an engineer does not have to dig into Kubernetes YAML. They can check the live logs, look at the built-in metrics, and trace the deployment history directly from the DuploCloud dashboard. These are the key benefits.

    What is most valuable?

    One valuable feature is tenant-based isolation and multi-tenancy. This is the foundational architecture of DuploCloud and its single best feature for daily tasks. It abstracts cloud environment into tenants, which are isolated trust zones. When we create a tenant for a specific project or microservices in our charging products, the underlying VPC subnets, routing tables, AWS security groups, and namespaces are automatically configured.

    The no-code UI paired with a low-code Terraform provider is one of the key advantages of using this platform, as it gives us the best of both worlds depending on comfort level. It offers a clean graphical interface to provision complex cloud services such as AWS RDS, S3, or EKS clusters without needing deep cloud expertise. For advanced infrastructure as code workflows, it features a specialized DuploCloud Terraform provider.

    The turnkey continuous compliance engine is another key feature. The platform has a rule-based engine mapped to strict compliance standards such as SOC 2 and HIPAA. If we deploy an application or storage bucket through DuploCloud, the platform automatically applies required controls such as forcing encryption at rest, enabling logging, managing backups, and setting up alerting and monitoring.

    What needs improvement?

    The most objective critique I can give of any low-code abstraction tool is feature latency. Major cloud providers such as AWS and Azure release dozens of new services, instance types, or deep granular configurations every single year. Because DuploCloud sits as a translation layer between the engineer and the cloud provider, there is naturally a slight lag before those brand-new features show up in DuploCloud portal or in its custom Terraform provider. If our team wants to experiment with a newly launched AWS machine learning instance type or a highly specific EKS feature, sometimes we have to wait for DuploCloud to build it into their UI or find a temporary workaround via native cloud consoles.

    While DuploCloud is designed to make standard compliant infrastructure setups incredibly fast, sometimes edge cases can happen. The platform does a fantastic job of automating the ninety percent use case, but if an application requires a highly exotic legacy network topology and unconventional Kubernetes Ingress configuration, fighting against the platform's rigid safety guardrails can sometimes feel restrictive, which we faced in one of our testing projects last year. The UI simplifies everything, so when we actually needed to inject the raw, highly complex native Kubernetes YAML modifications, the escape hatch to override standard rules can sometimes have a learning curve, which we have already faced. Streamlining how advanced overrides to default settings work without breaking the compliance engine would be a great user experience improvement.

    The platform actively monitors for compliance drifts and logs system configuration perfectly. However, the searchability, filtering, and reporting element inside the administrative audit log UI could be more intuitive.

    For how long have I used the solution?

    I have been using DuploCloud for nearly four years.

    What other advice do I have?

    Moving away from a ticket-driven DevOps culture means actively encouraging developers to embrace self-service. Do not just hand them the platform login; train them to understand that they now have the power and responsibility to provision their own isolated tenants and resources safely. When you remove the infrastructure middleman, you unlock massive team velocity, but the development team needs to be onboarded smoothly to build that confidence.

    You need to map out your environment boundaries and isolation strategies early because DuploCloud relies on the concept of tenants to build its security perimeters. Plan your application architecture around this logic right from the start. Do not treat no-code and code as enemies. While the graphical interface is amazing for quick setups and troubleshooting, do not completely abandon infrastructure as code.

    DuploCloud allows us to get the maximum value out of the vendor relationship, treating them as an extension of our infrastructure strategy rather than just a software utility, while maintaining a clean boundary as an independent enterprise customer. This is an important tool in today's technology landscape. I rate DuploCloud eight out of ten based on the improvement areas I have mentioned.

    Raman S.

    Robust DevOps Automation with Few Restrictions

    Reviewed on Dec 08, 2025
    Review provided by G2
    What do you like best about the product?
    By lowering reliance on DevOps personal, Duploclud boots developer productivity. while making sure everything is safe and compliant, developers can self-service deployments.
    What do you dislike about the product?
    After significant cloud provider changes , a few sophisticated cloud native capabilities take some time to show up in the platform
    What problems is the product solving and how is that benefiting you?
    DevOps bottlenecks are resolved by it. The platform allows developers to self-serve the majority of infrastructure chores, which shortens wait times and speeds up development cycles.
    Akash Sai R.

    Effortless Application Deployment, Needs a UI Refresh

    Reviewed on Nov 19, 2025
    Review provided by G2
    What do you like best about the product?
    I find DuploCloud incredibly easy to use, especially for managing clusters, nodes, pods, and automating various tasks. The ease with which I can deploy applications and manage tenants is a significant advantage, saving me time and effort. I particularly appreciate the ability to easily connect securely, which enhances our operational security. The capability to handle CI/CD for different environments seamlessly is invaluable, as it simplifies our deployment pipeline and boosts efficiency. The automated CI/CD deployments save time and reduce manual errors, which is crucial for maintaining workflow consistency across various environments. Additionally, the onboarding process for new services and tenants is straightforward, requiring only a couple of steps, which reduces the learning curve and facilitates faster integration and productivity. Overall, DuploCloud makes complex management tasks more straightforward and efficient, contributing positively to my daily operations.
    What do you dislike about the product?
    I find the UI interface of DuploCloud to be a bit outdated, although it does serve its functionality.
    What problems is the product solving and how is that benefiting you?
    I use DuploCloud to manage clusters, nodes, and pods with ease, automating CI/CD deployments for various environments, saving time, and simplifying tenant management.
    reviewer2770632

    Have faced unexpected platform limitations but have benefited from a smooth migration experience

    Reviewed on Oct 22, 2025
    Review from a verified AWS customer

    What is our primary use case?

    We were initially using Heroku but wanted to migrate for more granular control and cost savings.

    How has it helped my organization?

    This did not necessarily improve things as much as move us sideways. The initial project to migrate us went well, but we now have additional maintenance and administration costs that balance the cost savings from the cheaper infrastructure.

    What is most valuable?

    Their initial onboarding and migration service was great. A lot of effort was put into getting things working, and the process was also relatively quick.

    What needs improvement?

    There seems to be significant effort toward vendor lock-in. During the sales pitch, we were told it would be very easy to turn off Duplo and its software, but upon closer inspection, the workflows make use of vendor-specific software without a technical reason. The backups are vendor-specific for disaster recovery unless one specifically requests otherwise. They also use their own Terraform provider, which does not provide any advantage over the generic providers. The software portal can be quite buggy. Although some fixes have been done over time, the root causes were not resolved. The panel does not support everything, so features like termination protection are missing. Additionally, automated services running on the portal have performed unexpected actions, such as deleting RDS instances.

    For how long have I used the solution?

    I have used the solution for one year.

    Which solution did I use previously and why did I switch?

    We used a PaaS vendor that was increasing costs and reducing features and services.

    What's my experience with pricing, setup cost, and licensing?

    It is important to read the contract very carefully. I understood that we had a 30-day notice period, but according to Duplo, we are locked into a yearly contract.

    Which other solutions did I evaluate?

    We considered alternate solutions, but I cannot remember them by name.