← /work

teuka

state: production

A multi-tenant SaaS for scientific conferences: abstract submission, double-blind peer review, registrations, payments and certificates. I built it and run it solo, from the database schema to the deploy pipeline.

started
first commit in August 2025; in production today
stack
PHP 8.5 · Laravel 13 · Filament 5 · Livewire 4 · Octane on FrankenPHP · PostgreSQL
tests
~290 Pest test files, feature and unit, plus architecture rules
team
built and run solo; sales by a partner

A modular monolith. Each business area is a module with its own models, migrations, policies and tests: abstracts, evaluations, conferences, registrations, payments, certificates, users and organizations. Four Filament panels sit on top, one per kind of user: platform admin, organization admin, conference participants and reviewers.

  • Payment gateways plug in behind one interface, so adding a gateway does not touch registrations. A local online-payment gateway runs in production.
  • Certificates are rendered to PDF on request and sent as signed links, so no generated file is stored.
  • Pest architecture rules keep the boundaries honest, for example "payment partners never reach the presentation layer" and "no Eloquent model lives outside a Models namespace".

Hand-rolled, without a tenancy package: one PostgreSQL database where every tenant-owned row carries its organization, and every isolation rule lives in application code covered by tests.

  • The organization is resolved from an exact match on the request host. The match is deliberately not normalized: a looser match could hand one organization's pages to another.
  • Eloquent global scopes filter every query by organization, and role scopes narrow it further: participants see their own submissions, reviewers only the abstracts assigned to them.
  • Policies check the organization again, and panels answer 404 when no organization resolves.

Reviewers never see who wrote an abstract, and authors never see who reviewed it. Only the organizing committee sees both. This is enforced by policies and by what each panel renders, not by convention.

  • ~290 Pest test files: feature tests through the panels and HTTP layer, unit tests for the domain.
  • Guards for the failures that hurt in production: migration rollbacks, route caching and N+1 queries.
  • Every pull request runs the suite in parallel against PostgreSQL, plus Pint for code style.
  • Larastan (level 5) runs locally before changes go up.

I work with AI coding agents every day. The test suite and the architecture rules are what make that fast without making it reckless.

  • Every merge to main builds a Docker image on FrankenPHP, pushes it to the GitHub container registry and deploys it through Coolify.
  • Supervisor runs Octane, the queue worker and the scheduler inside the container.
  • Sentry reports errors and Laravel Pulse tracks performance in production.