Orbits Umbrella
← Products
Launching soonFounding tutors and schools

Book a tutor. Take a course. Enrol a whole class. One platform.

Live 1:1 and group tutoring, self-paced courses with quizzes and certificates, and bulk cohort enrolment for schools, built on one account system, one calendar and one payment engine. Every tutor is identity-verified before they appear. Every session payment is held until the session is done.

EduSphere is built and has been checked by hand. It is not deployed yet, so nobody can sign up today.

4
ways to learn: 1:1 live, group live, self-paced, school cohort
6
account types on one shared data model
2
supply channels: independent tutors and in-house staff, same backbone

What EduSphere is

At a glance.

EduSphere puts four ways of teaching on one platform. A tutor runs live 1:1 sessions and publishes recorded courses from the same profile, the same calendar and the same payout account. A parent books sessions for two children and buys a course for one of them from a single login. A school imports its students, groups them into a cohort, assigns them courses, and pays one consolidated invoice.

None of those are separate products bolted together. They share one account system, one scheduling engine, one payment engine and one content library, and a tutor approved once can do both live sessions and courses without verifying twice.

Status
Built and verified. Not yet deployed
Supply
Independent marketplace tutors and platform-employed teachers, on one Provider entity with different commercial rules
Buyers
Parents with child profiles, adult learners, and institutions
Verification
Government ID, certificates and CV reviewed by an administrator before a tutor appears in search
Payments
Escrow on live sessions, released on completion. Commission read from live platform settings at payout
Video
LiveKit for live sessions

1:1 live tutoring

A learner books a slot from a tutor's calendar. Payment is held in escrow and released when the session completes.

Group live sessions

A tutor opens a session with minimum and maximum seats. Each seat is charged. If the minimum is not reached by the cutoff, the session cancels and everyone is refunded in full.

Recorded courses

Sections and lessons with video, downloadable materials and quizzes. Progress and last-watched position are tracked. A certificate is issued on completion.

School cohorts

An institution imports learners by CSV, groups them into cohorts, assigns courses, and receives one consolidated invoice.

Why this exists

The problem.

Tutoring, online courses and school programmes are the same transaction wearing three different coats. The software treats them as three industries, and everyone pays for the gap.

A tutor runs two businesses. Live sessions on one marketplace, recorded courses on another, with two profiles, two calendars, two payout accounts and two sets of fees. The students who would buy the course are the ones already sitting in the sessions, and nothing connects them.

A parent manages three logins. One platform for the maths tutor, another for the coding course, a spreadsheet for who has what. Nobody can answer the one question that matters, is this child actually progressing, because no single system sees both halves.

A school cannot buy at its own scale. Enrolling a class of thirty on a consumer platform means thirty individual purchases, thirty logins created by hand, thirty receipts, and no cohort view. Most schools give up and go back to a spreadsheet and a WhatsApp group.

Money moves on trust. On a consumer platform the learner pays and hopes. On an informal arrangement the tutor teaches and hopes. Neither side has a mechanism that holds the money until the work is done, so both sides price in the risk.

Each gap is survivable alone. Together they are the reason a tutor with real demand stays a sole trader, a parent keeps a spreadsheet, and a school keeps paying for substitute teachers instead of buying what it needs.

The alternatives

Why one platform.

Everything below already exists and works for the case it was built for. None of them covers more than one.

OptionWhat it does wellWhere it stops
A tutoring marketplaceMatching a learner to a live tutor, with reviews and a calendarNo course authoring, no progress tracking, no certificates. A tutor's recorded material has nowhere to live, and a school cannot enrol a cohort.
A course platformHosting, selling and tracking self-paced video at scaleNo live scheduling, no per-session escrow, no tutor calendar. A learner who needs a person to explain it has to leave.
A school LMSCohorts, assignments and grades inside one institutionClosed to the outside. A school cannot reach a specialist tutor through it, and nothing in it is a marketplace.
All three, integratedEach tool at its bestThree subscriptions, three identity systems, three sets of permissions, and reconciliation work forever. The learner exists three times and no system knows it is the same person.

The argument for one platform is not that it does each job better than a specialist. It is that a tutor, a parent and a school are all dealing with the same learner, and splitting that learner across three systems is what creates the work.

What EduSphere gives up.

A dedicated marketplace will always have more tutors on day one, and a dedicated course platform will always have deeper authoring tools. We are betting that one verified identity, one calendar and one payment engine across all three is worth more than depth in any one of them. For a tutor who only ever records courses, or a school with an LMS it is happy with, it is the wrong bet and we would say so.

How it is built

Architecture.

Four decisions carry the platform. The first one is the whole product.

