CloudBeat is a centralized continuous quality platform that helps create, execute and analyze unit, API, integration and end-to-end tests in a DevOps environment
CloudBeat provides full end-to-end solution allowing users to create, execute, and manage automation tests. Tests can be created in a number of supported test frameworks such as NUnit, JUnit, Playwright,PostMan, etc. CloudBeat supports test parameterization, setting up switchable test environments, execution on multiple execution agents, flexible scheduling mechanism, and detailed test execution reports with user notifications. CloudBeat is made to cover all the needs in the area of QA, starting from manual test execution by QA engineers and up to automatic monitoring of production systems.
AWS Marketplace now accepts line of credit payments through the PNC Vendor Finance program. This program is available to select AWS customers in the US, excluding NV, NC, ND, TN, & VT.
Pricing is based on actual usage, with charges varying according to how much you consume. Subscriptions have no end date and may be canceled any time. Alternatively, you can pay upfront for a contract, which typically covers your anticipated usage for the contract duration. Any usage beyond contract will incur additional usage-based costs.
Additional AWS infrastructure costs may apply. Use the AWS Pricing Calculator to estimate your infrastructure costs.
You pay by the hour based on the EC2 instance size you run CloudBeat on. All nine options bill hourly and differ only by compute capacity. The t2, t3, and t3a families reflect different processor generations. Within each family, large, xlarge, and 2xlarge mark increasing CPU and memory. Larger sizes support heavier test execution and parallel workloads. Your cost scales with the instance size you pick and the number of hours you run it. You can match instance choice to your testing load and change it as needs shift.
Top-of-mind questions for buyers
What does one billing unit represent for each instance option?
Each unit is one hour that the CloudBeat software runs on a given EC2 instance size. You are billed for the running time on that instance type. Every hour the selected instance runs adds one hour of software charge to your invoice.
Am I charged when the CloudBeat instance is stopped or paused?
The hourly software charge meters running time only. When you stop the instance, the CloudBeat charge stops accruing. Underlying AWS storage or other resource fees may still apply while the instance is stopped, but those are separate from the software metering.
How do I decide which instance size fits my testing workload?
CloudBeat runs parallel test execution across many frameworks. Heavier parallel test sets and larger suites benefit from more CPU and memory. Pick a size that matches your expected concurrent test load. You can change the instance size as your testing volume shifts, since billing follows the size you run.
docs.cloudbeat.io
Helpful?
Vendor refund policy
We do not currently support refunds, but you can cancel at any time.
How can we make this page better?
Tell us how we can improve this page, or report an issue with this product.
Give us feedbackReport a problem with this product or seller
Legal
Vendor terms and conditions
Upon subscribing to this product, you must acknowledge and agree to the terms and conditions outlined in the vendor's End User License Agreement (EULA).
Content disclaimer
Vendors are responsible for their product descriptions and other product content. AWS does not warrant that vendors' product descriptions or other product content are accurate, complete, reliable, current, or error-free.
This CloudFormation template will launch an EC2 instance with an Elastic IP, with instance type, VPC, and subnet specified during the launch process. It will also create an Amazon ElastiCache Serverless cache (Valkey 8) in a separate security group accessible only from the main instance.
It will create secrets named cb_mysql_root, cb_mysql_wd_webui, cb_es_cb_web, and cb_default_user in Secrets Manager and will create a new role for accessing these secrets. These secrets will be used during the setup stage for configuring MySQL, Elasticsearch, and CloudBeat passwords.
Two security groups will be created:
A main security group with an ingress rule allowing access to ports 80, 443, 8080, 5002, and 3389 from the specified IP ranges, and an egress rule allowing all outbound traffic.
An ElastiCache security group allowing access on ports 6379-6380 only from the main EC2 instance.
Two subnets in different Availability Zones must be provided, as required by ElastiCache Serverless. You are responsible for assigning relevant domain names during the CloudFormation launch process and pointing them to the Elastic IP assigned to the instance.
Once created, users can access the platform using a web interface or an external API, and connect test agents to the system.
When choosing an instance type, please note that:
large instance is limited to 1 test execution agent.
xlarge instance is limited to 2 test execution agents.
2xlarge instance is limited to 6 test execution agents.
CloudFormation Template (CFT)
AWS CloudFormation templates are JSON or YAML-formatted text files that simplify provisioning and management on AWS. The templates describe the service or application architecture you want to deploy, and AWS CloudFormation uses those templates to provision and configure the required services (such as Amazon EC2 instances or Amazon RDS DB instances). The deployed application and associated resources are called a "stack."
Version release notes
Release notes are available upon request from the CloudBeat team.
Additional details
Usage instructions
Template components
CloudFormation template
Usage instructions
To get started with CloudBeat, launch the stack using the provided CloudFormation template.
The template will launch an EC2 instance; you will need to choose the instance type, VPC, and subnet for the instance.
Four secrets, named cb_mysql_root, cb_mysql_wd_webui, cb_es_cb_web, cb_default_user will be created in Secrets Manager, along with a new role to access these secrets. These secrets are used during the setup stage for configuring MySQL, Elasticsearch, and CloudBeat passwords.
A security group will be created with an ingress rule allowing access to ports 80, 443, 8080, 5002, and 3389. Specify the relevant CIDR IPv4 ranges when launching the stack. In addition, an egress rule allowing all outbound traffic from the instance will also be added.
Assign the domain names specified during the CloudFormation launch process and point them to the instance.
Once created, navigate to http://CB_DOMAIN, where CB_DOMAIN is the domain you specified when launching the CloudFormation template. The default user is guest@example.com. Password is stored in Secrets Manager under cb_default_user. This user should be removed or have its password changed once additional administrators have been added using the CloudBeat interface.
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.
Be the first to review this product. We've partnered with PeerSpot to gather customer feedback. You can share your experience by writing or recording a review, or scheduling a call with a PeerSpot analyst.