So if I understand correctly by local you mean on the test runner? So at the beginning you build your CI env and you start a local web server. Then later on when you are running the tests they hit the local web server (on the runner) during the tests?

We do support this yes. With what we call background jobs. Each test runner also comes with a dedicated docker server for running additional services (db, etc). It’s an experimental/new feature though and I haven’t properly figured out how to charge for it.

In the happy case while the worker isn’t running tests the background job should be consuming very little resources.. but we can’t rely on that (and also some people will inevitably try to mine crypto) so figuring out how to make sure the workers aren’t hogging the cpu between test runs has prevented me from broadcasting the existence of the feature, it is there though.