One Provider, two supply channels

An independent marketplace tutor and a platform-employed teacher are the same entity in the database, distinguished by one attribute. They share the profile, the calendar, the content library, the booking flow and the delivery system. What differs is commercial: commission rate, payout cadence and approval route.

The same entity carries capability flags for live tutoring and course creation. A tutor approved for live sessions can apply to publish courses without repeating identity verification, because verification belongs to the person, not to the capability.

The alternative is two parallel systems that drift apart for years. Retrofitting this attribute later is not a schema change. It is a migration across every booking and every payout record ever written.

One Buyer, with dependants beneath it

A parent and an adult learner are the same Buyer entity. A parent manages dependent learner profiles; an adult learner is their own. A child is never a standalone account, always a profile under a paying party, which is what makes parental oversight structural rather than a setting.

An institution sits above the same structure, owning dependent learners the way a parent does. Its students get their own login credentials, generated at import, that open a restricted view of their own enrolments and nothing else.

Money held until the work is done

Live session payments go into escrow and are released when the session completes, with commission read from live platform settings at the moment of payout rather than from a constant in the code. Group sessions escrow per seat and release as a pool. Recorded course purchases are held until the refund window closes.

Refunds are credited to an in-app wallet by default, withdrawable to the original payment method above a threshold. Every wallet movement is itemised.

Access control enforced where the action happens

A parent, an institution admin or a student can only reach their own records, enforced at the endpoint rather than by what the interface chooses to show. Several checks are structurally scoped: there is no parameter in which to even name another learner's record.

This is a lesson rather than a preference. A restriction built only in the interface was found to be fully bypassable by a direct API call. A disabled button is a courtesy, never a boundary.

Built and verified

What is built.

Six areas. Everything listed has been exercised by hand against real records: real bookings, real payments, real cross-account access attempts. Nothing here is on the page because a specification called for it.

Getting a tutor onto the platform

  • Identity verification. Government ID front and back, certificates and a CV, each uploaded as its own document with its own status. Uploading does not submit. Submission is explicit and is blocked until all four required documents are present.
  • Administrator review. Approve, reject with a reason, or send back for correction. A sent-back provider re-uploads only the flagged document rather than starting again.
  • CV extraction with a human gate. Bio, education, certifications and years of experience are extracted from the CV by rules rather than a language model, and land in staging fields. The provider reviews them side by side against their existing live profile and chooses field by field what to keep. Nothing overwrites a real profile silently.
  • Intro video with moderation. 90 seconds, 50 MB, enforced on the server by inspecting the file rather than trusting the browser. Pending and rejected videos are reachable only by their owner or an administrator, through short-lived signed links. Approved videos preview on hover in search.

Being found

  • Search ranks tutors and courses by a Bayesian-weighted score that pulls thin records toward the platform average, so a single five-star review does not outrank a tutor with forty. The badge appears only above three reviews.
  • Filters cover subject, language, skill level, rating and, for tutors, an availability window matched by real interval overlap rather than exact times. The homepage shows the top eight tutors and courses; the full discovery page paginates, and pagination respects the active filters.
  • Subject chips on the homepage are generated from what is actually on the platform, refreshed every ten minutes, rather than a hardcoded list that goes stale.

Booking and getting paid

  • Access gated on approval. Until approved, a provider reaches only their own verification tab. Cancelling a booking stays available at every status, deliberately: a lapsed provider must always be able to release a learner's money.
  • 1:1 and group sessions. Group sessions carry minimum and maximum seats. Below the minimum at the cutoff, the session cancels and every learner is refunded in full.
  • Per-seat pricing. A parent booking two children into one group session pays for two seats. Verified against real booking and payment records, not by reading the code.
  • Escrow and payout. Payment is held on booking. Completion releases it, deducts commission at the live platform rate, and credits the provider's earnings balance, each booking in its own atomic transaction.
  • Cancellation tiers. 48 hours or more, 24 to 48 hours, and under 24 hours, each with its own consequence for whichever side cancels. Provider cancellation always refunds the learner in full.
  • Wallet. Refunds go to an in-app wallet, itemised, withdrawable to the original payment method.
  • Disputes. A real status on the booking, synchronised with a dispute record. An administrator resolving in the learner's favour cancels and refunds; rejecting leaves the dispute on the record.
  • Bookings view. Four tabs with real counts (upcoming, past, cancelled, disputed), date filters, and a live countdown on the next session. Providers see unbooked availability and actual bookings side by side.

