Dear instructor,

We built OpenLuxe Courses because the usual answer to that question is five subscriptions. A course platform holds the videos. A community app holds the students. A processor holds the money. An email tool sends the reminders. Something else, eventually, tells you where people quit. Each of those is reasonable on its own; together they are a second job you did not apply for. Everything described below is one product, inside the account you already have.

Let me start with the part most pages put last. OpenLuxe takes 20% of every paid enrolment. You keep the other 80%, and it arrives as payout credits at the moment the enrolment settles rather than on a monthly cycle. Nothing is charged to build a course, to publish it, or to keep it listed. There is no per-student fee. If you teach under a school on the platform the split changes: the school takes 25%, and the remaining 55% goes to the instructor pool, divided between instructors by how many lessons each of them actually contributed.

One more number, because it looks like it should cost you something and does not. Anyone on the platform can assemble a curated collection of courses and earn 10% when a visitor enrols through it. That commission is funded by OpenLuxe, not deducted from your side of the split. Somebody promoting your course does not make your course worth less to you.

The thing instructors ask about first is the AI, and the honest answer is narrower than the pitch you are used to hearing. Multiple choice is scored deterministically and instantly. For open answers, you write the answer you would have written yourself, and that becomes the rubric. The AI grades each response against your rubric and returns three things: a score out of 100, written feedback naming what was right and what was missing, and a pass or fail against the threshold you set. It does not decide the standard. You do.

Assignments are where the teaching actually happens, so they are deliberately not text boxes. You write the prompt, then choose which submission types you will accept: written responses, one of your own journal entries, photos, video, voice recordings, PDFs, or an external link to a repository, a Figma file, a Loom. All of it renders inline on your review panel, so you watch the video, hear the audio and read the PDF without leaving the course. You leave feedback, give a grade out of 100, and choose one of three: approve, needs revision, reject. Mark it needs revision and the student can rework it and send it back with your old feedback cleared. Approve it and the submission locks, for both of you, permanently.

Any of that can be a gate, and you decide how hard the gate is. Submit-to-unlock suits a reflection prompt. Approval-required suits a capstone you want to sign off on personally. A passing-grade threshold suits the cases where the number is the point. Compose those with day-based drip releases, prerequisite locks and test gates and a course stops being a folder of videos and becomes a sequence. Courses are typed as well, because a compliance course and a coaching course are not the same promise: informal, coaching, certification, license, continuing education, compliance, or official. Pacing is self-paced or scheduled, and a scheduled course runs as a cohort with its own states (open, waitlist only, closed), an optional application form, and a deadline.

What surprised us in building this is how much of the work sits after the sale. So: every lesson carries its own threaded discussion, your replies wear an instructor badge, and you can pin one to the top, which means you answer a hard question once and every future student who reaches that lesson finds the answer waiting. Separately from that, each course gets a structured Q&A hub with upvotes, an accepted answer and a resolved flag, for the questions that outlive a single cohort. Students can also send you private feedback tagged positive, neutral or negative, visible only to you and your active instructors. And you can write an exit review of a student, four sections and an overall impression, held private until you choose to share it with them.

Completion issues a PDF certificate automatically. The student's name, the course title, your name and the final score are snapshotted at the instant of issue, so renaming your course next year does not quietly rewrite last year's graduates. Each certificate gets a public verification page anybody can open without an account, and it is themed to match the course. Reviews come only from people who finished, one per completion, and you can reply to any of them in public. You also control when graduates are invited to review, anywhere from a day after completion to a year. That setting is time-locked to one change per year, so nobody can slide the window around to bury a bad month.

Last thing, and it is the one that decides whether any of the above matters: you do not have to go and find a new audience. A course can be attached to a post or a public journal entry you have already published, and a call-to-action card appears inside it carrying the price and a one-click enrol. Ownership is checked on the server, so nobody can attach your course to their writing.