Anbox Cloud Appliance - Arm logo

    Anbox Cloud Appliance - Arm

    Scalable Android in the cloud

    Ratings and reviews

    3.7
    3 ratings
    4 star
    3 star
    2 star
    67%
    0%
    0%
    0%
    33%
    2 AWS reviews
    |
    1 external reviews
    External reviews are from PeerSpot .

    Filters

    Review type

    AWS Marketplace reviews
    External reviews
    Reviews (3)
    David Titus

    Cloud testing has replaced physical devices and delivers faster, more collaborative Android workflows

    Reviewed on Jun 05, 2026
    Review from a verified AWS customer

    What is our primary use case?

    The specific use case where we are using Anbox Cloud is to run Android system and applications directly instead of running them on physical devices, which helps our organization. All the procedures for the clients require the Android applications to be tested, and we are directly testing it on the cloud and building it on the cloud.

    We don't need physical devices for that, and it helps us with the same architecture used in actual smartphones. It avoids the sluggishness of traditional desktop emulators and offers a great native mobile phone experience at a very low cost and a very high pace.

    What is most valuable?

    The shift to Anbox Cloud has contributed to both the aspects of workflow. It has expedited the delivery aspect as well as the team collaborations. As we don't have to be dependent on physical devices, it directly impacts the organization's architectural expenses, which have been reduced. That is cost cut, for one. Second, when we don't have to rely on the devices, it means we don't have to wait for them to be available in the organization, leading to better collaboration, better availability of the teams, and the tasks they can perform.

    The first feature which I love is the ARM embedded execution, ensuring that 100% compatibility is there with the Android apps without any kind of translation overhead. Secondly, it provides us with a web-based dashboard that allows our teams to manage the virtual devices without writing complex deployment scripts, and it does not require any heavy architecture. Thirdly, I love the LXD containerization that runs Android in containers instead of full virtual machines, allowing us to pack more virtual phones onto a single cloud server, saving a lot on cloud server costs, OCP costs, and physical device costs. Additionally, I love the automated testing integration that easily plugs into our existing deployment pipelines and automates app testing at a very high level scale.

    The automated testing integration in Anbox Cloud has reduced our testing time by 90%, decreased defect density by 87%, and also helped identify any zero-day vulnerabilities earlier, ensuring that the testing is complete and all edge cases have been covered in that automated testing run.

    What needs improvement?

    Everything seems to be very great, whether it is deployment integrations, the user interface, the pricing, setup cost, deployments, each and everything is on point. The ROI we are getting here is more than expected, so there is nothing I can remember as an improvement to the software.

    If I had to think of an area for improvement in Anbox Cloud, I would say AI is getting advanced day by day, and they could add some advanced AI integrations and an AI agent in their upcoming workflows.

    For how long have I used the solution?

    We have been using Anbox Cloud for the last four years in our organization.

    What do I think about the scalability of the solution?

    The scalability of Anbox Cloud is really good; we can scale up and down with the pay-as-you-go model and have scaled up to 10,000 screens at a time during heavy resource demand without facing any build or stability issues.

    How are customer service and support?

    We spoke with customer support six months back, and they were really responsive, well-trained, and resolved our query within 45 minutes, so a 10 on 10 for the customer support.

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

    We did not use any other solution prior to Anbox Cloud.

    How was the initial setup?

    It was not difficult to deploy Anbox Cloud in our AWS environment; it was very well-versed with AWS cloud, and the integrations were seamless. We did not face any challenge while configuring the solution in our organization.

    What about the implementation team?

    When integrating Anbox Cloud with other AWS services like Lambda or EC2, we see much integration occurred, and the integrations were seamless. It was done through our SSO of the organization with single-click integration, very seamless, and there were no breaks or errors in the APIs or the responses.

    What was our ROI?

    My experience with pricing, setup cost, and licensing for Anbox Cloud was very transparent. The licensing and everything was clear. The ROI is really good, and we have seen cuts in resources and money. We have reduced the number of physical Android testing devices by 90%, and we have saved time by at least 80 to 85%.

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

    The metering and billing experience with Anbox Cloud on AWS is transparent via AWS Marketplace, and I feel they provide a great price while we are getting it from AWS. They give a transparent and good view for us to decide based on the price range, and I appreciate the good discounts we receive. The best thing I love about the metering and billing experience is the pay-as-you-go model, which allows us to pay based on how much we use.

    Which other solutions did I evaluate?

    While choosing Anbox Cloud, we definitely evaluated other options such as Azura, Chargebee, and Replicli. However, Anbox Cloud was the best one we figured out, which is why we chose it. Anbox Cloud is a 100% stable solution, and I feel it does a great job—very stable.

    What other advice do I have?

    Anyone who is looking for a great solution for building and testing Android applications over the cloud should definitely consider Anbox Cloud. I give this product a rating of 5 out of 5.

    Which deployment model are you using for this solution?

    Public Cloud

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

    Amazon Web Services (AWS)
    ANDRE VINICIUS HAMERSKI

    Facilitates digital transformation with seamless integration

    Reviewed on Dec 04, 2024
    Review provided by PeerSpot

    What is our primary use case?

    We are implementing Vicarious, a vulnerability management tool, and have integrations with Kubernetes using APIs. Also, we use Canonical to support access to technology documents, articles, and to open issues.

    What is most valuable?

    We have enjoyed the same experience as public cloud with a digital transformation since 2016, leading to a necessity to improve our environment using infrastructure as code.

    It helps run Android and system containers using Ubuntu Pro. The product made it easier to insert new components and hosts in our private cloud, allowing us to update the number of hosts in our environment.

    What needs improvement?

    In Brazil, it is difficult to find technical professionals with OpenStack or this technology skills. The solution is complex to administrate, and the initial setup requires significant experience.

    For how long have I used the solution?

    We have been using the solution since 2021.

    What do I think about the stability of the solution?

    It is perfect, not even a problem until now. We don't have any problems with stopping production or anything else.

    What do I think about the scalability of the solution?

    It's simple to scale. We insert new components and hosts in the private cloud and can update the number of hosts in our environment.

    How are customer service and support?

    We have an excellent experience with support from Canonical. They provide great support, and our experience with the support team has been excellent.

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

    We initially used OpenStack from VMware for our setup and had a simple deploy with them.

    How was the initial setup?

    The deploy with VIO from VMware was very simple, but the support wasn't set. With Canonical, we have excellent support and a good experience. However, the initial setup requires significant experience.

    What about the implementation team?

    We have four people administrating the solution who are infrastructure analysts with strong Linux experience.

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

    We have three clouds: one production, one for production, and one lab. We have a license supporting a specific number of hosts and update it each year, making the contract simple with them. It is not expensive.

    What other advice do I have?

    Overall, Canonical is rated ten out of ten. We don't have significant issues, and we have a great group of professionals, which makes administration easy.

    Michael

    waste of time

    Reviewed on Jun 20, 2024
    Review from a verified AWS customer

    Tested about 10 different applications self-developed or 3rd party published; all of them result in 500 error via anbox dashboard. Error logs were empty as well so couldn't even trace what might cause the issue.