Launch: Your Code, Your Domain, a Real Address

You've made a lot by now. But it all still lives inside the Studio. When this course ends, that changes. A real address you can send a friend with "here's my site", your own domain that opens from any search bar, a public project collecting feedback and cheers on the Launchpad. You go from someone who made things to someone who launched them.

The word launch can drag along words like server, deploy, and DNS until they feel like a wall. It's fine. This course dissolves that wall brick by brick with term cards, and the actual buttons take a few clicks. The scary part is the names, not the substance.

And one more theme runs through this course: ownership. The code, the data, and the domain are yours. You'll confirm that launching isn't binding yourself to a platform. It's planting your own assets in the world.

Press the code tab in the Studio and the entire source code of your current build appears. Not one line hidden. Can't read it? That's fine. What matters is that you can always see all of it, copy it, and take it with you.

Why does this matter? Some tools cage your results inside themselves; leave the tool and nothing leaves with you. VibeCampus is the opposite. The code of what you build is wholly yours, so you can move it anywhere, show it to any developer, and edit it yourself.

Skim the code and, surprisingly, parts of it read. When button labels, color codes, and section titles start surfacing, that's the first step of code turning from alien script into a document.

Press the download button and the build comes down as a file. That file is a complete copy on your computer. Internet down, whatever happens, your work stays in your hands.

The downloaded file opens straight in a browser. Double-click it, and the site you were just viewing in the Studio opens from your own machine. Watching it open with no server is a wonderful moment for understanding what the web really is.

For important builds, get in the habit of downloading each version and filing them into folders. Name them v1, v2, and you've built your own archive of history.

The handoff pack is the download's complete edition. Alongside the finished product (index.html), you get a README covering running, hosting, and backend connection, plus AGENTS.md, the document that hands the project over to AI tools. All in one zip. Free.

The power of this zip is continuity. Unzip it and open it in Claude Code, Cursor, or VS Code, and those AIs read AGENTS.md and continue the work already understanding the project. Hand it to a developer and the README makes explanations unnecessary.

And it's built so forms, members, and chat keep working wherever you put it. Moving boxes where the power and the water are already running when you arrive.

An embed is a copy-paste code fragment that slots your work inside another page. Even with a blog or company homepage already running, the promo videos and content you made in the Studio can go inside them.

On the video embed page, paste in any video address, a Studio promo, YouTube, or Vimeo, and it produces embed code with the aspect ratio, muted autoplay, looping, max width, and corner rounding all set. Copy it, paste it where you want it, done.

As launch strategy, embeds are a bridge. You don't abandon your existing channels; you lay your new creations on top of them, connecting the two worlds.

Now, the address. Publishing alone grants a free address, but if you're building a brand, you'll want your own domain. Nobody needs convincing that myflower.com belongs on a business card and mysite-abc123 doesn't.

Around the word domain travel two constant companions: DNS and SSL. The three cards below sort them out, so open each one. With these three you can follow most domain conversations.

And some advance reassurance: on VibeCampus you'll rarely touch any of the three directly. Know the concepts, and the tool presses the buttons.

Type the name you want on the domains page and you check registration status across the world's domains at once. It queries public registry data live, showing available or already taken on the spot. Searching is free, even without an account.

Prepare three or four candidate names. The name you had in mind is already taken more often than you'd think. If .com is blocked, considering other endings like .co or .kr is a legitimate move.

Found an available name? You can carry straight through to purchase. Register through VibeCampus and it auto-connects to your published build with no DNS setup needed. In the next step, you also learn the road for connecting a domain you already own.

Already own a domain? Attach it to your published build on the connect page. The flow is three moves. Add the domain and the screen shows DNS records (type, host, value); add those exact values in the management screen of the registrar where you bought the domain; then come back and press Verify DNS.

Once verified, hosting and HTTPS finish automatically, and when it's done the status flips to live. All you did was copy and paste, and behind the scenes the phone book entry and the lock issuance are complete.

