Migrating from DigitalOcean to Hetzner • Hacker News Board

Re: Migrating from DigitalOcean to Hetzner

#361

Post by onemoresoop » Sun, Apr 19, 2026, 1:03 AM UTC

p_stuart82 wrote: post #242

antirez wrote: post #9

I moved two servers, one from Linode and the other from DO to Hetzner a few months ago, with similar savings. The best part was that the two servers had tens of different sites running, implemented in different languages, with obsolete libraries, MySQL and Redis instances. A total mess. Well: Claude Code migrated it all, sometimes rewriting parts when the libraries where no longer available. Today complex migrations…

IMO nobody was paying for magic compute. they're paying to not touch ten years of glue. if agents eat that glue, the moat gets thin fast.

Don’t forget staples and the tape too. LLMs have a weakness for paperclips, hope we don’t end up on that path

Re: Migrating from DigitalOcean to Hetzner

#362

Post by acdha » Sun, Apr 19, 2026, 1:09 AM UTC

alternatex wrote: post #160

acdha wrote: post #106

Earlier quoted context omitted.

That’s like saying Mercedes is a scam because you’re fine with a Honda Civic. It’s a totally legitimate preference but not being in the target market doesn’t make something a scam.

AWS ain't no Mercedes. Mercedes feels premium and isn't full of bugs. AWS and Azure a charging an arm and a leg, but the offered quality is mostly perceived. Most of the bits and bobs they charge for are not providing much value for a vast majority of businesses. I won't even go over the complete lack of ergonomics with their portals.

I see you have strong emotions about this but really my point was simply that AWS customers are paying for things they value which you do not. It’s fine for you not to share their priorities but any time people are paying billions of dollars for something in a competitive market, it’s a mistake to say they’re all fools or being fooled.

Re: Migrating from DigitalOcean to Hetzner

#363

Post by Frannky » Sun, Apr 19, 2026, 1:11 AM UTC

I have been using hetzer for a few years now. I realized I just need a Linux VM and snapshots. It is so freeing to not have to deal with big tech's VMs and their cumbersome and soul-sucking steps and documentation.

Re: Migrating from DigitalOcean to Hetzner

#364

Post by anurag » Sun, Apr 19, 2026, 1:32 AM UTC

stephenhuey wrote: post #307

pier25 wrote: post #289

Earlier quoted context omitted.

I don't know about Hetzner but with Upcloud and Vultr my single VPS setups have been more reliable than multiregion with redundancy setups with other providers like Fly.

A few weeks ago, I tested deploying Rails apps to Hetzner and Vultr for the first time using Hatchbox to deploy Rails apps onto them. I'm still supporting clients on Heroku, but there are potential new projects in the coming months that I might deploy elsewhere. Render is decent in some cases, but you can get a lot of bang for your buck deploying on Vultr, and Hatchbox makes it easy to do, whether you have one instan…

Render lets you attach a disk to your app: https://render.com/docs/disks

Re: Migrating from DigitalOcean to Hetzner

#365

Post by squirrellous » Sun, Apr 19, 2026, 1:33 AM UTC

mariopt wrote: post #128

Every time I see this kind of article, no one really bothers about sb/server redundancy, load balancers, etc. are we ok with just 1 big server that may fail and bring several services down? You saved a lot of money but you'll spend a lot of time in maintenance and future headaches.

I’d even argue that most things operated by tech doesn’t need 24x7x365 availability. If it’s about life-and-death, then yes make it super reliable and available. Otherwise, bring back scheduled downtime please.

Re: Migrating from DigitalOcean to Hetzner

#366

Post by wpollock » Sun, Apr 19, 2026, 1:58 AM UTC

antirez wrote: post #251

FEELmyAGI wrote: post #130

Earlier quoted context omitted.

Come on can you really nitpick grammar when your original message contains: "when the libraries where[sic] no longer available" Btw this type of grammar error can be found by proofreading your posts with ChatGPT powered OpenClaw assistant.

I was joking. I notoriously write bad English but don't like using LLMs for writing. It removes personality.

> I notoriously write bad English...

You mean that you write in English badly. :-)

Re: Migrating from DigitalOcean to Hetzner

#367

Post by zuzululu » Sun, Apr 19, 2026, 2:01 AM UTC

Only complaint about hetzner is how difficult it is to become a customer there.

No matter what I try, they refuse which is frustrating. Even setting up a new company is not a realistic solution as the verification still requires passport.

If anybody knows an alternative, kindly leave a suggestion.

Re: Migrating from DigitalOcean to Hetzner

#368

Post by itsthecourier » Sun, Apr 19, 2026, 2:03 AM UTC

zuzululu wrote: post #367

Only complaint about hetzner is how difficult it is to become a customer there. No matter what I try, they refuse which is frustrating. Even setting up a new company is not a realistic solution as the verification still requires passport. If anybody knows an alternative, kindly leave a suggestion.

OVH is awesome

Re: Migrating from DigitalOcean to Hetzner

#369

Post by post-it » Sun, Apr 19, 2026, 2:08 AM UTC

rustyhancock wrote: post #60

antirez wrote: post #9

I moved two servers, one from Linode and the other from DO to Hetzner a few months ago, with similar savings. The best part was that the two servers had tens of different sites running, implemented in different languages, with obsolete libraries, MySQL and Redis instances. A total mess. Well: Claude Code migrated it all, sometimes rewriting parts when the libraries where no longer available. Today complex migrations…

Wow a Claude add embedded into a Hetzner add. How deep does this go?

Do folks see a mention of Claude as indicative of an ad? I usually say it because at work we've got a couple different options and I like to mention which one in particular I was using. But maybe I'll just start saying AI on forums unless someone asks me to specify.

Re: Migrating from DigitalOcean to Hetzner

#370

Post by pruthviraja » Sun, Apr 19, 2026, 2:10 AM UTC

Great migration execution. The nginx reverse proxy method during DNS propagation is a smart way. we utilize a comparable approach when transitioning workloads across Kubernetes clusters but the traffic management occurs at the ingress controller level with weighted routing. I am wondering if you thought about containerizing any part of this stack during the transition or if the decision to use bare metal was deliberate in order to maintain a manageable migration scope???