Show HN: Run `SSH bitbop.io`, get a personal GPU dev machine (twitter.com)

7 points by skainswoo ↗ HN
Hi HN! I've been hacking on this side project for the last month or two with the goal of making it dead simple to use cloud GPUs.

I ran into this problem personally during the phd, and built my own tooling around it. I always thought it'd be fun to try to turn that tooling into a more general product... and bitbop.io is the result!

All you have to do is run `ssh bitbop.io`, and you get your own personal dev GPU workstation in the cloud.

Looking forward to hearing your thoughts!

8 comments

[ 2.5 ms ] story [ 27.7 ms ] thread
Just tried this on a-Shell and got

> Permission denied (publickey).

… and same thing on iSH.

This is covered in the FAQ at the bottom https://bitbop.io/ (Note to developer: every (sub)heading on the page needs to be possible to link to.)

It did accept my RSA key, so I got a bit further than you, but then it failed to match it to the pubkey in my GitHub .keys file.

Just tried it on my mac. Same issue as the other user. Does not recognise my ssh key failed to match it on GitHub.
Make sure you pass -i ~/.ssh/your-github-added-key to ssh, that fixed it for me.
yep did that too. still the same error. GitHub key not matching.
I've noticed all users do not have their username.keys endpoint exposed on GitHub. I think it might be a privacy preference. (Disclaimer: haven't checked)
oh ok. Any idea how I can do that?
I like the simplicity.

On your pricing you state that for $19 (presuming USD?)/mo you get 'CPU, T4, and V100 GPU machines' - how do you manage fair usage of the GPU hours?

For example, if I wanted a V100 for say 3 hours today, then another 3 hours tomorrow - how does that work? What are the limits?

Also - what is the internet connectivity? How many MB / GB/s up/down to US east/west, AWS Sydney/Melbourne?