Nothing gets built in the air. Cloudflare and GitHub go in first — every system, every deployment, every piece of the stack lands on top of what we establish here.
There's a temptation to start building the exciting stuff first — the RAG, the agents, the course experience. Resist it. The two tools in this module are invisible when they work and catastrophic when they're missing. They are the ground everything else stands on.
Cloudflare manages every domain in the Cyber Coastlines ecosystem, routes traffic intelligently, and sits as the security perimeter in front of every web property. GitHub is the version control layer — every workflow, prompt template, configuration file, and custom integration built during this sprint gets committed here. If it isn't in GitHub, it doesn't exist.
Together these two tools answer a question that most solo operators never think to ask until something breaks: if the laptop is lost, if the consultant is unreachable, if something fails at 2am — does the system know how to recover? After this module, the answer is yes.
Infrastructure is the work nobody sees. It's also the work that determines whether everything else survives contact with reality.
Cloudflare sits in front of everything. It manages DNS for all six ecosystem domains — the .ai extensions for systems and methodology, the .com extensions for brands and stories. Every request that hits any Cyber Coastlines web property passes through Cloudflare first.
That means faster load times globally through CDN caching, DDoS protection without configuration, and a single control panel for the entire domain hierarchy. When the RAG intelligence layer goes live in Module 02, Cloudflare also acts as the access control layer — ensuring that the vault is never exposed directly to the public internet regardless of which hosting path the consultant recommends.
The free tier covers everything this ecosystem needs indefinitely. This is one of the rare tools in the stack where the free tier is genuinely, completely sufficient. There is no reason to pay for Cloudflare Pro at this stage of growth.
GitHub is the institutional memory of the sprint. Every piece of code, every configuration file, every prompt template, every workflow diagram, every SOP — if it was built during these eight days, it lives in GitHub. Permanently. With full version history.
This isn't a developer preference. It's a non-negotiable operational requirement. The entire point of this sprint is to build systems the founder can run independently. That requires documentation that doesn't disappear when the consultant leaves. GitHub guarantees that continuity.
All repositories must be set to private before any code is committed. No exceptions. The ecosystem IP and system architecture are proprietary — they do not belong in a public repository under any circumstance, regardless of how harmless an individual file might seem.
Cloudflare and GitHub don't directly talk to each other — but they work together as the two load-bearing walls of the entire stack. Everything else in the Cyber Blueprint touches one or both of them at some point in its lifecycle.
Module 01 is not complete until two things are true: every ecosystem domain resolves correctly through Cloudflare, and the first commit has been pushed to the sprint repository in GitHub. Do not begin Module 02 until both are confirmed. The vault requires a functional DNS layer and a version-controlled environment before the first line of RAG architecture is written.
Module 02 is where it gets interesting. The vault goes in next — and everything that follows depends on getting it right.