Courses with modules and video lessons
Video uploaded and served from your app's own quota, through a signed URL, not as a public file any learner can copy and pass on.
What gets built
Four things you could have working this week
Not a feature list. These are the apps people actually describe, and what the platform hands back when they do.
Enrolment as an access rule
A lesson does not open for someone who is not enrolled, and that is decided in the database. A leaked link does not become access.
Progress, certificates and materials
Progress saved per lesson, PDFs attached, and a certificate issued when a learner reaches one hundred per cent.
One-off purchase or subscription
Buy one course, buy the catalogue, or subscribe monthly, plus a public page per course for search engines to find.
Included
The parts nobody wants to build twice
Database, login, payments and publishing are part of the platform, not a list of services you go and wire up afterwards.
A real database, not a form dump
Every screen reads and writes models you can open, query and export. The data is a database of yours from the first minute, not a spreadsheet the app pretends to read.
Login for your own users
Email, magic link and Google sign-in, with roles and per-record ownership enforced by Postgres itself. A badly written screen cannot become a leak, because the database answers empty.
Payments that land in your account
Stripe, Pagar.me and Mercado Pago connect once. Card, Pix, boleto and subscriptions, with the card fields rendered by a hosted vault your app never touches.
Web, installable, and in the stores
One project published three ways: your own domain, an icon on the phone straight from the browser, and a signed binary submitted under your own store account.
Found in search, and by the models
Titles, metadata, sitemap, structured data and social images are generated with the app. Pages get found instead of only being linked.
React code you can take with you
Real React, edited line by line or by clicking the element on screen, exported as a ZIP or pushed to your GitHub. No lock-in you have to negotiate your way out of.
How it works
From a paragraph to a published app
Three steps, and the second one is the one people do not believe until they watch it.
Start here
A prompt you can paste right now
This is a complete first message, not a slogan. Paste it, change the nouns to yours, and you have an app to react to instead of a blank page.
Build an online course platform. Courses with modules and video lessons, plus PDFs attached per lesson; a learner enrols by buying a single course or subscribing to a monthly plan that unlocks the catalogue; a lesson only opens for someone enrolled; progress is saved per lesson and a certificate is issued when a learner completes a course; every course has a public page with syllabus and price, written to be found by search engines; instructors sign into their own account, publish lessons and see enrolments and revenue for their own courses only; and I see a dashboard with active learners, completion per course and revenue per month.
Ready to start from
Templates in this category
A template is a working app with data already in it. Open one, make it yours, publish it under your own account.
Questions
Frequently asked questions
Describe it. See it running. Publish it to the store.
Free to start, no credit card. You subscribe when you want your own domain without the badge or your app in the stores, and on the Builder plan you take the code with you if you ever want to.