Most course creators do not start out wanting to be platform owners. They start with expertise, a folder full of half-recorded lessons, and a nagging feeling that everything they are building is living on someone else’s land. Then the researching begins: comparison articles, pricing pages, affiliate reviews, and a spreadsheet with eleven browser tabs worth of features. Weeks later the folder is still full of half-recorded lessons.
- Why "Which Platform Should I Use?" Is the Wrong First Question
- System One: Somewhere for the Lessons to Live
- System Two: A Way to Take Money on Your Own Terms
- System Three: Keeping Course Video Out of the Wrong Hands
- System Four: Student Access, Progress, and Support
- What Does Running Your Own Course Site Actually Cost?
- The Technical Pre-Launch Checklist
- Mistakes That Quietly Kill Sales on a Course Site You Own
- Frequently Asked Questions
- The Part That Should Not Be Your Job
The reason that research phase never resolves is not that the options are complicated. It is that the question being asked is the wrong one. “Which platform should I use?” is a question about software. The real question is about infrastructure: what has to exist so that money arrives in your account, lessons arrive only to the people who paid, and neither of those two things depends on a company that has not heard of you.
This guide answers that second question in full. We will walk through the four systems every course business needs, what each one costs to run, how the tax and payment details actually work once you are the seller instead of a marketplace, and how to keep paid video from becoming a free download. If you have been stuck in tab-hopping research mode, this is the map out.

