Really it's for both. One of our cofounders came from a genomics background and so that's why we have the Marimo notebooks + R Studio Server + genomics container. But we've also had a lot of requests for general VMs so we made some of those as well.

Did you try to log in with Github or gmail?

We have no egress fees but you're right about Hetzner. They're cheap. We aim to offer more value-added software to make up for it. Also that machine is in Europe, Americans don't like the latency (at least I don't), they have been known to shut people down (within reason).

Also I'm seeing that the most they can go RAM-wise for a dedicated US location is 192G. We go to 512 and will soon go beyond. I'm sure they'll get there soon but that's a consideration as well.

Please go an checkout the whole offer of hetzner is already everything you need.

Hetzner doesn’t offer their cheap dedicated servers in the US, only their cloud offering which is similarly priced to the OP’s example ($223).

We have about 1000 cores right now.

We're really excited for the AMD EPYC Venice — 256 physical cores each -> 512 vCPUs -> 1024 vCPUS on a single board with dual-socket. It will probably be about $40k per machine with these RAM prices but we're definitely going to buy a few. A full data center on a single motherboard!

So we're limited on capacity since we own all our own hardware. Please do not use us for auto-scaling just yet. Our software would have no issue with us linking up other cloud machines such as AWS EC2 to our fleet and offering it there, which could help with auto-scaling, but we would not make any money on that and it would be a lot of engineering effort for us right now.

We don't have on-demand API-based bare metal provisioning right now. Sorry if that is misleading on the website. Our bare metal is OTC right now (over the counter).

For the rest of our provisioning (VM and container) I wrote the software myself. It's based on a Django app called the "master" that hosts the console and keeps track of who has rented what etc + a bunch of "host" nodes that listen for instructions from the "master". Pure python, the only thing that's in Go is the CLI.

I looked into Proxmox but ultimately decided I wanted full control. ZFS storage from Proxmox is something I do sometimes wish we had — going to offer s3-compatible storage very soon but I know Proxmox does ZFS out of the box really well.

How do you sanitize hardware between workloads?

Yes we're going to offer this very soon, we have a bunch of SSDs but we're still deliberating on what to use now that MinIO is moving toward closed source.

garage (written in rust) / seaweedfs (written in golang) are something which I have heard is mostly recommended by the community.

Someone on lowendtalk recently created a very minimalist php s3 thing too if you only need the basic crud app but I would recommend you to select garage from what I've heard

I have also heard someone creating a new rust s3 application but I forgot its name but maybe you can look out for it too and see what fits the best for your goal.

Also coolify team is maintaining a docker image of MinIO but that was before they said that minio is going closed source and that they had just stopped providing docker images so I am not sure how valid it is right now. There must be forks who are maintaining Minio too so you can look at it too.

Landing page or console? We didn't really build our console for mobile though we probably should.

We fixed this, please try again, also if anyone knows how to run a Three.js shader without exploding people's laptops I am very open to suggestions.

curiously other pages with three.js demos at the landjng page like svelteflow.dev/ doesn't have this issue

i think the trick is to not attempt to render at each frame (that is, don't try to provide something similar to a game engine). just render it based on user input, like the page I linked

We actually ran out of my house in our very early stages at which case we owned everything. We had Google Fiber 8gbps for $150/mo. The only issue was the Google Fiber terms of service — ie they could shut us down at any time. This was one reason we went to colocation.

> at which case we owned everything. We had Google Fiber

So you didn’t own everything. Google owned the IPs and network.

It’s the same colocating in that your network providers can be shut down.

I guess you're right. Is it even possible to truly own everything yourself? Even if you open your own data center, at some point you have to agree to peer with big fiber providers like Segra, Lumen, AWS Edge Network, right?

> Is it even possible to truly own everything yourself?

Even if you do there's still more to it e.g. blacklists of different kinds e.g. known proxies, spam listings, etc that would still mean you need to kick out your client.

Then there's the bad clients you need to deal with e.g. if they send DoS from your network. Even if you don't get a report it will eat up your limited resources and you may be subject to revenges and bring down your infrastructure.

Conclusion: there's lots to it but so does every business. That's just life.

We've yet to have any DDoS problems. We don't even use cloudflare proxy which we feel keeps our API and frontend super fast and responsive.

yes, pretty unlikely to have them, as long as all your customers are actually ML people