Archive note, November 14, 2025: This post is based on SoCalNomad infrastructure, security, and operations notes.
Running a public site from a home origin changes the meaning of “free tier.”
Cloudflare’s free services were not a convenience for SoCalNomad. They were part of the architecture.
The project ran on a residential fiber connection with a business account. The origin could serve the site, but I did not want the home network to feel like the edge of the public internet. Cloudflare gave the system a professional front door.
What Cloudflare Solved
Cloudflare handled the parts that a small home-hosted platform should not try to fake:
- DNS.
- TLS.
- CDN caching.
- Edge response behavior.
- A management layer for cache purges.
- A buffer between crawlers and the origin.
None of that replaced good server configuration. Apache, ISPConfig, WordPress, APIs, and headers still mattered. But Cloudflare made the overall system viable by absorbing a class of edge concerns that would otherwise have consumed the project.
The Origin Still Had To Behave
Cloudflare can hide latency on cache hits. It cannot make broken pages correct.
Googlebot still needed valid routes, working sitemaps, sane canonical behavior, usable metadata, and pages that did not collapse under cache misses. Users still needed assets to load. WordPress still needed to produce HTML. APIs still needed to answer.
This became a useful discipline: treat Cloudflare as acceleration and protection, not an excuse.
The origin had to be production-worthy before the edge could make it look effortless.
Caching Became An Operations Problem
The better the cache, the more cache invalidation matters.
SoCalNomad eventually used long-lived Cloudflare caching for parts of the site. That made public pages fast and helped a home origin behave like a more expensive environment.
It also created a failure mode: freshly published WordPress content could exist at the origin while Cloudflare continued serving stale pages.
That is not a reason to avoid caching. It is a reason to make cache purging part of publishing and deployment.
The operations notes eventually included both manual full-zone purges and targeted purge behavior for post publishes. That is the moment caching stops being a checkbox and becomes infrastructure.
Search Console Was The Referee
Google Search Console became a production acceptance test.
It did not care that the stack was clever. It did not care that the origin was home-hosted. It cared whether pages were crawlable, indexable, fast enough, structured enough, and consistent enough to trust.
Getting to green in Search Console was not one change. It was the accumulation of boring fixes:
- Sitemaps that Google could discover.
robots.txtpointing to the right places.- Cache purges when publishing changed visible pages.
- 404 and 410 behavior that did not waste crawl budget.
- Structured data where it made sense.
- A site that responded consistently through Cloudflare.
Cloudflare was indispensable, but Search Console forced the rest of the system to earn the edge.
Free Does Not Mean Amateur
There is a tendency to talk about free infrastructure as if it is only for prototypes.
That misses the point. The value of Cloudflare’s free tier was not that it made the project cheap. It made the project possible at the stage it was in.
A solo project can spend money to avoid problems, or it can spend engineering attention to understand them. SoCalNomad did the latter because that was the constraint.
Cloudflare became the free edge team. The origin still had to do its job.
That combination is what let a residential-fiber system behave like production.