Beta programme
The RootWright beta, explained in full.
Everything about the private beta in one place: what testers get, what we ask, how we pick people and what happens after. If something here isn’t clear, that’s our first bug.
Seats50
Length21 days
Your time2 hrs/wk
You pay$0
The beta deal
Your offerFounding price
Founding price, locked
Every Pro feature, free, for the whole beta.
When the beta ends, [40%] off any plan. That price never goes up while you keep renewing.
Prefer to pay once? The lifetime licence at the same founding discount.
Early access to every RootWright plugin that follows.
The small print
Founding price open to accepted testers until [date]. The renewal lock holds while the licence stays active.
What we ask
- Days 1–3Install the ZIP and answer a two-minute setup check-in.
- Week 1Build one course you would really teach.
- Day 10Midpoint check-in. Five questions.
- Weeks 2–3Enrol at least three students (test accounts count), try the Pro features, report what breaks.
- Day 21Final feedback form, plus an optional 20-minute call.
Plan on about [two hours a week]. If life gets in the way, tell us and we’ll pass your seat to the next person.
After the beta
- The beta build updates to the release like any plugin update.
- Courses are WordPress posts and student data sits in your database, so nothing moves. [Confirm update path from the ZIP to the WordPress.org release.]
Who it’s for
Who we’re looking for.
Fifty people can’t cover everything, so we’re aiming for a spread: different course types, different site sizes, and people coming from different LMS plugins.
Most seatsCourse creatorsSome seatsAgencies and freelancersSome seatsSchools and training teamsSome seatsMoving from another LMS
Most seats
Course creators
You sell, or want to sell, courses on your own WordPress site.
You’d testThe builder, checkout and the student app.
Some seats
Agencies and freelancers
You build learning sites for clients and live with the support tickets.
You’d testSetup, roles, the REST API and theme independence.
Some seats
Schools and training teams
You train staff or students and care about who finished what.
You’d testDrip, checkpoints, quizzes and spaced recall.
Some seats
Moving from another LMS
You run LearnDash, Tutor LMS, LifterLMS or similar and want out.
You’d testImporters [as they ship] and performance with real data.
The test plan
What you’ll actually test, week by week.
The schedule mirrors how a course comes together: build it, open it to students, then run it. You choose the course; we suggest what to try along the way.
0 of 9 triedTick what you’ve tried
BuildWeek 1
Install and set upUpload the ZIP, add your Pro key, answer the setup check-in.
Build one real courseModules, lessons, one reusable lesson used twice.
Add checkpoints and a quizTry at least three question types.
OpenWeek 2
Enrol three or more studentsTest accounts count. Real people count more.
Set a drip scheduleOpen one module seven days after enrolment.
Take a payment in test modeStripe test mode or the PayPal sandbox, with sales tax switched on.
RunWeek 3
Live with spaced recallUse the Today view yourself for a few days.
Protect one videoBunny.net or Cloudflare Stream, watermark on.
Send the final formAbout fifteen minutes. The optional call is twenty.
Testers so far
Round 1 hasn’t started yet.
Once it does, this space shows who’s testing (course creators, agencies, schools) and what they say, with their permission and their names. [Fill after week 1.]
{n} of {total} tried
Selection
How we pick testers. No lottery, no algorithm.
Rafi or Reza reads every application. We look for a mix, not the fastest typists, and we reply to everyone, yes or no.
- A mix of course types. Video-heavy, text-heavy, cohort-style and self-paced.
- A mix of starting points. New sites, and sites moving from another LMS.
- A clear answer to “what will you teach?” One honest sentence beats a long pitch.
- A reply either way within [2 working days]. If you’re not in round 1, you’re first in line for round 2.
Rules
The rules, in plain English.
- Perks never depend on reviewsWordPress.org guideline 9 forbids it, and so do we.
- Talk about it freelyNo NDA. Post screenshots, write about it, complain loudly.
- Security bugs come to us firstReport them privately so we can fix them before anyone else finds them.
- Your data stays on your server[No telemetry by default. Confirm.]
- You can leave any timeTell us and we pass the seat on. You keep the founding price.
Questions
Every question we’ve been asked so far.
Not here? Write to [[email protected]] and we’ll add it.
Search the questions
Search 14 questions
14 questions
Is RootWright LMS free?
Yes. The free plugin is heading to WordPress.org and includes the course builder, the student app, dedicated tables, lessons with quizzes and checkpoints, spaced recall, the skill map, course reviews, SMTP support and the REST API. Pro adds drip, exams, study plans, AI course building, native checkout with sales tax and EU VAT, and video hosting with a viewer watermark.
Can I use the beta on a live site?
You can, but we’d suggest a staging site or a fresh site for your first course. It’s beta software, so back up first and don’t move your only paying course on day one.
What happens to my courses when the beta ends?
They stay. Courses and lessons are ordinary WordPress posts, and student data lives in your own database. The beta updates to the release version like any other plugin update. [Confirm update path.]
Do I have to leave a review?
No. Your perks depend on feedback you send to us, never on public ratings. Reviews on WordPress.org are entirely your choice.
What happens to my Pro key if I don’t finish?
Your Pro key keeps working until [launch + 30 days]. After that, any plan is yours at the founding price, [40%] off for as long as you renew.
Can I move my courses from another LMS?
Importers are in progress. [List what ships in the beta.] Tell us what you use today on the form, and we’ll prioritise accordingly.
How do I report a bug?
[Decide: email to [email protected], a form, or GitHub issues.] Screenshots and the steps you took help most.
Will testing cost me anything?
RootWright costs nothing during the beta. Some Pro features use outside services: Bunny.net or Cloudflare Stream for video, and Stripe or PayPal for payments. Their test modes and sandboxes are free.
Can I test on a client’s site?
Yes, if your client agrees and knows it’s beta software. [Confirm: does a lifetime licence earned on a client’s site belong to you or the client?]
Who sees what I put in the form?
The RootWright team, plus the email and CRM services we use to run the beta, which are listed in the privacy policy. We never sell it. Marketing emails only if you tick that box, and every email has an unsubscribe link.
What does it need to run?
WordPress [6.x] and PHP [8.x] or newer, with a current MySQL or MariaDB. Email goes through wp_mail(), so the SMTP plugin you already use keeps working. Video streams from Bunny.net, Cloudflare Stream or YouTube.
Is the 50-seat limit real?
Yes. About fifty is the most we can support while reading every report and replying properly. When round 1 is full, the form turns into a waitlist for round 2.
What if I’m not picked?
You go on the waitlist for round 2, and you can use the free plugin as soon as it’s on WordPress.org. We delete declined applications after [6 months] unless you ask us to keep you on the list.
Does the plugin send any data to you?
[Confirm: no telemetry by default. Any usage data is opt-in, as WordPress.org rules require.] Your courses and student data stay in your own database.
{n} question matches
{n} questions match
No question matches that. Write to us and we’ll add it.
{n} questions
Apply for round 1
Want a seat? Tell us what you teach.
Four quick fields. takes two minutes