SimLabDisplay

Bring SimLabDisplay to your school

Simulation lab management built for dental education: live rotations, station capacity, sign-offs, and the records your program needs. Start with a pilot that needs no roster and no integration, and we'll face your IT review with you when you're ready.

See exactly what every student is doing

The board shows who's where, what's signed off, and whose hand is up, live on every device. One tap assigns the whole class and starts the day.

Spot who's falling behind, during the lab

Not in next week's grading. Rotations are proposed for you to confirm, TAs cover seat zones, and the students who are stuck surface while there's still time to act.

A record you can defend

Every sign-off is stamped with who gave it and kept. End-of-day reports show who finished what, and your program office can see it across all faculty.

Already partnered? Log in. Questions about security or data handling? Email support@simlabdisplay.com.

Request a demo

A few details and we'll take it from there.

We only use this to get back to you. See our privacy policy.

How schools adopt it

The risk disappears before the data arrives

01Pilot

Run a lab before sharing a roster

Demo accounts hold no email address and no password, only a seat number and a PIN in a dental lab or a name and a PIN in an undergraduate one. Your professor runs real lab days with the real product while your school imports nothing and connects nothing.

02Review

Put your IT team in front of us

We'll walk them through exactly how it's built, complete your security questionnaire, and sign your data agreement (your counsel's template, not ours).

03Roll out

Full access, your rules

Students sign up under your registered email domains. No institutional email, no account. When your identity team is ready, SAML single sign-on is a configuration step, not a rewrite.

For your IT team

The walkthrough, in writing

This is the summary. In the walkthrough we'll go as deep as your team wants, down to the individual access rules.

Access rules live in the database

Who sees what is enforced inside the database itself, not in app code. A student can only ever read their own records. A bug in the interface can't leak the wrong row.

Revoked means now

Close an account and the database refuses it on the very next request, even mid-session, even on a phone that's already signed in.

Minimal data, fully exportable

Names, school emails, class records, photos of practice work: that's the inventory. All of it exports to open formats at any time. There is no lock-in to us.

Single sign-on ready

SAML 2.0 is built in. Your identity provider vouches for students, they inherit your MFA, and deprovisioning follows your directory. Enabling it is configuration, not a project.

Records outlive accounts

Students can delete their accounts any time. Their identity goes, but faculty-signed coursework stays, nameless, as the institution's record. The line FERPA draws, drawn in the code.

Nothing watches your students

No ads, no analytics, no AI, no location. The app never even requests the permission. Encrypted in transit and at rest on SOC 2 Type II certified infrastructure.

If something ever goes wrong

If we discover a breach, the credentials that matter are revoked in minutes. That ends the exposure. Your designated contact hears from us within 24 hours with what we know, and within 72 hours you have it in writing: scope, cause, and fix. If your policy requires a different window, tell us the number and we'll hold to it in writing.