Online course · 6 weeks · 47 lessons
Vibe coding course: from prototype to an app in production.
The Production Program is a fully automated online course built for non-developers. In 6 weeks, at about 5 hours a week, you build your own business app with Claude, Lovable and Supabase, then take it live on your own domain, with protected data and payments included.
14-day money-back guarantee · 24 months of access · 12 months of updates
Go-live check
- Access rules enabled on every tablePassed
- No secret keys in the browserPassed
- Payments confirmed by a signed webhookPassed
- Private files, expiring linksPassed
- HTTPS domain, authenticated emailsPassed
- Backup restored and testedPassed
6 of 6 checks passed · 0 alerts
01 · Who it's for
For people with a real need, not a career change
Small business owners and managers
You want your own internal tools or a client portal, without a five-figure quote and without exposing your clients' data.
Freelancers
You want to turn the way you work into an app your clients actually use, and keep improving it yourself.
Employees at larger companies
You already build with AI and want a safe framework: access rules, secrets, backups, personal data.
This program is not for you if
- you want to become a developer: a longer, accredited program is a better fit;
- you can't set aside about 5 hours a week for 6 weeks;
- you're looking for an income promise: there isn't one here.
02 · Outcome
What you'll have after 6 weeks
An app in production
Your business app live on your own domain over HTTPS, with sign-in, roles, tested access rules, Stripe payments, authenticated emails and a backup you have restored. The code is yours and stays in your private GitHub repository.
A security file
Risk map, secrets audit, addressed scan report, access rule test matrix, published privacy policy and recovery plan. The file is analyzed automatically before you go live.
A certificate of completion
Issued automatically when your final project scores 70 out of 100, with both pass/fail criteria met and an average of at least 4 out of 5 on the quizzes. Anyone can verify it online by its number. It is not a state-recognized qualification.
03 · Curriculum
The curriculum, week by week and module by module
7 modules, 47 lessons of 5 to 10 minutes, close to 5 hours of video in total. Every lesson ends with an exercise on your project and every module with a 5-question quiz. The 6 Starter Kit lessons are included.
| Week | Modules | What you avoid | Assessed milestone |
|---|---|---|---|
| Week 1 | M1 and M2 | Building before deciding what to build | Milestone 1: one-page project brief and a list of verifiable tasks |
| Week 2 | M3 | Losing control of the interface, the code and your credits | Milestone 2: main screens built, code in a private GitHub repository |
| Week 3 | M4 | Data readable by any signed-in user | Milestone 3: access rule test matrix passed |
| Week 4 | M5 | Access granted without a confirmed payment | Milestone 4: access granted and revoked automatically, app on your domain |
| Week 5 | M6 | An exposed key, an ignored alert, a fix loop | Milestone 5: security scan report addressed |
| Week 6 | M7 | An app nobody else has ever used | Milestone 6: tests with 3 real users and final project submitted |
M1 · Fundamentals and methodWeek 1
What you avoid · Picking a project that is too big or poorly defined.
What you produce · Scored project sheet, a diagram of your app, accounts and tool budget in place.
- M1-L1 · Welcome: what you will have built in 6 weeks7 minFree preview
- M1-L2 · Vibe coding without the myth9 minFree preview
- M1-L3 · Anatomy of a web application10 min
- M1-L4 · The CADRE method8 min
- M1-L5 · Choosing your capstone project8 min
- M1-L6 · Setting up your workshop: accounts, tools, budget7 min
M2 · Scoping and promptingWeek 1
What you avoid · Paying for every misunderstanding in credits.
What you produce · Milestone 1: one-page brief, context file and 15 to 25 tasks with a definition of done.
- M2-L1 · The one-page project brief with Claude9 min
- M2-L2 · The 6 ingredients of a coding prompt7 min
- M2-L3 · The project context file (Knowledge)6 min
- M2-L4 · Breaking work into verifiable tasks7 min
- M2-L5 · Plan before you build7 min
- M2-L6 · Claude as architect and reviewer7 min
M3 · Lovable from A to ZWeek 2
What you avoid · An interface that drifts and code you don't own.
What you produce · Milestone 2: approved screens, brand guidelines applied, private GitHub repository in sync, backend connected.
- M3-L1 · Interface tour and first project7 min
- M3-L2 · Building the interface step by step7 min
- M3-L3 · Visual edits and consistent design5 min
- M3-L4 · Versions, rollback and what it does not restore6 min
- M3-L5 · GitHub: keeping ownership of your code5 min
- M3-L6 · Managing your credits5 min
- M3-L7 · Backend: Lovable Cloud or external Supabase7 min
M4 · Supabase: data, access, files, functionsWeek 3
What you avoid · An entire table readable by any account.
What you produce · Milestone 3: data model, roles, access rules proven by a test matrix.
- M4-L1 · Modeling your data7 min
- M4-L2 · Creating tables properly (migrations)6 min
- M4-L3 · Authentication: email sign-in link and password6 min
- M4-L4 · Roles and profiles6 min
- M4-L5 · RLS (1): understanding access rules6 min
- M4-L6 · RLS (2): proving it with tests6 min
- M4-L7 · File storage5 min
- M4-L8 · Server functions and secrets7 min
M5 · Payments, going live and your domain nameWeek 4
What you avoid · Access that opens without a confirmed payment.
What you produce · Milestone 4: end-to-end test payment, access granted and revoked by webhook, app on your domain.
- M5-L1 · Stripe: products, prices and test mode6 min
- M5-L2 · Getting paid: checkout page and confirmation5 min
- M5-L3 · Webhooks: granting access after payment6 min
- M5-L4 · TWINT, invoices and VAT: the basics5 min
- M5-L5 · Publishing and connecting your domain name6 min
- M5-L6 · Reliable transactional emails6 min
M6 · Security, data and debuggingWeek 5
What you avoid · An exposed key, an ignored alert, an endless fix loop.
What you produce · Milestone 5: risk map, secrets audit, addressed scan report, privacy policy, tested restore.
- M6-L1 · Thinking like an attacker, in 10 minutes5 min
- M6-L2 · Secrets and keys: the golden rule5 min
- M6-L3 · Security scan and file analysis5 min
- M6-L4 · Swiss FADP and GDPR: the essentials for a small app7 min
- M6-L5 · Debugging with AI5 min
- M6-L6 · Getting out of a loop5 min
- M6-L7 · Backups and recovery plan6 min
M7 · Agents, scaling and business modelsWeek 6
What you avoid · An app nobody else has ever used.
What you produce · Milestone 6: tests with 3 real users, a 5-minute demo, final project submitted.
- M7-L1 · Claude and agents: what changes6 min
- M7-L2 · Automating a task with human approval6 min
- M7-L3 · Scaling: performance and costs5 min
- M7-L4 · Case study: a club management platform6 min
- M7-L5 · Case study: business software shared by several firms5 min
- M7-L6 · Selling what you build: 4 business models5 min
- M7-L7 · Deliver, present and submit your final project5 min
04 · Method
The CADRE method, in the order you apply it
- C
Clarify
Week 1
A one-page brief written with Claude: users, roles, data, screens, what is out of scope.
- A
Architect
Week 2
Your tables and access rules decided before the first screen.
- D
Divide
Week 3
15 to 25 tasks, each with a definition of done you can check on screen.
- R
Realize
Weeks 3 to 5
Lovable builds, Claude reviews, and Plan mode comes before every sensitive task.
- E
Examine
Week 6
Role-by-role tests, including the ones that should fail, then going live.
05 · Support
What supports you, at any hour
The course is fully automated: no instructor, no live sessions, no manual grading. Instead, you get four forms of support available at any hour, answering in seconds or minutes.
The lesson's AI assistant
Ask your question under any lesson: the assistant answers based on the lesson's content. Every video also comes with a written step-by-step guide, including the text to copy. AI answers can be wrong: decisions about your app remain yours.
- One rule per table
- Testing with two accounts
- Common mistakes
Your question
How do I stop one client from seeing another client's files?
Lesson AI assistant
Enable an access rule on the files table that compares the file's owner with the signed-in account, then test with two client accounts.
Lesson passage at 04:12
Ask a question about this lesson
Automated milestone assessment
You submit each of your 6 milestones and get an assessment within minutes, criterion by criterion, with a verdict and suggested fixes. You fix, you resubmit.
Milestone 2 · Architect
- Tables and relationships
- 5/5
- Access rules by role
- 4/5
- Test data
- 4/5
- Consistency with the scope
- 5/5
Verdict
Milestone approvedAdvice
Add a cross-access test between two client accounts before moving to the next step.
Feedback within minutes
Automated security file analysis
Before you go live, your security file is analyzed automatically. The most common finding: an access rule that is too broad, tightened so each user only sees their own data.
dossiers · RLS
USING (true)USING (auth.uid() = owner_id)Before you go live, your security file is analyzed automatically. The most common finding: an access rule that is too broad, tightened so each user only sees their own data.
The certificate of completion
As soon as your final project reaches the threshold, the certificate is issued automatically, with a number anyone can verify online. It shows that you completed the program; it is not a state-recognized qualification.
Probata Academy
A certificate of completion
PA-2026-XXXX
Issued automatically when your final project scores 70 out of 100, with both pass/fail criteria met and an average of at least 4 out of 5 on the quizzes. Anyone can verify it online by its number. It is not a state-recognized qualification.
06 · Figures
Why going to production takes a method
Four figures from primary sources, with their dates. The problem isn't the tool, it's the lack of checks before going live.
company apps built with vibe coding platforms and publicly accessible exposed sensitive data, out of about 5,000.
Lovable projects analyzed had inadequate access rules.
Matt Palmer, statement on CVE-2025-48757 · May 29, 2025
or so of AI-generated code fails security tests when no security instruction is given.
Veracode, 2026 GenAI Code Security Report · July 28, 2026
more critical vulnerabilities after five rounds of AI code fixes.
07 · In practice
Prerequisites, time and tool budget
Prerequisites
No coding knowledge. A computer, an up-to-date browser, and everyday comfort with spreadsheets and email. A real project, even a fuzzy one: module 1 helps you choose it using 5 criteria.
Time
About 5 hours a week for 6 weeks: lessons of 5 to 10 minutes, and the rest of the time on your project. Your access lasts 24 months, so you can move at your own pace.
Tool budget
About 50 a month in your currency while you build, mostly for Lovable and Supabase. The lesson “Setting up your workshop” helps you estimate it. Third-party tool subscriptions are your responsibility.
Language
Every lesson comes as an English and a French video, with captions in each language and a written step-by-step guide.
08 · Pricing
One price, everything included
Production Program
24 months of access · 12 months of updates
- 7 modules, 47 lessons, plus the 6 Starter Kit lessons
- AI assistant and step-by-step guide under every lesson
- 7 quizzes and 6 milestones assessed automatically
- Automated security file analysis
- Certificate of completion issued automatically
14-day guarantee
If the Program isn't right for you, request a full refund within 14 days of purchase, provided you have completed fewer than 2 modules. One email is enough, no questions asked. The refund ends your access.
Prices include applicable taxes for individuals; businesses are invoiced excluding VAT where applicable, depending on your country. Invoice in your company's name on request at checkout.
Bought the Starter Kit in the last 30 days? Its price () is deducted from the Program automatically.
For 5 people or more, the Team Program bundles the licenses with a company dashboard to track progress, on request.
Explore the Team Program09 · Comparison
Three ways to learn vibe coding
Most offers you'll find fall into one of these three formats. Each has its place; here is what sets them apart.
| Criterion | Short video courses | Long instructor-led programs | Production Program |
|---|---|---|---|
| Format | Videos to watch, often with no assessed exercise | Several months, sessions and mentors on a fixed schedule | 6 weeks online, at your own pace, milestones assessed automatically |
| Deliverable | A demo app | Depends on the program | Your app, in production on your domain |
| Security | Rarely covered | Sometimes one module | Dedicated module, tested access rules, file analyzed automatically |
| Help | Comments or a forum | An instructor, at scheduled times | AI assistant under every lesson, at any hour |
| Price | Low | High, sometimes eligible for public funding | , 14-day guarantee |
| Recognition | Rarely a certificate | Certificate, sometimes an accredited qualification | Verifiable certificate of completion, not state-recognized |
Comparison of vibe coding course formats
Short video courses
- Format
- Videos to watch, often with no assessed exercise
- Deliverable
- A demo app
- Security
- Rarely covered
- Help
- Comments or a forum
- Price
- Low
- Recognition
- Rarely a certificate
Long instructor-led programs
- Format
- Several months, sessions and mentors on a fixed schedule
- Deliverable
- Depends on the program
- Security
- Sometimes one module
- Help
- An instructor, at scheduled times
- Price
- High, sometimes eligible for public funding
- Recognition
- Certificate, sometimes an accredited qualification
Production Program
- Format
- 6 weeks online, at your own pace, milestones assessed automatically
- Deliverable
- Your app, in production on your domain
- Security
- Dedicated module, tested access rules, file analyzed automatically
- Help
- AI assistant under every lesson, at any hour
- Price
- , 14-day guarantee
- Recognition
- Verifiable certificate of completion, not state-recognized
Not ready for 6 weeks?
Starter Kit
6 lessons to scope your project. Price deducted from the Program within 30 days.
Starter Kit10 · Questions
Frequently asked questions about the Production Program
Do you need to know how to code to take the Production Program?
No. You learn to describe precisely what you want, check what the AI produces and test it with real accounts. Reading a change plan or an access rule is something you can learn without becoming a developer. If you can use a spreadsheet and write a clear email, you have the starting level you need.
How much time should you plan each week?
About 5 hours a week for 6 weeks. Lessons last 5 to 10 minutes; the rest of the time, you work on your project by following the step-by-step guide. Your access lasts 24 months, so if one week is busy, you can pick up later without losing your progress.
How much do the tools cost during the course?
Plan on about 50 a month in your currency while you build, mostly for Lovable and Supabase. These subscriptions are your responsibility and are not included in the Program price. The first week teaches you to estimate this budget, and module 3 shows you how to keep your credit usage down.
Is there an instructor or are there live sessions?
No. The course is fully automated. You are supported by the AI assistant under every lesson, the automated assessment of your 6 milestones, the automated analysis of your security file and a certificate issued automatically. Everything is available at any hour, with no appointment to book.
What kind of app can you build?
An internal tool, a client portal, a booking app with payments: a real need, known users and three roles at most. Module 1 helps you pick a project you can finish in 6 weeks, using 5 criteria. The lessons use Dossiers Clair, a fictional client portal you can explore online.
Is the certificate an accredited qualification?
No. The Probata Academy certificate of completion is not a state-recognized qualification. It is issued automatically when your final project scores 70 out of 100, with both pass/fail criteria met and an average of at least 4 out of 5 on the quizzes. Anyone can verify it online using its number.
How does the 14-day guarantee work?
If the Program isn't right for you, email us within 14 days of purchase, provided you have completed fewer than 2 modules. The refund is in full, made to the payment method you used, and ends your access. This guarantee applies to the Production Program; the full conditions are in our terms of sale.
Is the Starter Kit price deducted from the Program?
Yes. If you bought the Starter Kit within the 30 days before buying the Production Program, its price is deducted automatically at checkout, in the same currency. There is nothing to request. The 6 Kit lessons stay available to you, since they are also part of the Program.
Can your employer pay for the course?
Yes. Your company can pay directly: an invoice is issued in its name, excluding VAT where the rules allow. The Program is not eligible for public training funds such as France's CPF. To train 5 people or more, the Team Program adds a company dashboard to track everyone's progress.
What happens when Lovable or Supabase change?
The CADRE method doesn't depend on any one tool: clarify, architect, divide, realize and examine still apply. When an interface changes, the affected lessons are updated, and you receive those updates for 12 months. The step-by-step guides also flag labels that may vary.
In 6 weeks, your app can be running in production.
· 14-day money-back guarantee · 24 months of access