I see how that could be confusing; I'll add clarity around pricing. Currently it mirrors the way serverless computing is priced - per second of compute time per

I see how that could be confusing; I'll add clarity around pricing. Currently it mirrors the way serverless computing is priced - per second of compute time per instance. So, your second example is correct. I started with $0.003 per second, because it aligns with existing cloud-hosted grids. An example pricing model is ~$200/month for 2 parallel instances with 1000 min. Assuming unlimited parallelism, you get $0.00333 per second. 20+ parallel browsers on existing services are at least a couple thousand every month. I don't think remote grids are the best solution for every test performance problem, and for some test loads, local runs can be faster. That said, pricing weighs into the remote vs local decision, so I really appreciate the feedback.