Why “Which Platform Should I Use?” Is the Wrong First Question
Marketplaces make one promise and one threat. The promise is audience: you show up, list your course, and someone else worries about traffic and payments. The threat is that your business is a row in someone else’s database, priced by their algorithm, and reachable only through their search results.
That trade is not automatically bad. What makes it dangerous is that creators usually accept it without knowing what the alternative requires. Once you can name the pieces you would need, the marketplace decision becomes a deliberate business choice instead of a default.
What “Owning Your Course Business” Actually Means
Owning your course business comes down to five things, and none of them require a large audience. You control the student list, so you can email your buyers without asking permission. You control the checkout, so you can set price, currency, bundles, and payment plans. You control the learning experience, so a lesson format change does not require a feature request. You control the data, so you can see who finished what. And you control continuity: no sudden commission change, no wind-down announcement, no forced migration with a deadline.
If you sell on a marketplace and your entire business is a single course, you can replicate all five of those properties on a site that already exists and is already yours. That is the whole project. Everything else is implementation detail.
The Four Systems a Self-Hosted Course Business Needs
Strip away the marketing pages and every working course business is four systems talking to each other:
- Lesson delivery, which is simply where your content lives and how it plays.
- A checkout, which is how a stranger becomes a paying student.
- Access control, which is how paid content stays with paid students.
- Student identity, which is how you know who is on the other side of the screen.
Each of these is a solved problem. The failures happen at the seams, which is why it helps to think about the four of them together rather than shopping for them one at a time.
System One: Somewhere for the Lessons to Live
This is the part creators over-think least and under-plan most. A course is not a page of streaming video. It is a structured sequence with a beginning, a set of dependencies, and a reason for a student to keep going after lesson three.
What Is the Difference Between a Course Page and a Course?
A course page has a title, a cover image, and a payment button. A course has a curriculum: modules, lessons inside modules, an order that means something, and progress a student can see. You can build the first version in an afternoon with a page builder and a Buy button. The moment you have a second course, though, a page-based approach starts costing you, because there is no shared structure to reuse and no consistent way for students to see what they have finished.
This is one of the reasons a purpose-built course layer on top of your existing site tends to be the pragmatic middle path: you keep the site you already own, but your lessons stop being pages and start being a curriculum.
How Many Lessons Before You Need a Real Course Player?
There is no magic number, but there is a pattern. If your content is under about forty minutes and entirely text, pages and a password will do. Between forty minutes and three hours, with even one video per lesson, you want a real player with lesson navigation, resume-where-you-left-off, and a curriculum sidebar. Beyond that, you want progress tracking and completion, because a student who cannot tell how far along they are is statistically a student who will not finish.
You will also want to decide early what “finished” means, because it drives the whole student experience. Completion could mean watched the video, answered the quizzes, submitted an assignment, or simply reached the end of the last lesson. Pick your definition now and design the student’s dashboard around it.
System Two: A Way to Take Money on Your Own Terms
The moment you are the seller, you inherit the parts marketplaces used to absorb: processing, currency, tax, refunds, and the unglamorous machinery of failed payments.
What Do You Need to Accept Course Payments on Your Own Site?
You need three things stacked in order. First, a payment processor account, which is a Stripe, PayPal, or similar business account tied to your own bank details. Second, a checkout on your site that creates the order, collects the money, and records the sale. Third, a fulfilment step that turns a successful payment into access, which is the part small setups most often skip and then fix by hand for six months.
Two practical details matter more than people expect. Your processor needs to know you sell digital course content, because that determines which features you get and how disputes are handled. And your checkout must show the price in the currency your buyers expect, or you will quietly lose the international share of your audience who find a foreign-currency total confusing.
One-Time Payment, Payment Plan, or Subscription?
One-time pricing is the simplest and the best fit for a self-contained course: students own it, and your revenue arrives in a concentrated burst. Payment plans are the workaround for a high-ticket course, spreading the same total across three or six monthly charges. Subscriptions are for access that never ends: a constantly updated library, a community, or ongoing coaching.
The mistake is mixing the models before the course is proven. Selling lifetime access while charging a monthly price, or offering a payment plan at the same total with no commitment, tends to attract buyers who have no intention of finishing. If you already know your number, the mechanics of setting the price matter more than the billing shape.
How Do Taxes, Refunds, and Failed Payments Work?
When a marketplace sells your course, it is usually the merchant of record, which means it handles indirect tax on the transaction. When you sell directly, that responsibility shifts to you. In practice this means understanding whether sales tax applies to digital goods in the jurisdictions you ship into, whether VAT or GST applies to your buyers, and whether you need to collect tax identifiers from business customers who will handle it themselves.
Refunds deserve a written policy before anyone can buy, not after someone asks. A clear window, stated in plain language, converts better than a vague promise, because it removes the specific form of doubt that stops an on-the-fence buyer. Failed payments need a rule as well: how many retry attempts, how much grace, and at what point access pauses. Write the rule once and let the software enforce it, because deciding case by case on a Sunday night does not scale.

