checking
Web surface
Landing shell, router and public assets are reachable from this deployment.
Checking current origin...
Runtime boundaries, without guesswork.
This page checks the public web surface and states what is intentionally protected, local-only or session-gated. It is built for deployment review, not marketing.
Current score
4/ 7 expected
Expected 404s and auth gates count as healthy when they match the architecture.
checking
Billie Studio
The visual preview surface is a public route and should be available without login.
Checking /billie-studio...
checking
Protected app
Anonymous users should be redirected to login before app data is loaded.
Checking /app redirect...
expected
Supabase client
Auth, wallet and chat data use the configured Supabase project.
Public project host: btkcbwozwvknpggsmxhh.supabase.co
expected
Chat Edge Function
The web chat calls the Supabase Edge Function after a valid user session exists.
Anonymous probes are skipped because the function requires a user session.
expected
FastAPI local engine
The local FastAPI runtime is intentionally not exposed from the public web domain.
Public /api/health is expected to stay unavailable on the web deployment.
healthy
Public boundary
No service role token or database password is exposed by this status page.
Only public route outcomes and hostnames are displayed.
Need deeper proof?
Run the local verification suite before deploy: typecheck, lint, web smoke, API contracts, build and visual QA.