Why the Cloud
You can prototype in minutes — but you cannot share it yet. The cloud closes that gap. Here is what it is, why you need it, and how every tool in this programme uses it.
You just built things in ChatGPT, Gemini, and Claude that looked real. A compliance table. A screen layout. A draft letter. They felt finished.
But try this: send a link to that prototype to a client. Ask them to open it on their phone. Let two colleagues use it at the same time.
You cannot. It only exists in your chat window. The moment you close that tab, it is gone.
This is the gap between a prototype and a product. And the cloud is what closes it.
The Problem with "It Lives on My Computer"
Most CA firms still depend on one computer — or one server in the office — for critical data and work.
That setup has four hard limits:
| Problem | What actually happens |
|---|---|
| Need to be physically present | Work is limited to your office computer. Client calls at 9pm — you cannot check the file from home. |
| Risk of data loss | Hard disk failure, virus, or theft can cause permanent loss. No redundancy. |
| Difficult to collaborate | Files are emailed back and forth. Version confusion. Two people cannot edit the same document at the same time. |
| Scaling requires buying servers | More clients means buying expensive hardware, paying for power and maintenance, managing IT support. |
As your practice grows, these problems get bigger, costlier, and riskier — at exactly the moment when you can least afford them.
What the Cloud Actually Is
Cloud computing means using servers, storage, databases, and applications over the internet — instead of owning physical hardware.
The simplest analogy: internet banking for computing.
| Old way | New way |
|---|---|
| Visit the bank branch — only option | Bank anywhere — 24×7 access |
| Do transactions with limited timing | Do transactions anytime, anywhere |
| Carry cash and documents — risk of loss | Secure and protected, backed up always |
Before internet banking, you had to physically visit a branch to access your money. The bank moved its operations to the cloud — and you gained freedom, security, and access from anywhere without building your own vault.
The cloud does the same thing for your data and applications.
What You Get
Once your application lives in the cloud, four things become true:
1. Access from anywhere, on any device Your client can open it on their phone. You can check it at a restaurant. Your article can update records from home.
2. Automatic backup and strong security Cloud providers run on redundant infrastructure. Your data is backed up multiple times across data centres. No single hard drive failure wipes your work.
3. Easy collaboration Multiple people use the same live application at the same time — each with their own login, their own view, their own data. No emailing files.
4. Scale instantly and pay only for usage Start with 10 users. If you grow to 10,000, you scale with a click. No upfront hardware investment. No maintenance costs. You pay for what you use.
The Three Cloud Layers You Care About
You do not need to understand all of cloud computing to build software. You need to understand the three pieces that every app in this programme uses:
| Cloud service | What it does | Your app's equivalent |
|---|---|---|
| GitHub | Stores your code in the cloud. Version history, collaboration, backup. | Your firm's document management system — but for code. Every change is tracked. |
| Supabase | Your cloud database. Stores your app's data (students, fees, filings). Accessible from anywhere. | The cloud filing cabinet. Secure, structured, always available. |
| Vercel | Publishes your app to the internet. Gives it a live URL anyone can visit. | The building your firm operates from — except anyone in the world can walk in. |
These three services together answer the question you could not answer after the prototyping exercise:
- Where does the code live? → GitHub
- Where does the data live? → Supabase
- How do people visit the app? → Vercel
The Roadmap from Here
This is where the programme's shape becomes clear:
| Session | What you learn | What it solves |
|---|---|---|
| S1 (now) | Command line, code, AI prototyping | You understand what software is and can describe products |
| S2 | How AI works | You understand the tool you'll use every day |
| S3 | VS Code, Git, GitHub, Supabase, Vercel | You set up the three cloud services that close the gap |
| S4 | Claude Code | You use AI to build inside those services, not just prototype |
| S5+ | Build real products | You ship live applications people can actually use |
The gap you felt at the end of the prototyping exercise — "I made this, but I can't share it" — is exactly what Sessions 3 and 4 are designed to close.
Before you move on — can you do all of this?
Click each item you're confident about. Bring the unchecked ones to your next session.
I understand why a prototype in a chat window is not the same as a published product
I can explain the four problems with keeping everything on one computer
I can explain the cloud analogy: internet banking removed the need to visit a branch; the cloud removes the need to depend on one physical machine
I know what GitHub, Supabase, and Vercel each do at the application level
I understand why Sessions 3 and 4 come next in this sequence