System Three: Keeping Course Video Out of the Wrong Hands
Video is the most expensive part of running a course and the easiest part to give away by accident. Getting this system right is mostly about choosing the right place for the files and then being honest about what protection can and cannot do.
Where Should You Host Your Course Videos?
There are four workable options, and each has a distinct failure mode.
- Public video platforms with unlisted links — free, zero maintenance, and effectively unprotected. Anyone with the link can forward it, and your buyers will see someone else’s branding and recommendations beside your lesson.
- A dedicated video host — paid, fast, and built for embedding, with privacy controls that make links harder to share outside your site. This is the most common professional choice for course libraries of any size.
- Self-hosting on your web server — tempting because it feels fully owned, but large video files are exactly what your web host’s bandwidth limits were designed to constrain. This is the route that produces surprise invoices and throttled playback.
- A course layer built for video — your files live on video infrastructure sized for delivery, and access flows from your own student records rather than from a public link.
Cost scales with bandwidth, which is just a way of saying it scales with how many people watch. A rule of thumb at current rates: a self-hosted setup on ordinary web hosting runs tens of dollars a month until an audience arrives, a dedicated video host lands in the low hundreds per year for a typical single-course library, and platform pricing with transparent delivery included is around a hundred to a few hundred per year depending on library size.
What Actually Stops Video Theft?
Nothing stops a determined viewer with screen-recording software. Anyone who promises otherwise is selling a feeling. What you can control is the effort required, and the effort required is what separates a protection strategy from a leak.
Signed, expiring playback links mean a copied URL goes dead within minutes. Domain-locked embeds mean the video refuses to play anywhere except your site. Rendering the player inside an authenticated area of your site keeps discovery out of the picture. Light per-student watermarking turns a leak into a traceable event. Taken together, these turn casual copying from a two-second problem into a project. You can read more about the approach in the note on protecting course content from theft and the practical implementation of protected HD video.
Why Playback Quality Decides Completion Rates
Playback is a completion-rate lever, not a cosmetic detail. A student on conference-room wifi who waits eight seconds for each lesson to buffer simply stops opening the lessons. Adaptive delivery, which switches quality as bandwidth changes, matters more than peak resolution, because a consistent 720p that never stalls beats a 4K stream that hiccups.
Two small choices help more than any encoding setting: keep individual lesson videos short enough to watch in one sitting, and make sure the player behaves on a phone. Most completed lessons happen on mobile, in fragments of time between other things, not on a desktop in a dedicated study block.
System Four: Student Access, Progress, and Support
Access control is where a course business stops being content and starts being software. It is also where creators lose the most time to improvised solutions, usually a shared password and a spreadsheet of who paid.
Accounts, Magic Links, or a Shared Password?
A shared password is fine for a free lead magnet and a liability for anything paid. You cannot revoke it without disrupting everyone, you cannot see who used it, and it gets forwarded. Password logins are the familiar default and work well when students return regularly. Magic link logins, where the site emails a one-time login link, are the smoothest for students who refuse to remember credentials, with the trade-off that they require access to the same email inbox every time.
Whichever you choose, the account must be created by the checkout, not by you. The moment you are manually adding students to a list, you have built a job for yourself rather than a business system.
How Do You Offer Lifetime Access Without Giving Everything Away?
Lifetime access needs to be defined before it is promised. It usually means access for as long as the course exists in its current form, with access to corrections and format updates included, and a clear policy for what happens if the course is ever retired. Students accept that definition readily when it is stated up front, because what unsettles them is ambiguity, not the word lifetime.
One practical habit protects both sides: keep a time-stamped copy of every published version of your course. If anyone ever questions what they bought, the answer is a screenshot rather than an argument.
Where Do Students Ask Questions?
Support has a volume problem, not a difficulty problem. The same twelve questions arrive in the first month of every cohort, and the way you handle them decides whether teaching feels sustainable. A lesson-level comment area catches the specific ones where the confusion happens. A small private community or group chat catches the social ones and gives students a reason to return between lessons. A short FAQ page catches the ones that are really onboarding issues.
Choosing deliberately here matters, because course creators who skip it end up answering the same email eleven times a week. If you want to go deeper on the human side, the guide to creating a great student experience covers the patterns that keep people finishing.
What Does Running Your Own Course Site Actually Cost?
Direct selling is usually cheaper than creators expect at the low end and more expensive than they expect at scale. A realistic annual picture for a single course with a few hundred students looks roughly like this.
- Site hosting — ten to thirty dollars a month for a site that already runs your business, with no additional cost for a course layer.
- Course and video delivery — somewhere between zero and a few hundred dollars a year depending on library size and whether delivery is bundled.
- Payment processing — roughly 2.9% plus a small fixed fee per transaction, with a slightly higher rate on international cards.
- Email — free under a few hundred contacts, then twenty to fifty dollars a month as your list grows.
- Tax and accounting help — the one line item that is invisible until it is expensive. Get a professional opinion before your first international sale.
Set that against marketplace economics, where a typical commission takes a double-digit percentage of every sale plus payment fees, and the arithmetic usually favors direct selling once you are past the first few dozen students. The full breakdown, including production costs, is worth a look if you are planning the whole budget.
The Technical Pre-Launch Checklist
Before you announce a date, confirm each of these ten items. Nine is not enough, because the tenth is usually the one that costs you your launch week.
- Test a real purchase end to end — with a live card, from a phone, using an email address that is not yours.
- Confirm access is granted automatically — the receipt and the login should arrive without you touching anything.
- Check every lesson plays — on mobile data as well as wifi, and after a hard refresh.
- Verify protected playback — copy a lesson URL into a private browser window and make sure it fails.
- Read your own refund and access policy — if anything requires interpretation, rewrite it before it is needed.
- Set up tax handling — or confirm with your processor that it is being handled for you.
- Install analytics and conversion tracking — so launch data is measurable instead of anecdotal.
- Test the password reset and magic link flows — they are the number one support ticket in month one.
- Confirm checkout works in every currency you advertise — including the one you cannot test from home.
- Write the two support answers you will need first — where is my login, and how do I get a refund.
Mistakes That Quietly Kill Sales on a Course Site You Own
- Treating launch as a build milestone — the site can be finished for weeks while the audience hears nothing. Marketing is a schedule, not a step.
- Rewriting the curriculum forever — version fourteen of lesson two is not the reason nobody bought. Ship a v1 and improve it with student feedback.
- Assuming buyers already understand the offer — a sales page that lists features without naming the transformation does not convert.
- Skipping validation — building the whole thing before confirming that anyone will pay for the specific outcome.
- Hiding the price — “contact us for pricing” filters out exactly the decisive buyers you wanted.
- Ignoring the post-purchase sequence — the first thirty minutes after buying decide whether a student starts or shelves the course.
- Building a community with no reason to return — an empty forum is worse than no forum, because it signals the course is abandoned.
The thread connecting nearly all of those is a focus on the artifact instead of the sale. A course website that exists and functions is table stakes; the work that produces revenue is helping a specific person decide that this specific outcome is worth money this week.