Learning

  • Courses are built as sections and lessons, each with video, downloadable materials and an optional quiz. The player tracks completion, overall progress and last-watched position, so a learner resumes where they stopped. Quizzes run as practice or graded, and graded results gate course completion.
  • Live sessions run on LiveKit, with two-way audio and video confirmed in a real two-participant call.

Keeping learners coming back

  • Badges across ten achievement types, streaks counting any day with a login, a lesson watched or a quiz attempted, and sound on quiz interactions with a working mute. All three are deliberately absent from every institutional cohort view, because ranking and comparing children in front of a school is a decision nobody has taken.

Schools and institutions

  • Bulk import. Learners imported by CSV into profiles owned by the institution rather than a parent.
  • Student logins. Each imported student gets generated credentials and signs in to a restricted view of their own enrolments. This exists because a teacher cannot click into a course for every student every morning.
  • Cohorts. Learners grouped into cohorts for assignment and reporting.
  • Course assignment. A licensed course assigned to a whole cohort at once instead of a separate purchase for each student.
  • Consolidated invoicing. One invoice covering course licences across the institution. Verified end to end on a real invoice: paid, escrow released on every underlying payment, and provider earnings credited to the exact expected amount.

Before and after launch

What comes next.

What stands between this and a live platform, then what comes after.

Before launch

  • Deployment. The platform and its live-video service go into production. Until then EduSphere is not available to the public.
  • Search by keyword across tutor names, course titles and topics, and subject drill-down from a category into its branches. Both are absent today; filters cover the rest.

After launch

  • Subscriptions as an alternative to one-off course purchases
  • Course discussion threads and public community spaces
  • Native mobile applications. The platform is responsive web today
  • Co-teaching with revenue splits
  • Analytics for providers, and cohort-level analytics for institutions

Decisions nobody has taken yet

These are on the page as decisions rather than features, because each one is a policy question before it is a build.

DecisionWhy it is open
Refund window for recorded coursesTime-based, percentage watched, or both. Needs legal input per market, and it sets what creators can count on.
LeaderboardsRanking learners against each other breaks the rule that a buyer sees only their own data. Anonymised, opt-in, cohort-only or not at all is a deliberate choice, not a feature flag.
Institutions bringing their own teachersAn institution cannot yet onboard and manage its own staff under its own umbrella. That is a data-model change rather than a screen.

What “built” means here

How we verify.

A platform that holds other people's money has to be checked differently from one that does not. Nothing here is marked done because the code looked right.

The standard: a feature touching money is verified by making a real payment and checking the balances before and after by hand. A feature touching access is verified by attempting the access as the wrong person, and specifically as the wrong person of the same role, since proving a tutor cannot see a parent's data proves very little about whether one parent can see another's.

Access control on all of it was verified the hard way: one student against another student, one parent against another parent, one institution against another.

What this changed

  • A restriction built in the interface alone is not a restriction. One was found fully bypassable by a direct API call, and every rule of that shape is now enforced at the endpoint.
  • A number having a plausible value is not the same as it being right. A placeholder four-figure course price and an off-by-one in lesson numbering both survived every automated check and were caught by a person looking at the screen.

Before we open

Founding partners.

We are taking a small number of tutors and one or two institutions onto the platform before it opens publicly. Three blocks, one for each reader.

Tutors and course creators

You get

No commission for an agreed founding period. Verification handled directly with us rather than in a queue. Your subjects, curricula and rate structures shape the taxonomy everyone else inherits. Both capabilities, live and recorded, from one approval.

You should know

The platform is not open to learners yet. A founding tutor is betting on learners arriving, and we are not going to pretend otherwise. There are no notification emails yet, so bookings and messages have to be checked in the dashboard. You can take your learner list and your course content with you if you leave.

Parents and adult learners

You get

Early access to the founding tutors, who are the ones we have verified personally. Your payment is held until the session actually happens, from the first booking.

You should know

A small tutor list at the start. No mobile app: the site works in a phone browser. No reminder emails yet, so an appointment is something you note yourself.

Schools and training centres

You get

Your cohorts imported and set up with us rather than by you. Consolidated invoicing on your own payment terms. Direct influence on cohort reporting, which is the part most worth shaping before it is fixed.

You should know

Multi-seat group-session pricing is being corrected before any institution is billed for one. You cannot bring your own teaching staff onto the platform under your own umbrella yet. Cohort analytics are basic. No provider background-check programme exists, which matters if your learners are minors and your policy requires one.

Next step

Three readers, three routes.

Tutor

Teach live, publish courses, or both, from one profile

Learner or parent

Be among the first to book

School

Put a cohort on the platform before we open

Same working day reply, Monday to Friday. If EduSphere is not right for you yet, we will say so in that reply.