Attendance System
About

Built for the people at the front of the room.

Every faculty member we've spoken to has had the same argument with a student about a signature on a paper. That's why this exists. It shouldn't be harder than it needs to be.

Why we started

A four-minute cost you pay every class.

The first version was a Google Form. The lecturer would paste a link on a slide, students would type their name, the responses would land in a spreadsheet, and that was that. It worked. It was also easily gamed — anyone could type any name — and it took ten minutes to build a fresh form for each lecture.

The second version added a QR code and a student-ID confirmation step. The third added timestamps and time-window enforcement. The fourth added a proper roster and a per-device cookie. By the fifth version we had rebuilt half of what an attendance module in an LMS does, but without the twelve extra menus and the vendor onboarding session.

What you're looking at is version six. It runs on Cloudflare and Supabase, exports to CSV/Excel/PDF, and — most importantly — you can start using it in your next lecture without asking anyone's permission.

What we believe

Four principles that shape every decision.

01

Faculty own their data

Rosters, attendance, quiz results — yours, exportable, deletable. We never sell it. We never train an AI on it.

02

Zero IT bureaucracy

You should not have to file a ticket to run your own class. Every workflow adopts without institutional approval.

03

Compatibility, not conquest

LMSes are here to stay. We work alongside them, not against them — with CSV, PDF, JSON, and a bit of humility.

04

Small teams, big impact

Built by academics for academics. Every design choice is measured against "will a busy lecturer actually use this on a Tuesday morning?"

Under the hood

Boring, well-understood technology.

We use small, well-known building blocks so the platform stays fast, cheap to run, and easy to reason about. No exotic stacks, no vendor moonshots.

Runtime
Cloudflare Workers · EU edge
Database
Supabase Postgres · EU region
Email
Resend (transactional)
Payments
Stripe (EUR)
Auth
Cookie sessions · PBKDF2 hashing
Frontend
Astro SSR · React islands

Try it in your next lecture.

Invite-only during private beta. Request access using your university email.