| Hi! > In my opinion the syntax of layerci is relatively simple That's awesome! They've definitely built a nice product for some use cases, can't disagree with that. > Reploy only works if my app fits in the runtimes that were preconfigured by you Reploy actually supports any arbitrary runtime. Checkout our docs: https://docs.getreploy.com > their aggressive docker-like layer caching allows very substantial speedups in not only builds, but tests as well Makes sense; Reploy actually won't run your tests (or any other CI-esque things to that note). We're very much focused on only spinning up environments! Overall, there is definitely overlap here. I'd argue that if someone wants to spin up a frontend, backend, db, etc., it makes a lot more sense to enumerate your `services` rather than try and serve them all in a single runtime (I think this is called a Layerfile?). I'm not sure how a use case like this would work with Layer, but that would be my hesitance in trying to set things up. Layer seems like a great option for running long jobs to really take care of that speed up. |