ESP32-S3 Bench Guide
ESP32‑S3 N16R8 벤치 가이드: 실시간 핀아웃, 강의, 시뮬레이터 및 벤치 로그
한 링크로 예약·결제, 실시간 번역 자막·AI 요약 제공, 수수료 0%, 30일 무료 프로
One link your students book and pay through, a video classroom with live translated subtitles, and AI notes after every class. 0% commission. Start with 30 days of Pro free, no card needed.
교육TypeScript · JavaScriptGitHub @jaystewartuk온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
A production Next.js and Postgres platform for independent teachers: Stripe Connect payments, self-hosted LiveKit video, live translated captions and an LLM pipeline that turns each class into learning notes. Built and run by one person.
README 전체를 불러오는 중입니다.
README 전문 보기 ↗A scheduling, payments and video platform for independent teachers of any subject. It runs in production at spiralclass.com on live payment rails, with a teacher and her students using it, and this repository is the whole of it.
A teacher signs up, sets her availability, publishes a booking page, and sells packages of classes. Her students buy a package, book slots against it, join the lesson in the browser, and get homework and materials afterwards. She gets paid — either by card through her own Stripe account, or by Wise transfer against instructions the platform generates and reconciles. Nobody installs anything.
The real teacher dashboard, captured locally from the
/demo fixture. The public page draws the
production component from invented data rather than opening a demo account
(D-142). No real person, class or figure
appears in it.
| If you want to… | Read |
|---|---|
| understand how it is built | Architecture overview |
| understand why it is built that way | Two decisions, told in full — one page, then the log |
| run it on your machine | Development setup — or pnpm setup && pnpm dev |
| understand the database | Data model |
| see what it does, feature by feature | Feature documentation |
| find any other document | The documentation map |
| know what is exposed by publishing it | Security posture |
[!NOTE] How this repository was built. SpiralClass was built by one person working with AI coding agents; most of the code was agent-written under review. The public history starts from a sanitised working-tree snapshot (why); every change since lands here as a pull request.
It is published as an honest record of how one engineer builds and runs a
payments-handling, video-carrying SaaS product alone: the architecture, the
decisions, the things that went wrong, and the mechanisms built so they would
not go wrong twice. The engineering decisions in
docs/decisions/ are the most useful thing here —
several of them reverse an earlier one and say why.
No code was simplified, staged or rewritten for presentation. What you are reading is what serves production. The decision log is curated, and says so: records were removed before publication, numbers were never reused, and the index says which groups went and why.
This is a live system, and it is also small: a solo-built product with a customer base measured in individuals, not thousands. There is no team, no on-call rotation, and no uptime SLA. The engineering is sized for correctness and for one person being able to hold it in their head — not for scale it does not have.
여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