Skip to content
Independent system — Schematic S-02

AutoInspectPro.

A solo-built, multi-tenant SaaS for vehicle inspection workflows. Below is the drawing — the moving parts, and how a single request routes through the stack from field device to database.

Decommissioned 2026 · Code retained Solo-built Multi-tenant Next.js · NestJS · Postgres
↳ Request path — top to bottom

The system, layer by layer.

01Client

Browser

Inspectors and admins work from any device — capturing inspections in the field and managing them from the office.

HTTPS
02Web App

Next.js 15

Server-rendered UI (App Router) for auth, inspection forms, and dashboards. Fast first paint, clean routing, and a single front-end for every tenant.

ReactApp RouterTailwind v4TanStack Query
REST API
03API

NestJS 11CORE

The core. Every request is scoped to a tenant before anything else, then runs the inspection logic. A BullMQ worker renders PDF reports with Puppeteer + Chromium off the request path.

Tenant-aware auth (JWT · RBAC)Business logicBullMQ · PDF generation
Prisma 6 ORM
04Data

PostgreSQL

Each tenant's inspection records stay isolated by Postgres Row-Level Security. A typed Prisma schema with migrations keeps the data layer predictable and safe to evolve.

Row-Level SecurityTyped schemaMigrations
General note — Ran on
Fly.io deployCloudflare R2SupabaseUpstashGitHub Actions CI/CDWeekly backupsNew Relic
Notes 01–03 — Design principles
N-01

Multi-tenant by design

Every customer's data is isolated, and tenant context runs through each request — not bolted on afterwards.

N-02

Inspections → PDF

Structured inspection records compile into clean, shareable PDF reports on a background worker, straight from the API.

N-03

Built to run

Deployed with CI/CD, automated backups, and observability, so it behaved like a product, not a demo — through to an orderly 2026 sunset.