Real projects for every student on the roster.

Real project briefs from real companies. Each brief becomes a project a student can pick: they work through milestones, submit a deliverable by the deadline, and earn a certificate signed by someone at the company. A school cohort gives a group of students access to the catalog on a school-billed plan instead of individual purchases.

The brief comes from a real company with a real decision on the line. A student isn't writing for a grade, they're submitting work the company will read. The deadline is real because the company is waiting. The certificate is signed because someone at the company reviewed and approved it.

An email address and a browser. Nothing to install. Each student claims their own account from an invite link you send them.

Schools pay a flat per-student fee covering full catalog access for the cohort's active window. Your agreement names the per-student rate and the window. We bill via Stripe Invoices. If you add students mid-cohort, we invoice separately for the additional seats at the same rate.

Up to 100 students per invite batch, and you can send as many batches as you need. Students can be added after the cohort has started, and late joiners get the same catalog access as everyone else.

Anything a student has submitted stays submitted, and their certificates are theirs permanently. We'll reach out before the window closes to talk through a renewal cohort for the next academic period if you want one.

The seat fee covers cohort access rather than completions, so unused seats aren't refunded. The student keeps catalog access for the rest of the window in case they come back.

No. Students submit directly to the company that wrote the brief. We don't insert a school-review step because it would dilute the real-work, real-deadline frame the platform runs on. You can read a student's reflections and see their uploads on their roster page after they submit.

Every submission runs a preflight check, and all four of these must pass or it's blocked:

1. The final deliverable is uploaded.
2. Every milestone with a required artifact has it.
3. Every reflection meets its minimum length.
4. Every milestone is explicitly marked done.

If a check fails the student sees which one. There's no soft-pass.

Each student's overall progress — not started, in progress, or submitted — and when they last worked. In-progress reflection text and uploads stay private to the student until they submit.

The workspace enters a grace state. The student can either move their credit to a different brief or claim a one-day extension, and they can still submit normally if the work is ready. After 7 days with no action the workspace locks, and the credit can still be moved.

Yes, from the roster page. Each certificate has a permanent public page showing the student's name, the company, and the date, which students share on LinkedIn or a resume. Certificates belong to the student who earned them, so there's no bulk cohort download.

Full name, email, and roster status; which briefs they've started, their progress and submission status, and the certificates they've earned. You see what they're working on, not how they're working on it.

You do not see in-progress reflections or uploads, payment history for briefs they bought personally, or their browsing on the catalog.

In our managed Postgres database and Supabase Storage, encrypted at rest and in transit. Byldora staff with admin access can read student data for support purposes. We don't sell it or share it with third parties.

Yes. A student emails contact@byldora.com and we remove their profile, reflections, and uploads within 30 days. Certificates they've earned stay, since those are public credentials tied to the issuing company.