Frequently Asked Questions
Can I sell courses without a marketplace at all?
Yes. A marketplace is a distribution channel, not a requirement. You need a checkout that can take a card, a place for lessons to live, and a way to keep paid content behind a login. All three can run on a site you already own, and the trade-off is straightforward: you give up marketplace browse traffic in exchange for keeping your margin, your customer list, and your pricing.
Do I need to be a developer to run a self-hosted course site?
No, provided you choose tools that assume you are not one. The developer-shaped work is behind the scenes: payment processing, video delivery, access control. What you should expect to do yourself is content, pricing decisions, and support. If a setup requires you to touch server configuration to publish a lesson, it is the wrong setup for a course creator.
How do I stop students from sharing their login?
You discourage rather than prevent. Concurrent-session limits, per-student watermarks, and expiring playback links all raise the effort of sharing, and most people simply will not bother. Keep the framing proportionate: the overwhelming majority of buyers are honest, and treating them like suspects costs you more goodwill than a rare shared account costs you in revenue.
What should I do first if I already sell on a marketplace?
Start with the list, not the site. Export your buyers, set up your own email so you can reach them without platform rules in the way, and tell them what you are building. Then set up the checkout and move one course across, keeping the marketplace listing live until your own sales numbers justify the switch.
How long does it take to set up a course site properly?
If your content already exists, the technical setup is measured in days rather than weeks, but the sequence matters more than the speed: choose the four systems, wire the checkout to access, test a real purchase, then announce. Most of the elapsed time in a course launch is spent on positioning, sales page, and audience, not on infrastructure.
The Part That Should Not Be Your Job
Every one of those four systems is a solved problem, and none of them is the reason you started teaching. If you are working on a site you already own, Owwlish adds the course layer that turns it into a course business without a migration: lessons and curriculum, checkout with payment plans and tax-aware pricing, protected video that will not stream outside your student area, and a dashboard that shows who is actually finishing what. Keep the site, keep the audience, and spend your launch week on the parts only you can write.



