Super helpful, thanks for touching on what does and doesn't have an immediate need for you. re: ~/Booste directory, just pushed and update yesterday that allow

Super helpful, thanks for touching on what does and doesn't have an immediate need for you. re: ~/Booste directory, just pushed and update yesterday that allows you to move your filesync directory around to wherever you want. It's not quite perfect yet, as I haven't built a way to clean old project files out of the codebox. But your new repo will overwrite anything that'd get int the way, so functionally, you're good to go there. There's a "booste upload bulk" command, which takes a .boosteignored "bulk/" directory, for hefting code up to the codebox without bogging down filesync. Haven't get built a "booste download bulk" command, since customer pull recently has been more web-dev oriented, but I'll get on that once more ML folks play with Booste. Codeboxes have auto-spindown. Default four hours live, but could make a command to monitor processes and spindown once done. Like a flag "booste --stop-when-done python3 train.py" Nothing for Jupiter notebooks yet, and it's frankly going to be a tough technical nut to crack. Interested in exploring though. (Edit: added below) As for cloud flexibility, I'm sure more enterprise scale companies would absolutely require to host Booste on their own infrastructure. Like a bring-you-own-server model. Bring-you-own-server and multi-cloud not in the works in the near future, but perhaps mid-long term.