Certe.ID

Context

Indonesian universities needed a way to administer English proficiency tests (TOEFL-equivalent, locally validated) without coordinating with a central testing body. Certe.ID is the platform that lets each university run its own sessions, schedule its own test takers, and get results back the same day.

What I built

A Laravel + MySQL application with three main surfaces:

• University admin — manage students, schedule test sessions, configure scoring rubrics, see results.
• Test taker — register, take the test, see provisional scores.
• Results processor — scoring logic, report generation, export to the formats universities needed.

The non-obvious parts were test integrity (browser lockdown, time-bounded sections, single-attempt enforcement) and the scoring model (each university calibrated its own passing thresholds, so the schema had to support per-institution rubrics without forking the codebase).

Outcome

Universities went from running tests quarterly with manual scoring to running them weekly with automated results. The platform handled a few thousand concurrent test takers during peak registration windows without us having to redesign anything — the queue worker and the connection pooling did their jobs.

What I'd do differently: I'd push back harder on the original "every university gets its own subdomain" requirement. We did it with a wildcard cert and route-based tenant resolution, but the operational cost of per-tenant debugging was higher than I expected. A single-tenant-per-database model would have isolated failures better.