EU Production on Hetzner
Two days to ship and operate in Frankfurt — Docker, Caddy, backups, and a clear rule for when the workload belongs on AWS.
- Duration
- 2 days
- Level
- Beginner to intermediate
- Format
- On-site or remote
- Price
- On request
What to expect
Two days to run production in the EU on Hetzner: project and firewall, Docker Compose, TLS, deploy, backups, and a clear rule for when AWS is the next step.
- A firewall and Compose setup you can repeat
- TLS and a reverse proxy in front of a real deploy
- Backups, update habits, and the Hetzner-versus-AWS decision
What to know before
Who it's for
- Teams moving a prototype to a Hetzner VPS in the EU.
- Engineers who can SSH and want Docker, TLS, and backups without inventing an ops platform.
- Groups deciding whether this workload stays on Hetzner or belongs on AWS.
You'll learn to
- Stand up a Hetzner project with a firewall baseline and Docker Compose for production.
- Put TLS and Caddy in front of a deploy, including a static export.
- Run backups and updates, and decide when the service should move to AWS.
Agenda
- 1
Day 1
- Hetzner project and firewall baseline
- Docker Compose production patterns
- TLS and reverse proxy (Caddy)
- 2
Day 2
- Deploy from Lovable or a static export
- Backups, updates, incident basics
- When to stay on Hetzner vs move to AWS
How it's run
- Mostly hands-on. Most of the time is labs. Slides show up only when the next exercise needs them.
- Scoped to your stack. We use your accounts and repositories where that is the point of the day.
- Everyone drives. The group stays small enough that each person gets keyboard time.
- You keep the labs. Scripts and notes stay with the team after the last day.
Request this training
Tell me about the team and I will reply with dates and a quote for this training.
FAQs
What does this training cost?
A training is quoted after the request, not listed as a public price. The quote depends on how many people attend, whether we meet on-site or remote, and how many days you book. Send the form and I reply with a price for that team.
Is the training on-site or remote?
Both. Choose on-site or remote in the request form. On-site I come to your team and we work on your machines. Remote is the same labs over a video call, with everyone on their own keyboard.
Who is the training for?
It is for a company team that wants hands-on time on a stack I run in production. It is not a self-paced video course and it is not a public webinar. Groups stay small so each person drives.
What should we prepare before day one?
A laptop per person, and access to the accounts or repositories you want to use. After we agree dates I send a short checklist. You do not need a finished environment before the request.
Can we book fewer days than the published agenda?
Yes. The agenda is the full version. In the message, name the outcome you care about and I will cut the days to match. The quote follows the days you actually book.
How long is the Hetzner EU production training?
The Hetzner training is two days, from beginner to intermediate. Day one is the Hetzner project, firewall, Docker Compose, and TLS with Caddy. Day two is deploying an app, backups, incident basics, and when to stay on Hetzner versus move to AWS.
Can we run the Hetzner training on our own servers?
Yes. The labs use your Hetzner project, so the firewall, reverse proxy, and backups are the ones your team keeps. You do not need a separate sandbox project unless you want one.
Do we need an AWS account for the Hetzner training?
No. The training is Hetzner-first: VPS, Docker, TLS, and backups in the EU. AWS appears only as the decision of when a workload should leave the VPS.