A 6-week live cohort · Starts the week of Oct 19

Your vibe-coded app works. Now make it production-grade.

A live, follow-along course that moves your Lovable, Replit, or Vercel app onto AWS infrastructure you own. Four quick questions to see if it's a fit.

6 weeks Live + recorded Weekly office hours $250 first cohort
~/fit-check

$ Have you built an app yet?

$ less ./details

Want the details before you reserve? Open whatever you're curious about.

$ cat ./how-it-works.mdHow the first cohort works
  1. 01

    Reserve your seat.

    Free. No card. Takes one minute.

  2. 02

    We hit 25.

    I won't start Session 1 or collect money until 25 people reserve.

  3. 03

    You get a payment link.

    $250, due by October 14 — five days before Session 1. If you've changed your mind, just don't pay.

  4. 04

    Session 1 starts

    The week of October 19, 2026.

If we don't reach 25 by October 9, nobody pays anything and I'll tell you what happens next.

$ diff platform.yml aws.ymlWhy move off the platform
cost

Predictable cost

Usage-based platform credits get hard to predict as you grow. Serverless can run for very little at low traffic, and cost scales roughly in line with usage.

availability

Availability you control

You decide the redundancy, the monitoring, and the alarms — instead of waiting on someone else's status page.

ownership

Ownership

Your code, your data, your AWS account. Nothing to export later, because it's already yours.

portability

Portability

No single vendor between you and your users. Standard building blocks you can move, extend, or hand off.

$ ls ./curriculumThe 6-week curriculum

Every session is follow-along: you do each step on your own app while I teach it.

WEEK 01

Get your code out and understand what you have

Export to GitHub, run it locally with Claude Code, and map every dependency — auth, database, storage, env vars, third-party APIs. Set up your AWS account safely: IAM, MFA, billing alarms.

You'll have your app running locally and a migration map.
WEEK 02

Frontend on AWS

S3 + CloudFront, your domain in Route 53, SSL with ACM, and automated deploys from GitHub.

You'll have your frontend live on your own AWS account.
WEEK 03

The API layer

Move server logic and edge functions to Lambda + API Gateway. Secrets management, CORS, environments.

You'll have your backend running serverless.
WEEK 04

Data and auth

DynamoDB vs. a relational option vs. keeping your current database; migrating data; auth options (Cognito or keeping your provider); file storage on S3.

You'll have your data and users on infrastructure you control.
WEEK 05

Production readiness

Infrastructure as code, staging vs. production, CloudWatch logs and alarms, backups, and basic load testing.

You'll know when something breaks before your users do.
WEEK 06

Cost, scale, and cutover

Cost modeling at 10x and 100x traffic, caching, a zero-downtime DNS cutover, and a rollback plan.

You'll switch real traffic to your new stack.

Exact topics per week may flex to what the cohort is actually running into.

$ cat ./includes.jsonWhat's included
live

Live weekly sessions

Follow along and do each step on your own app while I teach it.

recorded

Every session recorded

Miss one or need to rewatch a step? It's there.

office-hours

Weekly office hours

Bring your specific app, your specific error, your specific question.

cohort

Private group chat

25 people solving the same problems at the same time — built into the platform we use for the live sessions.

# The weekly session time is picked by a cohort poll before Week 1. Can't make it? Every session is recorded and shared so you can follow along on your own time.

$ whoamiWho's teaching this
Yash Ambardekar

The path I actually use — taught live, on your app.

I'm Yash. I've spent years architecting and running serverless SaaS products on AWS — including Support Caddie and CMS Caddie — built to handle real traffic while keeping hosting costs low.

Vibe-coding platforms are the fastest way I've ever seen to get from idea to working app. But the platform that gets you to v1 usually isn't where you want to run v10.

This course is the path I actually use, taught live, on your app.

$ man vibecodelessonsFAQ
What happens if 25 people don't sign up?

Nobody is charged — you never entered a card. I'll email everyone with what's next.

When do I pay?

Only after 25 seats are reserved. You'll get a payment link, and payment is due by October 14 — five days before Session 1.

When are the live sessions?

Once a week, starting the week of October 19. Before Week 1 I'll poll the cohort and pick the time that works for the most people. If you can't make it, every session is recorded and shared so you can catch up on your own time.

Do I need to know how to code?

No, but you need to have built something on a vibe-coding platform. We use Claude Code throughout to do the heavy lifting.

What do I need?

Your app's code (exportable to GitHub), a Claude subscription for Claude Code, an AWS account, and your domain.

What will AWS cost me?

For most early-stage apps, very little — often within free tier or a few dollars a month. We set up billing alarms in Week 1 so there are no surprises.

What if my app uses Supabase / Firebase / something else?

Common. Week 1's dependency map covers it, and Week 4 covers whether to migrate or keep it.

Will the price stay at $250?

Only for this first cohort. Prices go up for the next one.

Can I get a refund?

Yes, pro-rated. If you cancel, you're refunded for the weeks left out of six, counting from the week you ask. Cancel during Week 2, for example, and you get 4 of 6 weeks back — about $167. Cancel before Session 1 and you get it all back.

Is this affiliated with Anthropic, AWS, Lovable, Replit, or Vercel?

No. Vibe Code Lessons is independent.

First Cohort

This is the first cohort, and $250 is a first-cohort price — it goes up for the next cohort. Future cohorts will also likely be larger.

Back to my reservation ↑