Issue with deno deploy specifically: they have Deno subhosting but the model is you create an end user script, push it, then can run it.

There's no concept of "run this once" or eval. So it's a very heavy, deploy per run, model of iteration which is not suitable for the main use case of giving end users an editor to iterate with