Limits & roadmap: Lyceum
Updated
What this version deliberately cannot do, why not, and what would trigger building it.
Why this page exists
Every piece of software has limits. Discovering them after buying is the most expensive way to learn them. Here they are, beforehand.
No multi-tenancy
Lyceum is built for one operator. A marketplace with third-party sellers, separate payouts per seller and separate data spaces is a different thing and would not be a retrofit but a different product. Several authors under one operator, by contrast, already work today. Those are roles, not tenants.
Course pages are invisible to search engines
The public site is assembled in the browser, not pre-rendered on the server. For buyers arriving via a mailing list, ads or social networks this has no consequence. Anyone who needs organic search results as a sales channel needs an additional building block for it. This is the most important limit of this version. Check it against your sales channel before deciding.
One offer per purchase
No cart. Two courses are two purchases. For an unlimited digital good that is rarely a problem and saves a whole step in checkout.
What is on the list
Subscription · vouchers · reviews · duplicate a course · a time-limited preview link. After that quizzes, assignments with submission and drip release. Those are projects of their own, not switches.
And what is already prepared today
Company licences are not built, but the seam is in place: quantity on the order and a licence reference on the enrolment exist from day one. When the first company enquiry arrives it is work, but not a data migration.