Digital voting SaaS
Votein
Online voting for organisations: sessions with candidates, optional voter checks (email code, WhatsApp code or ID-number format), one vote per voter, live results with a region map, and add-ons paid per session.

The problem
Official votes need to be limited to eligible voters, count each person once and show results that people can trust.
What it does
- Organisations with members and invitations; voting events with candidates and photos.
- Voter checks per event: none, an email code, a WhatsApp code, or an ID-number format check.
- One vote per voter, enforced by an atomic claim inside a database transaction.
- Add-ons and wallet top-up paid per session through Midtrans.
- Live results with charts and a map of where votes came from.
How it is built
- Next.js 16 with React 19; Prisma 7 on PostgreSQL; Better Auth organisations; Tailwind 4 and shadcn.
- S3-compatible storage for photos, Resend for email, PM2 with a scheduled route.
- An internal audit document lists 39 findings, three of them critical and fixed.
Honest notes
- The ID-number option checks format, province and birth-date structure only. It does not query a government registry.
- No automated tests yet.
Engineering depth
Counts taken from the repository itself, not performance claims.
- 16
- data models
- ~26
- API route files
- ~22
- pages
- 39
- findings in the internal audit