hi everyone, after reading through the doc, i find it only mentions Garden Cloud where you do

garden login

or checking garden dashboard on SaaS. i am curious what are missing in OSS and if i can easily self-host it on my own K8s cluster (e.g. do you plan to provide a Helm Chart)

remote container builds (that is managed by garden), team caching, and remote variables and secrets are the only things you're missing out on that come to mind. and there are some good OSS and self hosteable alternatives for all of those if you're willing to jump through some hoops. there's probably plenty of other neat and awesome things but docs.garden.io isn't marketing those aggressively so can't list those as I haven't used the cloud. there are some demo videos in youtube if you're interested. the log viewer looked really cool but I've managed without it so far

thanks for sharing. i hope Garden can be more clear what features are Cloud only and what are not. but i wonder why you pick Garden over alternatives like Tilt or telepresence?

Hi @delightful-piano-88229 Thanks for chiming in @fresh-angle-76971. That's a pretty good overview. Beyond what's been mentioned I'd also call out that we display results and logs from all Garden command runs in the cloud product. This can be helpful when debugging failed CI runs because it makes it easier to focus on just the logs for the Garden action that failed. A lot of teams also use this to share links to errors / issues when debugging things together. I will say that the Youtube videos are a bit dated, we recently did a complete overhaul of the cloud product and the UI is quite different. I'll throw in some screenshots below from the Command Runs page which shows command results, logs, etc