I Fired My Host: Why I Rebuilt My Infrastructure
I looked at my infrastructure and I got absolutely furious. My hosting provider (df.eu) was useless - dashboard from 2005, subdomain SSL extortion, no Next.js support, monthly fees just for an email inbox. It was time to fire my host. I built a high-efficiency low-cost stack instead: Cloudflare for DNS and SSL, Vercel for hosting, Amazon SES for email. No more fighting my own infrastructure.
>The Solution: I built a high-efficiency Low-Cost Stack using Cloudflare (DNS/SSL + Free Gmail Forwarding), Vercel (Hosting), and Amazon SES (Email API).
Reality Check //
This is not "free." You pay for domains. You pay SES usage. But you stop paying for idle servers,
outdated interfaces, and monthly inbox fees.
InfrastructureProduction ReadyCost Optimized
Why I Fired My Host: The Stack That Doesn't Fight Back
I needed infrastructure that doesn't fight me. The old host blocked everything I wanted to build. This stack removes the blockers.
Automatic SSL
Wildcard SSL certificates for all subdomains. No extra fees. No manual configuration.
Cloudflare handles it.
Free Email Forwarding
Professional email addresses that forward to Gmail. Zero monthly fees. Cloudflare Email
Routing makes it happen.
Next.js Native
Vercel is built for Next.js. Edge functions, API routes, automatic deployments. No PHP on
Apache nonsense.
Cost Efficient
Pay for what you use. No idle server fees. No monthly inbox charges. Just domain costs and
actual usage.
Platform Features
Everything you need to run modern web apps. This stack is built for performance, simplicity, and cost efficiency. It gets out of your way so you can build.
Wildcard SSL Certificates
Automatic SSL for all subdomains. No configuration. No extra fees.
Email Routing & Forwarding
Free email forwarding to Gmail. Professional addresses without monthly fees.
Next.js Edge Runtime
Native Next.js support with edge functions, API routes, and automatic deployments.
Scalable Email API
Amazon SES for transactional emails. $0.10 per 1,000 emails. Industry standard reliability.
Global CDN & DNS
Cloudflare's global network for fast DNS resolution and content delivery worldwide.
Modern Dashboard
Clean, fast interfaces. No 2005-era dashboards. Tools that work in 2026.
The Truth About Costs (Radical Transparency)
Reality Check //
Be clear before you cancel your current contract. This is not a magic "$0" empire.
Cloudflare: The free tier includes Wildcard SSL and Email Routing. This saves me the specific costs that made me angry, but remember: you are the product.
Vercel: The Hobby tier is excellent for personal projects. But if you build a commercial app that scales, you will hit bandwidth limits and you will pay.
Amazon SES: It is cheap ($0.10 per 1,000 emails), but it is not free. You need a credit card.
Your Domain: You always buy this. There is no hack around ICANN fees.
This stack reduces waste. It does not eliminate the cost of doing business.
The Philosophy: Why I Fired My Host
My goal wasn't just to save $30/month. My goal was to stop being blocked by my own infrastructure.
I am a Builder. I need tools that work in 2026.
The UX Pain: The DomainFactory dashboard was a relic. Navigating it felt like archaeology. I need modern, fast, clean interfaces - not a struggle against a UI from the dark ages.
The Inbox Pain: They offered no decent free email. I refused to pay Google $6/month just to receive mail at [email protected]. I wanted to forward it to my free Gmail.
The SSL Pain: I spin up subdomains constantly. My old host wanted $5/month per subdomain. Ridiculous.
The Tech Pain: I need Next.js and Vector solutions for my AI models. My old host offered... PHP on Apache. Useless.
Pro Tip //
If your hosting provider's dashboard looks like it was built before 2015, that's a red flag.
Modern tools have modern interfaces. Period.
The Components
I am using enterprise-grade tools. They are powerful, but they require actual configuration.
CloudflareVercelAmazon SES
1. The Bouncer: Cloudflare (DNS, SSL & Email)
Cloudflare is the new boss of my domain.
The "Free Inbox" Hack: Email Routing. This is the MVP feature. Cloudflare catches emails sent to [email protected] and forwards them to my private Gmail. I reply from Gmail. It looks professional, but costs $0 extra.
The Kill Feature: Automatic Wildcard SSL. I can create app.bernhardrieder.com or ai.bernhardrieder.com. Cloudflare secures them all automatically.
>The Kill Feature: Automatic Wildcard SSL. I can create app.bernhardrieder.com or ai.bernhardrieder.com. Cloudflare secures them all automatically.
2. The Host: Vercel
I use Next.js. Hosting this on a traditional shared server is painful. Vercel is built for it. It handles my frontend and the API routes for my custom newsletter tool. It works - but watch your build minutes.
Build Limits //
Vercel's Hobby tier has build minute limits. If you're building commercial apps, monitor your
usage. You will hit limits and you will pay.
3. The Robot: Amazon SES
My custom newsletter tool needs to send thousands of emails. I don't need a UI for that; I need a raw API. Amazon SES is the industry standard. It costs pennies compared to Mailchimp, but setting up the reputation/verification is a grind.
The Surgery: How I Switched
Moving a live domain is stressful. I don't care how many times you do it - there is always that moment of panic where you think you broke the internet.
Phase 1: The Hostile Takeover
I logged into DomainFactory. I found the Nameserver settings. It was full of expensive legacy junk.
I deleted them. I pasted in the two Cloudflare nameservers: derek and hera.
The dashboard screamed at me in German: "Die Einstellungen auf dieser Seite sind unwirksam!" (The settings on this page are ineffective!). Good. That was the point.
Nameserver Change //
DNS propagation can take 24-48 hours. Don't panic if things don't work immediately. Cloudflare
usually takes over within a few hours.
Phase 2: Killing the Zombies
Once Cloudflare took over, I saw the mess I left behind. There were A-records for pop3, imap, and smtp pointing to the old server IP 216.198.79.1.
This is the digital equivalent of keeping old keys to a house you sold. I got a bit manic here. I started hitting delete.
imap? Gone.
smtp? Gone.
Wildcard *? Gone.
If it points to the old server, it dies.
Phase 3: Wiring the Robot (SES)
This is the tedious part. To let Amazon send emails as "Me," I had to prove I own the domain. Amazon gave me 3 CNAME records. I pasted them into Cloudflare.
Then came the waiting game. "Verification Pending." "Verification Pending."
I hate waiting. It makes me pace around the room muttering about propagation times. You have to sit on your hands and trust the system.
Then - pop. Verified. Green tag. The robot is authorized.
The Aftermath
It is quiet now.
The old server is cancelled. My subdomains get SSL certificates automatically. My professional emails land in my free Gmail. My custom newsletter tool sends via SES. My Next.js apps run on the edge.
It works. It is clean. It is efficient.
>There is a specific feeling when a complex system finally hums along without friction. It's not excitement. It's just... relief. Smooth, quiet, deeply satisfying relief. Like a schmuse-katze finding the perfect sunbeam. 🐱
Everything is exactly where it belongs.
Mission Accomplished //
The stack is live. The old host is cancelled. I'm back to building instead of fighting
infrastructure.
Now I can stop playing sysadmin and get back to what I actually do: Building.