HNHacker News
TopNewBestAskShowJobs

sksjvsla

186 karma · joined June 21, 2025

jk@datapult.dk

https://datapult.dk/

https://knobel-dk.github.io/landingpage-iso-playbooks/

submissionscomments
sksjvsla··on We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
Yes, bootstraped for our own money. It makes a difference.

If I generalize, I see two kinds of groups for whom this reduction of cost does not matter. The first group are VC-funded, and the second group are in charge of +million AWS bill. We do not have anything in common with these companies, but we have something in common with 80% of readers on this forum and 80% of AWS clients.

sksjvsla··on We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
Exactly our insight having maintained the same app both places.
sksjvsla··on We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
We use cloudflare as the WAF and loadbalancer, which makes traefik less relevant and Certbort easier to couple.
sksjvsla··on Show HN: We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
https://news.ycombinator.com/item?id=44335920#44336757
sksjvsla··on We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
> Cost of DIY and support: You’re absolutely right that 24x7 ops could eat up any savings if you built everything from scratch without automation or if you needed dedicated staff watching dashboards all night. In our case:

• We heavily invested upfront in infrastructure-as-code (Terraform + Ansible) so that infra is deterministic, repeatable, and self-healing where possible (e.g. auto-provisioning, automated backup/restore, rolling updates).

• Monitoring + alerting (Prometheus + Alertmanager) means we don’t need to watch screens — we get woken up only if there’s truly a critical issue.

• We don’t try to match AWS’s service level (e.g. RTO of minutes for every scenario) — we sized our setup to our risk profile and customers’ SLAs.

> True cost comparison:

• The migration was done as part of my CTO role, so no external consulting costs. The time investment paid back within months because the ongoing cost to operate the infra is low (we’re not constantly firefighting).

• I agree that if you had to hire more people just to manage this, it could negate the savings. That’s why for some teams, AWS is still a better fit.

> Business vs. cost drivers: Honestly, our primary driver was sovereignty and compliance — cost savings just made the business case easier to sell internally. Like you, our European customers were increasingly skeptical of US cloud providers, so this aligned with both compliance and go-to-market.

> Terraform / YAGNI: Fair point! Terraform probably is more than we need for the current scale. I went with it partly because it fits our team’s skillset and lets us keep options open as we grow (multi-provider, DR regions, etc).

And, finally, because this, I am posting about it. I am sharing as much as I can, and just spread the work about it. I just sharing my experience and knowledge. If you have any questions or want to discuss further, feel free to reach out at jk@datapult.dk!

sksjvsla··on We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
Without making it too political and speculating on things I don't know, I, like many other Europeans, have seen plenty of cases of Russia ruining infrastructure projects in Europe, everything from internet cables on the ocean bed, telcos, water supplies, railways and more. Authorities are asking civilians in Scandinavia to be prepare their hiused with. Good and water and are actively hardening security around critical infrastructure, including their software. I won't comment more on this because it's gonna derail this discussion.
sksjvsla··on We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
Great question. Technically speaking I might not need both, but I have a gut feeling that one of these cloud providers might not be as hardened as the hyperscalers, and that Russia is just waiting to put one of these two services down. So for maximal resiliency I chose to design from a multi-cloud setup from the beginning.

Scaleway came up but is more expensive. IONOS did not come up in our research.

Part of what we tried to do was to make ourselves independent from traditional cloud services and be really good at doing stuff on a VPS. Once you start doing that, you can actually allow yourself to look more at uptimes and at costs. Also, since we wanted everything to be fully automated, Terraform support was important for us, and OVHcloud and Hetzner had that.

I'm sure there's many great cloud providers out in Europe, but it's hard to vet them to understand if they can meet demand and if they are financially stable. We would want not to keep switching cloud providers. So picking two of the major ones seemed like a safe choice.

sksjvsla··on We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
The Medium post is more of a high-level case study for a mixed audience (including non-technical decision makers). I intentionally kept the details lighter there, partly to avoid overwhelming readers and partly because the real “meat” (like our Ansible/Terraform patterns, Prometheus config, etc.) is harder to convey in that format without turning it into a giant technical appendix.

I’m happy to share specific configs, diagrams, or lessons learned here on HN if people want — and actually I’m finding this thread a much better forum for that kind of deep dive.

I'll dive into other aspects elsewhere: You can't doubt that given what I am sharing here.

Any particular area you’d like me to expand on? (e.g. how we structured Terraform modules, Ansible hardening, Prometheus alerting, Loki tuning?)

sksjvsla··on We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
Thanks for the compliment.

We used AWS EKS in the old days and we never liked the extreme complexity of it.

With two Spring Boot apps, a database and Redis running across Ubuntu servers, we found simpler tools to distribute and scale workloads.

Since compute is dirt cheap, we over-provision and sleep well.

We have live alerts and quarterly reviews (just looking at a dashboard!) to assess if we balance things well.

K8s on EKS was not pleasant, I wanna make sure I never learn how much worse it can get across European VPS providers.

sksjvsla··on Show HN: We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
Depends on the use case, right? I don’t accept traffic from random Hetzner IPs — only Cloudflare’s IPs are allowed.

The only potential indirect risks is if your Hetzner VPS IP range gets blacklisted (because some Hetzner clients abuse it for Sybil attacks or spam).

Or if Hetzner infrastructure was heavily abused, their upstream or internal networking could (in theory) experience congestion or IP reputation problems — but this is very unlikely to affect your individual VPS performance.

This depends on what you are doing on Hetzner and how you restrict access but for an ISO-27001 certified enterprise app, I believe this is extremely unlikely.

sksjvsla··on Show HN: We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
Yes, it would be nice. Given Cloudflare's dev-friendly branding for some reason, I did not mind keeping it.
sksjvsla··on We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
A good alternatives for Loki is Victoria. Popular, way more performant and reputable but we went with Loki because of the relative size and diversity of maintainers between the two projects. Your points are super valid and we worked around it as mentioned above.
sksjvsla··on We moved from AWS to Hetzner, saved 90%, kept ISO 27001 with Ansible
Pollution: We front everything user-facing through Cloudflare, so external users (and bots) don’t interact directly with our Hetzner/OVH IPs. We lock down our IPs at the firewall (ufw + Cloudflare IP allowlisting) so only trusted sources can even connect at L4.

Failures/upgrades: We provision with Terraform, so spinning up replacements or adding capacity is fast and deterministic.

We monitor hardware metrics via Prometheus and node exporter to get early warnings. So far (9 months in) no hardware failure, but it’s a risk we offset through this automation + design.

Apps are mostly data-less and we have (frequently tested) disaster recovery for the database.

Loki: We’re handling the memory hunger by

• Distinguishing retention limits and index retention

• Tuning query concurrency and max memory usage via Loki'’'s config + systemd resource limits.

• Use Promtail-style labels + structured logging so queries can filter early rather than regex the whole log content.

• Where we need true deep history search, we offload to object store access tools or simple grep of backups — we treat Loki as operational logs + nearline, not as an archive search engine.

← PreviousPage 2 of 2