Verum Auto
Dealership storefront built on verifiable vehicle history
- Status
- BuiltBuilt, awaiting launch
- Period
- 2026–now
- My role
- Sole developer
- Client
- Used car dealership
- Stack
- Next.js · TypeScript · Prisma · PostgreSQL · Docker · GitLab CI
The problem
Used car listings are a market where nobody believes anything. The brand's whole premise — verum, truth — is that every claim on a listing can be backed with a document.
How it was built
Provenance is a data model, not a marketing line
Vehicles carry specifications, images and a timeline of events. A mileage guarantee is a record with a source, not a badge on a photograph.
Accounts live in the database, not in environment variables
Seeded users get one-time passwords printed once during deployment and must change them on first login. Admin credentials in .env are how small sites get taken over.
Postgres is never published to the internet
No mapped database port, the app binds to localhost, TLS terminates at a reverse proxy in front. The example compose file this was adapted from did all three the other way.
Where it landed
- Storefront, admin, financing calculator and viewing reservations
- 36 automated smoke checks covering storefront, i18n, auth, admin CRUD and permissions
Adapted, not copied
The stack came from the Kozmetika build, but every place where the original made a convenient choice for a demo — published ports, default passwords, binding to all interfaces — was deliberately changed. Reuse is only cheap if you reread what you are reusing.