Your GitHub repo is
already a course
Write lessons in Markdown. Ship quizzes in YAML. Deploy with git push. Start free, self-host if you want, and only turn on paid access when it actually fits your workflow.
Paste owner/repo, a full GitHub URL, or even a /tree/main/docs/course link — we'll normalize it for you.
Useful for monorepos, docs folders, or a course stored in a subdirectory.
Proof first · No credit card · Free forever · MIT licensed · Optional paid access
Choose the lowest-risk proof path.
With zero signups and zero revenue, the homepage should help skeptical creators test TeachRepo without feeling trapped in a signup flow.
See a real public repo turn into a course outline before you create an account.
Grab course.yml, lesson frontmatter, quiz YAML, and a launch checklist in one click.
See exactly when the $19 plan starts making sense before you think about paying.
Free to self-host · MIT licensed · No lock-in · hello@teachrepo.com
Get the starter kit in your inbox
We’ll send the course.yml example, lesson frontmatter, quiz YAML, and the fastest proof path so you can test TeachRepo without committing to a signup first.
Low signups usually mean the first move is still too fuzzy.
So this is the honest split: repo-first, notes-first, or self-host-first. Choose the path that already matches how your material actually exists today.
Bring one repo and judge the workflow quickly.
Best if your lessons already live on GitHub and you want the fastest proof path into a real import.
Start from a folder, not a polished repo.
Use the notes-first starter kit if your material lives in workshop notes, docs drafts, or a local Markdown folder.
Keep MIT + self-host real from day one.
For skeptical operators who only want hosted later if it clearly saves time and earns the monthly cost.
The fastest way to lose technical creators is to make them guess.
These are the promises TeachRepo puts in front of skeptical repo-first users before asking them to sign up or pay.
You can generate a repo outline before signup. TeachRepo does not push to your GitHub repo during preview.
MIT-licensed core, transparent file format, and a clear self-host path if you do not want platform lock-in.
If calls or recordings are annoying, you can stay async over email and still get help or share feedback.
Concierge onboarding is available for the first repo so creators do not get stuck reverse-engineering the format.
Show the flow before asking for trust.
The sharpest feedback so far was predictable: engineers want a believable proof path, not just pricing and feature claims. So this beta now makes the sample flow, the starter kit, and the self-host route visible before signup.
Generate an outline from a public repo before you sign up. No repo writes, no GitHub mutation, no lock-in.
Copy a known-good course.yml, lesson frontmatter block, quiz YAML, and deploy checklist in one place.
Self-host stays real. Hosted has to earn its keep by shortening setup and helping you ship faster.
For engineers, the alternative is usually glue code.
Zero signups and zero revenue usually mean one thing: the value is still fuzzy. TeachRepo only deserves to exist if it beats the obvious alternatives for repo-first creators who want proof, not lock-in.
TeachRepo
- •Markdown + YAML stay source-of-truth
- •Payments, previews, and versioned updates in one stack
- •Self-hostable if managed hosting is not worth it
Docs stack
- •Great for docs, but payments and gated lessons are bolt-ons
- •You still have to stitch together auth, checkout, and access control
- •Best when free documentation is the whole product
DIY stack
- •Maximum control, but you own every integration and edge case
- •Useful if you actively want to build course infrastructure yourself
- •Most creators only want this if hosted tools break trust or flexibility
Use hosted only if it saves more time than the DIY or docs-only path.
| Question | TeachRepo | Docs stack | DIY stack |
|---|---|---|---|
| Git-native authoring | Yes — repo stays canonical | Usually yes | Yes |
| Built-in paid access | Yes — optional | No | Not by default |
| Versioned course updates | Yes | Docs only | Only if you wire it yourself |
| Self-host path | Yes — MIT core | Yes | Yes |
| Why pay hosted? | To skip setup + ops | No hosted course layer | You pay in time instead |
Don't guess your way through the first import
The biggest drop-off right now is signup → first import. So we made the lowest-risk path, the starter template, and human help explicit.
Import an existing repo
Already have a workshop, docs repo, or lab materials? Paste the GitHub URL and preview the course structure before you sign up.
Open the starter kit
Need a known-good format first? Copy the exact course.yml, lesson frontmatter, quiz YAML, and launch checklist in one place.
Get a setup walkthrough
If you want a human sanity check, we will review your repo, point out frontmatter issues, and help you ship the first lesson.
Zero signups usually means the audience still has to squint.
Discovery feedback kept repeating the same pattern: TeachRepo works best for technical creators who already publish from repos and want a low-risk path to course structure, previews, and optional payments.
- ✓You already teach from GitHub, Markdown docs, workshop repos, or lab materials.
- ✓You want one free preview lesson before asking anyone to pay.
- ✓You want self-hosting to stay possible, but would pay later if managed launch speed is obviously better.
- —You only want a marketing site or docs site and already have that solved.
- —You never plan to teach, package lessons, or charge for access.
- —You reject any paid layer on principle, even when it saves real setup work.
“Turning GitHub repos into courses feels genuinely useful, especially for developers.”
“a single strongest proof, e.g., starter repo would be the most convincing way to prove the 15-minute setup promise.”
“Honest answer is no, I wouldn't have any use for it.”
Pick the path that matches your workflow
Most repo-first creators do not want the same thing. Answer three quick questions and we’ll point you to the lowest-friction next move.
Use concierge beta before deciding
You want proof and a human sanity check before choosing self-hosted or paid.
- •Bring one repo or docs folder and we’ll help you judge fit quickly.
- •Best when you are curious but still skeptical about the first import.
- •Good fallback if calls are annoying — async email works too.
Self-host stays available either way. Hosted only wins if it saves enough time to matter.
What real repo-first users pushed back on
We cleared the 10-reply outreach gate before touching the product. These were the sharpest objections, so they now shape the product copy and onboarding path.
"A single strongest proof, e.g., starter repo, would be the most convincing way to prove the 15-minute setup promise."
"No ... Free self hosting ... make an onboarding video."
"Not interested in putting anything behind a pay-walled product."
The sample import path and template are now front-and-center so people can test the workflow before committing to a signup.
We now say the quiet part out loud: many engineers want MIT + self-host first, and hosted only if it genuinely saves time.
TeachRepo now leads with course publishing and proof. Monetization stays available, but it is no longer the first thing maintainers see.
Don't buy first. Import a sample repo, clone the template, or book a walkthrough. If the workflow feels real, then decide whether self-host or hosted is worth it.
From repo to course in 15 minutes
Structure your repo
Add course.yml + a lessons/ folder to any GitHub repo. Copy from our template to skip setup.
Paste the GitHub URL
Drop the URL into the import form. We fetch lessons, parse YAML, and import everything automatically.
Set your price
price_cents: 0 for free, or any amount for paid. Stripe handles checkout, receipts, and refunds.
Publish and share
Hit Publish. Your course is live with a shareable link, SEO metadata, and a buy button.
Everything a technical creator needs
Markdown-first
Write lessons in plain Markdown. Frontmatter sets order, paywall, and quiz links — no CMS needed.
Zero-config paywall
Set price_cents in course.yml. Stripe Checkout handles the rest — access is enforced server-side.
AI quiz generation
One click to generate MCQs from your lesson content. Edit, reorder, then save directly to the course.
Git-native versioning
Every import creates a version snapshot. Roll back or publish a new version with a single push.
Creator analytics
See your full funnel: signups → imports → published → checkouts. Know exactly where you lose people.
Self-hostable, 0% fee
MIT-licensed core. Deploy on your own Vercel + Supabase in 10 minutes. Keep 100% of revenue.
Hosted Creator needs a better reason than convenience theater.
Revenue is still zero, so the paid offer has to become more legible. The honest pitch: hosted is for creators who want the repo-native workflow without babysitting the surrounding infrastructure.
Use Hosted Creator when publishing speed matters more than infra ownership.
Stay self-hosted if the MIT core already covers your workflow and you do not need managed checkout + analytics.
Use concierge if you are still deciding and want a human sanity check before you pay.
Not everyone should buy the hosted plan
Our outreach kept saying the same thing: self-host has to stay real, and hosted only wins if it clearly saves time. So here's the honest version.
- •You want full control, MIT licensing, and no platform dependency.
- •You are comfortable with Vercel + Supabase or already have infra.
- •You care more about publishing than managed convenience.
- •You would pay to skip setup, ops, and maintenance work.
- •You want analytics, hosted checkout, and a faster path to launch.
- •You only upgrade if the time savings feel obvious.
- •You are curious but not convinced the workflow will fit your repo.
- •You want a human to sanity-check course.yml, lessons, and pricing.
- •You would rather talk before you decide whether to self-host or pay.
The questions that usually block signup.
The fastest way to lose a skeptical engineer is to dodge the hard questions. These are the ones that kept coming up in discovery, so we answer them directly.
Do I have to buy anything before I know this works?
No. The intended path is proof first: preview a sample repo, inspect the starter kit, and only create an account when the workflow feels believable.
What if I only want the self-hosted path?
That is a legitimate outcome. TeachRepo keeps the MIT + self-host route visible because many technical creators prefer control first and hosted only if it clearly saves time.
What if my content lives in a docs folder or monorepo?
That is why the preview accepts a path inside the repo. You can point TeachRepo at a subdirectory instead of reshaping the whole codebase upfront.
Who should not pay for Hosted Creator?
If you enjoy maintaining the stack yourself, only publish free docs, or do not need managed auth, checkout, and analytics, stay self-hosted and keep your $29.
What is the fastest credible first run?
Use the sample repo or starter kit, publish one free preview lesson, then share the live URL with a few people before touching marketplace or affiliate features.
If you are still unsure, do the smallest credible thing: preview a repo, inspect the starter kit, or book a walkthrough. The product should earn the signup.
Try free lessons right now
These courses show the TeachRepo format — Markdown files, YAML quizzes, Stripe paywall. No signup needed for free lessons.
Git for Engineers sample import
Preview a public GitHub repo turning into a course outline before you create an account or touch billing.
Starter kit + course.yml walkthrough
Copy a known-good course.yml, lesson frontmatter block, quiz YAML, and launch checklist instead of reverse-engineering the format.
Self-host vs hosted decision guide
Use the honest $19 break-even math, self-host path, and founder-fit guide before deciding whether the managed plan is worth it.
Until creator inventory grows, we're showing the strongest proof paths users asked for instead of a blank marketplace.
Tell us if this should exist
We're talking to engineers and repo owners about one thing: can a repo-to-course flow feel fast, trustworthy, and worth paying for?
“Would you actually try a repo-to-course flow on a real codebase or docs folder?”
“Is onboarding under 15 minutes believable, or do you need a starter repo and concierge help first?”
“Would you pay for a hosted version, or is self-hosted-only the right answer for this category?”
Free to Use. Free to Fork.
The TeachRepo core is MIT-licensed and self-hostable. Deploy to your own Vercel, keep 100% of revenue.
Course Template
Official course template — Markdown lessons, YAML config, GitHub Actions CI/CD. Clone and ship.
TeachRepo CLI
Import repos, validate YAML, scaffold courses from the terminal. Works in CI/CD pipelines.
Platform Source
The full TeachRepo platform. Next.js 15, Supabase, Stripe, 500+ Playwright tests. Self-host it.
We'll help you get the first repo live
Right now, getting a real creator through signup → import matters more than pushing referral mechanics. If you have a repo, workshop, or docs folder, we'll help you import it, fix frontmatter issues, and publish the first lesson.
Ship your course this week.
If you can write Markdown, you can build a course.
Free to start — no credit card, no lock-in.