Skip to content

Student portal

A student sees which lesson they are on, hands work in there and gets the next module without anybody opening access by hand.

Who this suits: Online schools where a curator sends out the lesson links, access is opened by hand after a payment, and progress lives in a chat.

What is in the first version

  • lessons by module
  • access from payment
  • assignment review
  • student progress

The figures above are the package this sits on: CRM or client portal. Anything past its edges the calculator adds before the work starts, not after.

How the path goes

  1. 01

    The payment opens what was bought

    The plan, the cohort and the length of access come out of the payment, not a tick in a spreadsheet.

  2. 02

    Hand-in lives under the lesson

    The assignment sits under the lesson and the answer uploads to the same place, so review knows which attempt.

  3. 03

    The next module opens by rule

    By a date, by an accepted assignment or by both, and the rule is written into the course.

What decides whether this works or annoys people

  • A cohort is not a course

    If the cohort is not in the data model from the start, the second run becomes a copy and edits diverge.

  • Review is a queue, not mail

    Work arrives in a wave at the deadline, so the queue is ordered by waiting time from the first version.

  • Refunds, transfers and freezes

    What happens to access on a refund, a transfer and a pause is written into the rules before launch.

What to measure once it is live

  • students reaching the last module
  • time from hand-in to review
  • accesses granted by hand
  • support questions about access

Why this comes out faster

The shape of this one is known: the states, the edge cases and the things that usually go wrong have been decided before. Nothing here is a template, and the saving is not in your half of the work. It goes into your process, your content and the systems this has to talk to, which is the part nobody can have solved in advance.

A likely stack for this

Picked against the task when we scope it, not decided in advance. This is the shelf it usually comes off.

  • Portal and admin panelTypeScriptReactNext.js
  • Server and dataNode.jsPostgreSQLPrismaRedisS3
  • Payments and notificationsStripePaddleTelegram Bot APIDockerGrafana
See the whole stack

Price it yourself, right here

Five steps, and you can see the number without leaving a contact. The estimate accounts for the kind of work, what you already have and what it will need inside.

Step 1 of 5
What needs building?

These bills do not come from us

  • video storage and delivery
  • payment provider fees on tuition
  • mail and SMS to students
  • hosting and servers

Asked before the first call

Why not a ready-made course platform?
If your course fits one, take it, and we will say so. Your own portal earns its place where the platform blocks your rules for opening modules, your review process and your payments.
Where does the video live and can it be protected?
In your storage or with a video service, given out by a temporary link issued to one student, optionally watermarked with their name. Screen recording we do not promise to stop.
Can we change the programme ourselves?
Lessons, materials, module order, assignments and the date rules are edited from the admin panel without us. A new mechanic like points or an auto-marked exam is code and goes through us.
What it starts at
  • Buildfrom $2,850
  • Timeline4–7 weeks
  • Supportfrom $570/mo
Get the price in a minute