Architecting Our Own Infrastructure
A studio that sells sub-second storefronts has to run on one. If our own site shipped page-builder bloat and a stack of third-party scripts, the performance budgets we set for client builds would carry no weight.
The site you are reading runs on the stack we ship to clients: Next.js 16 App Router and Supabase Postgres with row-level security, deployed on Vercel, styled with Tailwind CSS 4 and animated with GSAP and Lenis on transform and opacity only.
Pages are statically rendered or server-rendered from our own components with no commercial theme, OpenTelemetry log export is wired through instrumentation.ts, and product analytics run through PostHog.
- Next.js 16
- Supabase PostgreSQL RLS
- Tailwind CSS
- GSAP + Lenis
- Vercel
- OpenTelemetry
Owner-recorded benchmark for panarchdigital.com, 9 July 2026: 100/100 mobile PageSpeed (Lighthouse lab run), and at the 75th percentile of real-user data a 0.47s Largest Contentful Paint, an 87ms Time to First Byte and 0.00 CLS. Sources and method are published on our performance baseline page.
- Mobile PageSpeed (Lab, 9 Jul 2026)
- 100/100
- P75 LCP (Field, 9 Jul 2026)
- 0.47s
- P75 TTFB (Field, 9 Jul 2026)
- 87ms
See where your storefront loses its first second.
A 30-minute consult with Arpan Tyagi, founder and principal engineer, on where your current stack spends its load time and what we would change first.
Client platforms shipped for Fabriclicious, Mithila Enterprises and Kiran Singh Foundation.