Best VPS options - Can't tell if I don't know of any good options or if I'm just retarded

  • 🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.

lrios4403

kiwifarms.net
Joined
Sep 15, 2024
Hey, I'm trying to find a good VPS in order to host some archives of websites I downloaded over the years as a hobby.

Got a pseudo next frontend with a custom warc parser all in docker. The plan was to forward the backend API to a VPS (where the frontend resides) but the vps I was using OVH (recommended from a friend) only had prebuilt packages, where if only wanted higher speed internet (since all of the websites are stored at home with a reverse proxy) I had to pay for higher tiers with storage and CPUs I didn't need.

I got it running with OVH but was wondering if there were any other options available for just shitty VPS good with good download speeds
 
  • Deviant
Reactions: Just A Butt
If you need lots of space and US location is fine, https://crunchbits.com/vps/storage
They won't fold to "speech" related issues, owner is a great guy.

It all depends on how much storage exactly do you need. Provide me with specs for a more tailored recommendation.
Whatever you do, don't touch iHostArt, its unusable. I already told Josh to remove it from the list.
 
Last edited:
If you need lots of space and US location is fine, https://crunchbits.com/vps/storage
They won't fold to "speech" related issues, owner is a great guy.

It all depends on how much storage exactly do you need. Provide me with specs for a more tailored recommendation.
Whatever you do, don't touch iHostArt, its unusable. I already told Josh to remove it from the list.
Sorry let me better explain my stack.

On the vps I have the front end of the server written in nextjs as well as the entry point for the API. Using a proxy I can connect this frontend to the backend somewhere else so all I really need here is something cheap to handle nextjs. For example /warcs/view?uri=... shows the wanted page with the parameters given.

On the backend it connects to my old desktop that I am using as the parser and the API. With a proxy the API and http requests are forwarded and responded to the frontend. This gives me the ability to buy as many cheap hard drives that I need without worrying about the costs of space, CPU, ram needed for parsing I think a couple tb or storage.
 
Sorry let me better explain my stack.

On the vps I have the front end of the server written in nextjs as well as the entry point for the API. Using a proxy I can connect this frontend to the backend somewhere else so all I really need here is something cheap to handle nextjs. For example /warcs/view?uri=... shows the wanted page with the parameters given.

On the backend it connects to my old desktop that I am using as the parser and the API. With a proxy the API and http requests are forwarded and responded to the frontend. This gives me the ability to buy as many cheap hard drives that I need without worrying about the costs of space, CPU, ram needed for parsing I think a couple tb or storage.

So all you really need is a reverse proxy to your backend, many cheap vps would do.
What are your bandwidth requirements(TB per month)? What uplink port would you like?
 
1753374666769.webp


Any reference on these guys?
 
Last edited:
Back