Home

reportmate-app-web

The ReportMate dashboard: a Next.js 15 App Router application that renders fleet inventory, managed-install state, events, and per-device detail for endpoints reporting into ReportMate.

The dashboard holds no fleet data of its own. Every page is served by a server-side route handler in app/api/** that proxies reportmate-api over HTTP, adding an internal shared-secret header on the upstream hop. The browser never talks to the API directly, and the API base URL is never exposed to the client.

Where it sits

agents  ->  reportmate-api  ->  PostgreSQL
                  ^
                  |  X-Internal-Secret
                  |
          reportmate-app-web  <-  browser (session cookie)

Sign-in is NextAuth with a JWT session. A middleware.ts matcher covers every path that is not a static asset or a health endpoint, so an unauthenticated browser request is redirected to sign-in and an unauthenticated fetch gets a JSON 401.

Other ReportMate repos

Repo	What it is	Wiki
reportmate-api	FastAPI ingest and query backend	Wiki
reportmate-client-win	Windows agent (C# / .NET), managedreportsrunner	Wiki
reportmate-client-mac	macOS agent	Wiki
reportmate-cli	reportmateutil, the cross-platform admin CLI	Wiki
reportmate-mcp	MCP server exposing the fleet to AI agents	Wiki
terraform-azurerm-reportmate	Azure deployment module	Wiki
terraform-aws-reportmate	AWS deployment module	Wiki
selfhosted-docker-reportmate	Docker Compose stack and Packer appliance	Wiki
reportmate-website	Marketing site, reportmate.app	Wiki

Contents

• Getting Started — clone, configure, run against an existing API.
• Architecture — the BFF proxy pattern, directory layout, data flow.
• Routes and Pages — every page and every server route.
• Configuration — every environment variable the code reads.
• Authentication — the providers actually wired up, roles, kiosk sessions.
• Theming and UI — Tailwind, dark mode, PWA, URL-as-state.
• Deployment — Docker image, standalone output, published image.
• Development — build, lint, unit tests, end-to-end tests.
• Troubleshooting — failure modes with the error text and the cause.