Launch student platforms on one identity layer

Build a learning platform or a student information system on one SDK. Students and staff sign in through your institution's SSO, after which the same access policy applies to the gradebook, messages, tuition, and AI tutoring.

One identity, from SSO to gradebook

A student platform has to recognize the same student in the gradebook, the advising dashboard, a parent's view, tuition billing, and the AI tutor, with the same privacy rules at each of those points. Conjoin Auth signs the student in once through the institution's SSO, after which every other Conjoin service checks each request against that identity and its access policy.

A semester on Conjoin, from enrollment to tuition

Conjoin uses a different service for sign-in, student records, messages, and tuition, although every one of those services checks the same access policy for students, faculty, and administrators.

Sign students, faculty, and administrators in through institutional SSO

Students, faculty, and administrators sign in through Conjoin Auth over SAML or OIDC against the institution's existing directory, so each person uses the account that the institution already issues them. Auth assigns separate roles to students, teaching assistants, faculty, and registrar staff, so a student can open their own transcript while a professor opens the rosters of their own courses. A parent or guardian views one student's records through a short-lived token that Auth issues for that student alone.
Outcome

The learning system, the records system, and the messaging service all check one identity in Auth.

Keep every submission and every grade change

Conjoin Database records grades, enrollments, and course content, with a history of each grade change and the account that makes it. Students upload assignments, essays, and media to Conjoin Storage, which stores a new version of a submission each time the student resubmits it. A teacher opens each submission through a signed URL, while a student can open only their own.
Outcome

When a new teacher takes over a course, they can open every earlier version of each submission.

Reach a struggling student before the midterm

Conjoin Messaging sends assignment reminders, grade notices, and schedule changes on the channel that each student sets in their profile, and logs each message against the student record. Your platform publishes engagement events to Conjoin Relay, which pushes them to the advisors' at-risk dashboard as they happen. Inside the course, Conjoin AI tutors students from the course material and assists with grading, retrieving only the content that the student's account can open.
Outcome

An advisor can contact a student in the same week that the student stops logging in, well before the midterm.

Bill tuition by the institution's own rules

Conjoin Billing bills tuition, course fees, and subscriptions, including installment plans, which divide a semester's tuition into payments on the dates that you choose. To those bills, code on Conjoin Runtime applies your institution's own policies, such as scholarships, add-and-drop refunds, and tuition tiers by residency.
Outcome

The bursar's office sees each refund in Billing next to the Runtime rule that sets its amount.

One identity for every service, and the evidence for AI tutoring

The tutoring figure comes from a randomized controlled trial, published in 2025, that compared an AI tutor with in-class active learning among 194 students in an introductory physics course at Harvard.

One identity layer

for a university and a training provider alike

One platform

for sign-in, records, tutoring, and tuition

Over 2×

median learning gains with an AI tutor, compared with in-class active learning

One access policy across every student service

The rule that lets a student open their transcript at sign-in is the same rule that Storage, Database, and AI check later in the session.

Institutional SSO

Institutional SSO

Send the institution's IT administrator a link to the self-serve SSO portal in Auth, where the administrator uploads the SAML metadata of the directory and turns SSO on.

Student-privacy access controls

Storage, Database, and AI check the same roles in Auth, so Database returns a student only their own records and returns a teaching assistant only the courses that they assist with.

Versioned submissions

Because Storage assigns each version of a file its own ID, a teacher can compare two drafts of an essay or restore an earlier one.

At-risk dashboards in real time

Relay broadcasts each login, submission, and missed deadline to the advisors' dashboard in under 50ms.

AI tutoring with a spending limit

Conjoin AI answers each student's question from the course material that you index in Storage. You can also set a spending limit on each student account, so Conjoin rejects further tutoring requests once that account's spending reaches the limit.

Refunds with reason codes

Billing issues full or partial refunds with a reason code, which lets your finance staff list every refund for a dropped course.

Student platforms for a university and a training provider

Both builds use Auth for every permission check, although only the university connects Auth to its own directory.

Full-stack LMS for a public university

Students, faculty, and staff sign in through Conjoin Auth with SAML against the university's directory. During the term, Conjoin Database records every change to a grade or an enrollment. Students turn in essays and lab videos through Conjoin Storage, which versions every file. Conjoin Messaging sends reminders and grade notices on each student's chosen channel. Advisors watch an at-risk dashboard that Conjoin Relay updates with every login and submission. Conjoin AI tutors students and drafts grades for faculty to review, under the same access rules as the rest of the platform. When tuition is due, Conjoin Billing charges each installment after code on Conjoin Runtime applies the university's scholarship rules.
What this delivers

The gradebook, the advising dashboard, the tutor, and tuition billing all use one identity and one audit trail.

Continuing-education platform with certificates and cohorts

Learners sign in through Conjoin Auth with a social login or with their employer's SSO, depending on the cohort. Course content, lesson plans, and cohort rosters are in Conjoin Database, while video lectures and exercise files are in Conjoin Storage, which serves each one through a link that expires when the enrollment ends. Learners pay per cohort or by subscription through Conjoin Billing, which also invoices the employers that sponsor a group. Conjoin Messaging sends cohort reminders, exam-window notices, and certificate notices. When a learner gets stuck, Conjoin AI tutors them one to one through the course material and reports the mistakes that recur across the cohort to the instructor. Conjoin Relay sends each learner's progress to the instructor dashboard. Once a learner meets the eligibility rules, code on Conjoin Runtime issues a signed certificate.
What this delivers

One platform takes the learner's payment, records their progress, and issues the certificate, so an employer can verify that certificate against the learner's record.

Build your next app on Conjoin

Conjoin will open with a free Build tier, while the pricing page already lists the launch prices for Pro and Business. If you tell us what you're building, we'll talk you through early access.