Internal MVP foundation

AI Meeting Organizer gives platform teams one operator-first surface for access, tenant setup, and service health.

The product is still in its walking-skeleton stage, but it now reads like a deliberate control plane: shared route shells, bootstrap-driven authentication, tenant-aware health, and a typed frontend/backend contract are already in place.
Open dashboard shell
Open auth shell
Tenant-aware auth and route guards
Operator health across platform and customer scopes
Shared shell and visual system
Product snapshot

Stronger hierarchy, same truthful scope.

This entry surface is meant to orient platform staff quickly: what is already working, what the shared stack proves, and where to go next.
App name
AI Meeting Organizer
API base URL
https://kaiku-qa-backend.jollymoss-a52196d9.swedencentral.azurecontainerapps.io
Auth mode
MSAL redirect flow
Current focus
Operator shell, onboarding, and health visibility
What is live today
  • Platform visibility
    System, operator, and tenant-aware integration checks already flow through the shared admin workspace.
  • Bootstrap-driven access
    The frontend resolves runtime tenant settings from the backend bootstrap contract instead of hard-coding auth paths.
  • Unified product framing
    The app shell, auth shell, and landing surface now share one visual system instead of separate placeholder treatments.
  • Typed API baseline
    Frontend data access stays grounded in the committed OpenAPI contract and generated client types.
  • Runnable local stack
    Local compose services keep the API, worker, SQL Server, Redis, and frontend available as one runnable MVP environment.
Honest MVP status
The app now has a credible product frame, but it is not pretending to be feature-complete. The goal is to make the current state legible while the deeper meeting workflows and integrations keep arriving in later slices.
  • Graph, SharePoint, and Visma workflows still expand through later feature slices.
  • Meeting lifecycle CRUD and operator automation remain intentionally narrow at this stage.
  • This page should set expectations honestly: the product frame is real, but the business surface is still growing.