AI can write the app. You still need the map.
Agents draft features fast. A live product still needs the boring layer underneath — domains, hosts, repos, databases, secrets.
Watch someone prompt an agent and get a working screen in minutes. It feels like the hard part disappeared. Then they ask: where does this live? Who owns the domain? Where do logins go? What breaks when I change one file?
The agent wrote the app. The map was still missing.
What “live” actually means
A public URL is not one trick. It’s a stack of small, boring agreements — most of them older than AI IDEs.
Name
A domain you control — so people can find you again tomorrow.
Place
Hosting that serves files (or a build) to the internet.
Memory
A repo so yesterday’s work isn’t lost in a chat scroll.
Truth
A database when the product must remember users, not just draw screens.
Skip any one of those and the demo dies the moment the laptop closes. That’s not a skill issue. It’s a map issue.
When to use which piece
I don’t teach brand names as religion. I teach the job each piece does — so when a tool changes, the mental model doesn’t.
Static pages and marketing sites can live as files on a host. No database required — until someone must log in or save something that isn’t in the HTML.
The moment you need “this person’s stuff,” you need memory outside the chat. A database (or a BaaS that is one) is that memory. Pick it for the job — not because a tutorial used a logo.
API keys and passwords do not belong in the repo people can clone. Env files and host dashboards exist so agents can build without leaking the keys that keep the product yours.
CMS tools, site builders, commerce platforms — I used most of them for years. They weren’t the destination. They were different maps for the same jobs: put something online, remember customers, take money, fix what broke at 11pm.
What AI changes — and what it doesn’t
AI IDEs collapse the time between “I want this” and “a draft exists.” That is real. What they don’t remove is judgment: which layer am I on? Did we ship to a place people can revisit? Are secrets safe? Will tomorrow’s change land in the same repo?
I am not a specialist who memorized one stack. I am someone who kept shipping while tools rotated — and learned the map by getting stuck, then unstuck. The classroom version of that is simple: build something real, name each layer as it appears, and leave with a live URL you can open on your phone.
Chat can write code. A workspace ships it. The week teaches you to stay. None of that sticks if you never learn the map under the URL.
If you’re starting something and want that digital must-know map while you actually ship — Founder Ship Stack is the short door we built for founders and non-tech builders.