Selected work.

Key decisions

• → Monorepo from day one: Four separate apps sharing Supabase schemas and TypeScript types. One PR updates shared logic across all surfaces.
• → Supabase as the entire backend: No Express server. Supabase handles auth (PKCE for iOS), database, real-time subscriptions for chat, Edge Functions for business logic, and RLS as the authorization layer.
• → Stripe web-only (no 30% Apple cut): Payments flow through the web app. Mobile deep-links to web checkout. Fully compliant — gyms keep 30% more revenue.
• → LLM translation in chat: Real-time Thai ↔ English translation using LLMs with sub-second latency. Trainers and students communicate without a shared language.

Key decisions

• → Monorepo with shared types: Web (Next.js 14), admin dashboard, and mobile share a single TypeScript codebase. Schema changes propagate everywhere.
• → Vipps over Stripe: Norway's dominant mobile payment method. The integration is complex but the conversion rate difference is significant.
• → Async scoring with Supabase real-time: Participants complete quizzes at different times. Real-time leaderboard updates use Supabase subscriptions.

Key decisions

• → Headless Shopify + Storefront API: Shopify GraphQL API for product data. Next.js 15 for the frontend. ISR with revalidate:60 keeps product data fresh.
• → No-checkout pattern: B2B customers request quotes, not instant checkout. Airtable handles the CRM side.
• → AWS Amplify for hosting: Amplify handles CI/CD from GitHub, environment variables, and custom domain.

Key decisions

• → RAG pipeline with pgvector: WooCommerce product data ingested into Supabase pgvector. Semantic search retrieves relevant products before the LLM generates responses.
• → OpenRouter for model flexibility: Route between Claude, GPT-4o, and Groq depending on query complexity. Fast models for simple questions, reasoning models for comparisons.
• → Cloudflare Workers for edge processing: Query preprocessing and caching at the edge. Sub-200ms response times for cached product lookups.

Key decisions

• → n8n queue mode on Docker: Production n8n deployment with separate main and worker containers. PostgreSQL for persistence, Redis for queue management. Auto-restarts via systemd.
• → AI-powered document processing: Claude processes incoming briefs, extracts requirements, and creates structured Notion pages. Saves 2+ hours per client onboarding.
• → Telegram bot for ops: Real-time alerts for deployments, errors, and client messages. Quick-reply actions for common operations.

Key decisions

• → Multi-tenant from the core: Single codebase serves multiple compliance clients with isolated data, configurable KYC flows, and tenant-specific branding. Row-level isolation at the database layer.
• → AI-powered AML screening: Custom AI agents screen against 1.7M+ sanctions records in real-time. Lead scoring and risk assessment automated — what used to take hours now takes seconds.
• → Blockchain for verifiable KYC: XRPL NFTs as proof-of-KYC that users own and can present to any participating institution. Polygon for RWA tokenization. Not crypto for crypto's sake — solving real compliance portability.
• → 12+ repo architecture: Monorepo wasn't practical at this scale. Separate repos for API, admin portal, client portal, KYC widget, AI agents, deploy CLI, and shared packages. Custom Deploy CLI orchestrates Cloudflare Pages deployments.

Key decisions

• → Offline-first with dirty tracking: Every local mutation gets a dirty flag and timestamp. When connectivity returns, the sync engine resolves conflicts using last-write-wins with manual review for price conflicts. Pharmacies can't afford downtime.
• → Tauri over Electron: 50MB installer vs 200MB+. Native OS integration for thermal printers and barcode scanners. Rust backend for SQLite operations — fast and memory-efficient on pharmacy hardware.
• → Dual product modes: Pharma mode enforces batch tracking, expiry dates, and regulatory fields. Non-pharma mode is streamlined for general retail. Same app, different workflows based on product category.
• → .NET 9 ProductService microservice: Separate microservice handling product catalog sync across branches. PostgreSQL, EF Core, Redis caching, RabbitMQ for event-driven updates between branches.

Key decisions

• → Sanity CMS for non-technical editors: Visual editing, real-time preview, and structured content types the marketing team manages independently.
• → Performance-first architecture: Static generation for portfolio pages, ISR for blog content. Sub-second page loads.