Bugmole Cloud or your own machines

Bugmole can run your tests in two places. You choose per project, and you can switch any time.

	Bugmole Cloud	Your own machines
Where tests run	Bugmole's browsers	Your laptop, CI runners, or servers (`bugmole serve`)
Setup	Nothing to install	Install the CLI
Cost	Uses your plan's cloud minutes	Free on every plan, with no limit
Browsers	Chrome, Firefox, Safari (WebKit) and Edge, plus emulated phones and tablets	Whatever the machine has
Reaching your app	Your app must be reachable from the internet	Can test `localhost` and private networks
Where results are kept	Bugmole storage	Bugmole storage, or your own bucket

Choose where a run goes

On Test plans, pick Where to run:

Bugmole Cloud starts the run on Bugmole's machines within a few seconds.
My workers queues the run for a machine running bugmole serve in this project.

The choice applies to Explore this URL as well, and it's remembered for the project. Re-runs, including Apply fix and Ask AI to fix, go wherever the original run went.

Cloud runs need Bugmole storage

A cloud runner starts from a clean machine, so it reads your plans from Bugmole storage and saves screenshots, videos and logs there. Projects created when you sign up use Bugmole storage from the start.

If a project keeps its files in your own bucket (Amazon S3, Cloudflare R2 or Google Cloud Storage), Bugmole Cloud is unavailable for it. To change that, open Manage → Projects and set the project's storage to Bugmole storage.

To use Bugmole storage from the CLI, set this in bugmole.config.yaml:

storage:
  provider: bugmole
  bugmole:
    registry_url: ${BUGMOLE_REGISTRY_URL}

The CLI signs in with the project's API key (BUGMOLE_API_KEY).

How cloud minutes are counted

A run's minutes are counted from when a cloud machine picks it up until it finishes.
Minutes are rounded up, with one minute as the smallest charge.
A run that never started (for example because no machine was available) isn't counted.
One run on four browsers uses one machine, so its minutes are the time the whole run took.
Each cloud run can take up to 60 minutes.

On Free, cloud runs stop when the month's 300 minutes are used up. They start again the next month; runs on your own machines keep working in the meantime.

On paid plans, runs continue past the included minutes at the plan's per-minute rate, up to your monthly spending limit. See Plans and limits.

You'll get an email when a workspace reaches 80% and 100% of its included minutes.

When your app isn't public

Cloud runners reach your app over the internet. For an app on localhost or behind a VPN, run on your own machines instead. A preview deployment or a staging site with a public address also works.