Client overview - Xem

The Xem client is the web app in the client/ folder of the monorepo. It talks to the Go API in server/ and provides every screen in Xem: campaigns, newsletters, templates, automations, audience and CRM, the inbox, analytics, the Ask Xem assistant and workspace settings.

Stack

Part	Choice
Framework	Next.js 16 with the App Router and Turbopack
UI	React 19, Tailwind CSS, shadcn/ui components
Data fetching	TanStack Query
Sign-in	NextAuth.js v5
Tests	Jest with ts-jest and Testing Library
Package manager	Bun (`bun.lockb`)

Folders

client/
├── app/          # Routes: campaigns, newsletters, audience, automations, inbox, analytics, settings…
├── components/   # Feature components and shared UI
├── lib/          # API helpers, validation and domain logic
├── __tests__/    # Jest tests
├── auth.ts       # NextAuth configuration
└── middleware.ts # Route protection and public pages

Public pages that need no sign-in, such as hosted forms at /f/… and the newsletter web archive at /n/…, are allowed through in middleware.ts.

How it reaches the API

Browser requests go to NEXT_PUBLIC_API_URL. On a self-hosted install this is /api/v1, which your reverse proxy forwards to the backend. Server-side code uses INTERNAL_API_URL to reach the backend directly. See Client setup for the variables.