Could you walk me through how to estimate AWS costs for this setup?

Here’s a concise approach to estimate AWS costs for Genymotion Cloud on AWS, based on Genymotion’s cloud offering and pricing guidance:

• Define scope
• Determine how many concurrent virtual devices you need (test parallelism), which Android versions, and test duration per run.
• Choose AWS region for your deployments (costs vary by region).

• Identify the Genymotion deployment option
• Genymotion Device Image on AWS (AMI) in the cloud, or Genymotion SaaS in the cloud. These options are designed for cloud-based Android emulation and support scalable, browser-based access. See Genymotion Cloud on AWS details for overview and capabilities. Source: Genymotion AWS page.
• Pricing approach emphasized by Genymotion: price ranges for Genymotion on AWS are typically quoted per hour per device; example ranges cited include roughly $0.125–$0.5 per hour depending on configuration. Source: Genymotion on AWS pricing page.

• Estimate compute costs
• Multiply the hourly price per device by the number of concurrent devices and by the expected hours of usage.
• Consider ARM-based (Graviton) instances if available, as Genymotion highlights ARM64/Graviton options for cost efficiency. Source: Genymotion AWS overview.

• Add storage and data transfer
• Include EBS volume costs for the device images and any persistent storage.
• Include data transfer costs (inbound typically free; outbound data transfer billed by AWS). If devices stream data to CI/CD or dashboards, estimate egress.

• Include orchestration/automation costs
• If you use AWS APIs to automate device provisioning, scaling, and teardown, factor in API request costs and any additional networking or IAM-related charges.

• Build a simple example budget
• Example (illustrative): if a device costs 0.25/hour and you run 10 devices for 8 hours/day, monthly compute cost ≈ 0.25 10 8 * 22 ≈ $440. Add storage and data transfer estimates as applicable. Note: use current AWS region pricing and Genymotion’s current per-hour rates from their page for accuracy.

• Validate with a pilot
• Run a small pilot with a handful of devices to verify actual usage, then scale the estimate up for full test runs.

Sources:

• Empower your Android teams with Virtual Devices that truly scale on AWS (Genymotion Cloud on AWS pricing and capabilities) Empower your Android teams with Virtual Devices that truly scale on AWS
• Get to the Next Level with Genymotion on AWS (pricing guidance and ARM64/Graviton notes) Get to the Next Level with Genymotion on AWS

Would you like me to tailor a rough monthly AWS cost estimate based on your target concurrency (e.g., 5, 10, 20 devices), region, and expected daily test hours?

One follow-up question: How many concurrent emulators do you plan to run, and in which AWS region are you considering?