Skip to content
Kevin Arian

Exhibit A

APTP management platform

A motorsport association moved its whole operation — accounting, member registration, race management, and tax-authority invoicing — from manual work to one system.

Status
In production since 2025
Scope
1 API · 3 client applications
Invoicing
Filed automatically with ARCA
Role
Sole engineer, end to end

TypeScript · Express · Prisma · PostgreSQL · Redis · React · AWS Cognito · Cloudflare

The problem

The Asociación Pilotos Turismo Pista runs racing championships in Argentina: pilots to register, races to organize, fees to collect, and electronic invoices to file with ARCA, the national tax authority. All of it was manual — administrative work that grew with every season and depended entirely on the people doing it by hand.

What I built

One platform that runs the operation:

  • A single API (Express + TypeScript, Prisma over PostgreSQL, Redis caching, Zod validation at every boundary) as the source of truth for accounting, members, and races.
  • Three applications on that API — an admin panel for the association, a portal for pilots, and an app for providers — built in React and sharing types and validation schemas with the backend, so the contract between them can’t silently drift.
  • Automated electronic invoicing: integration with Argentina’s fiscal system (via TusFacturas/ARCA), so invoices that were typed one by one are now generated and filed by the system.
  • Production infrastructure: AWS Cognito authentication, S3/Cloudflare R2 file storage, automated deploys (Coolify for the backend, Cloudflare Pages for the frontends).

The outcome

The association operates on the platform today. Billing that consumed administrative hours runs automatically; registration and race data live in one place instead of scattered spreadsheets. Built and shipped end to end by one engineer — architecture, backend, three frontends, and deployment.