Compliance-aware UX
The fee transparency framework explicitly separates government charges from service fees, which is a trust and compliance requirement, not just a content choice.
Overview
This project is a multilingual SaaS platform designed to guide travelers through government authorization applications such as ESTA, eTA, and ETA. The core product challenge is not only form completion. It is trust, compliance, and policy change handling in a workflow where users are often stressed, unfamiliar with rules, and vulnerable to misinformation.
The application is built as a Turborepo monorepo with discrete packages for UI components, validators, content, email templates, and policy monitoring. That structure keeps contracts shared across the product instead of duplicating logic across application layers.
Guided wizard flows support individual, family, and group use cases, while Clerk manages authentication, Stripe handles payments, and PostgreSQL with Prisma keeps the transactional layer structured and auditable. The result is a complete SaaS stack rather than a narrow single-page form.
The most differentiated component is the monitoring package. It scrapes relevant government pages on a schedule and uses LLM-based semantic analysis to detect policy changes before users are affected, turning compliance monitoring into an active product capability.
Product Architecture
apps/web (Next.js 14 App Router) | | multilingual wizard flows, account UI, checkout, content rendering v packages/ui packages/validators packages/content packages/emails packages/monitor | | shared contracts, copy, templates, and policy-monitoring logic v PostgreSQL + Prisma | | application state, user records, transaction workflows v Clerk + Stripe | | authentication, payments, subscription / checkout flows v Monitoring jobs | | scheduled government-site scraping + OpenAI / Anthropic semantic analysis +--> policy alerts and content updates
Business-Relevant Capabilities
LLM-powered policy monitoring
Scheduled scraping plus semantic analysis catches changes in government requirements earlier than manual review cycles, reducing the risk of stale guidance.
Shared contracts across the monorepo
Zod validator packages enforce consistent data contracts across the UI, business logic, content layer, and email workflows.
Accessibility and test discipline
End-to-end coverage with Playwright and a11y validation with axe-core turn quality into a release requirement instead of a best-effort aspiration.