Skip to main content

​
Insight

Backend APIs deployed on custom domains (like mission.so1.io) are often invisible — returning JSON 404s to browser visitors. This is wasted brand surface. A dual-mode landing page turns the backend domain into both a conversion funnel for public visitors and an admin dashboard for authenticated operators.

​
How it works

The page serves identical HTML to all visitors. A hidden admin panel (display:none) attempts to fetch an authenticated metrics endpoint. If the request succeeds (user is authenticated via the console’s proxy), JavaScript reveals the telemetry section showing uptime, request counts, and adapter connectivity. If it fails (public visitor), the admin panel stays hidden and the visitor sees only the branded marketing page with CTAs to the product.

​
Why this matters

  1. Zero-cost brand presence: No separate frontend deployment — the landing page compiles into the API binary
  2. Conversion surface: Every SO1 subdomain now funnels to the product (rover.so1.io) rather than showing a JSON error
  3. Operational visibility: Admins get live system status without needing a separate monitoring tool
  4. Progressive enhancement: The admin panel degrades gracefully — no broken UI for unauthenticated users

​
Applicable to

Any backend service deployed on a branded domain. The pattern requires: (a) the ability to serve HTML from the API framework, (b) an existing auth mechanism for the admin check, (c) brand assets available as code (CSS variables, not image files).