If publishing feels scary, that's okay. You can always flip back to private, and a domain connection can be undone. Launch isn't an irreversible stamp; it's an adjustable switch.

What actually happens when you press publish? Your work goes up onto a computer that's always on, a free address that opens anywhere in the world is issued, and the backend switches on automatically. That whole process is called a deploy.

This used to take days: renting a server, configuration, security, certificates. You now finish all of it with one button. Still, knowing what happens behind the button makes you the person who knows where to look when something goes wrong.

The three cards below sort out deploy, hosting, and server. The three chain into one sentence: a deploy is moving into the building called a server and receiving hosting.

The handoff pack gave you the code; now let's talk about protecting it. Developers record code in a version control system called Git, and store that record in an online vault called GitHub. The three cards below are the keys to this world.

The commands on screen are the three lines that leave a first record in your downloaded project folder. git init declares that this folder's history will be recorded, git add picks the files to record, and git commit presses the stamp along with a message. Run them and a save point named v1 first launch exists.

It's not mandatory today. But the more precious a project becomes, the more those save points are worth. The moment you unzip the handoff pack and run those three lines, your code gets one layer safer from mistakes and accidents.

$git init
$git add -A
$git commit -m "v1 — first launch"

[main (root-commit) a1b2c3d] v1 — first launch

As important as the code is the data. If bookings, members, and order records sit in a platform-owned warehouse, leaving means leaving them all behind. VibeCampus is structured differently. Connect a backend and the data is stored directly in a database you own (Supabase), from the very start.

What that structure means shows up on moving day. Take the code away with the handoff pack and host it elsewhere, and because the database lives in your account, the forms, the members, and the data carry on seamlessly. Not a move where you pack everything up, but one where you change houses and the furniture is already in place.

Before launch, check just once. If the build has forms or login, is the backend connected, and is data stacking up in your dashboard? That one check protects your future ownership.

Launch is not the end; it's the start of operations. When edits are needed, three roads lie open. First, continue in the Studio: refine chat and Click to edit, fixing things exactly the way you have been. The easiest road.

Second, the handoff pack plus AI tools: download the code and work on it directly in tools like Claude Code or Cursor. Thanks to AGENTS.md, those AIs start already understanding the project. Third, hand it to a person: code with a README can be picked up by any developer immediately.

The three roads don't block each other. The Studio for the everyday, AI tools for big overhauls, people for the specialist territory. Being able to switch lanes as the situation demands is itself the privilege of owning your code.

You have an address; time to announce it. The Vibe Launchpad is the stage for showing the world what you're building and what you've launched. Press register a project, fill in the name, the one-line intro, the description, the category, and the live URL, and you're public.

Public projects collect feedback, and people who like them send credits as boosts to cheer you on. Pre-launch, you can gather a waitlist with notify me at launch; the moment you flip the status to launched, every waiter is notified at once.

Pour your effort into the one-line intro. In the list, that one line is all people read. Get what it does and who it's for into a single sentence, and the clicks follow.

The class's final mission. The Try it now button below holds a one-page site prompt for a neighborhood flower boutique: a seasonal catalog and an order form. Small, and real.

This time we don't stop at building. Publishing, and announcing, are the mission. Complete this loop yourself and you're no longer someone who knows about launching. You're someone who has launched.

Congratulations. From the excitement of the first fifteen minutes through prompts, websites, apps, games, media, editing, trust, and now launch. You've completed the entire class. The works stacked in your Studio and a real address are the proof.

You can now run the full loop alone: idea to screen, screen to verified work, verified work to an address in the world. This ability doesn't disappear. It only gets faster and deeper with repetition.

And there's a next door. You've learned to build; now come learn to sell and to grow. In the Solo Founder School, a journey awaits that turns what you make into a business: idea validation, the funding market, teams, and marketing. The door is open.