Cloud as Lego Bricks

Narrated

You have a real application now. Authentication, database, file uploads, background jobs, queues, payments, GDPR compliance, monitoring, Docker containers, load balancing. You built all of this. It works. And right now, it’s running on Vercel.

Vercel is managed hosting. You push code, it deploys. You don’t think about servers, you don’t worry about operating systems, you don’t SSH into anything. That’s the whole point. And for a lot of apps, that’s all you’ll ever need.

But there are reasons you might want more control. Maybe you want to run your Docker setup from Lesson 23 on a real server. Maybe you want to understand what’s actually underneath Vercel — what it’s doing for you. Maybe you have a use case that needs a persistent server: a background process that runs 24/7, a database you want to manage yourself, a service that doesn’t fit the serverless model. Or maybe you just want to prove to yourself that you can put an app on a raw cloud server and make it work.

This lesson is about self-hosting. Taking the Docker setup you already have and running it on a real server in the cloud. Not instead of Vercel — alongside it as a skill you understand. You’ll see both paths: the managed path you’re already on, and the self-hosted path that gives you full control.

The cloud isn’t one big intimidating thing. It’s a catalog of individual pieces — like Lego bricks. You pick the ones you need, snap them together, and build exactly the infrastructure your app requires. Let’s open the catalog.