Web application
The Next.js application is reachable and serving local health checks.
Source: /api/health
A public launch-readiness surface backed by the same local health/config checks used by uptime probes. External status hosting remains an operational setup step.
Local status checks are available; one or more launch-readiness integrations or external status hosting steps remain.
Last local check
Build
5b495828026337651e3a954ec0a7603564534bad
Status routing
/status is the local fallback while status.midas-edge.com is still pending setup.
The Next.js application is reachable and serving local health checks.
Source: /api/health
The public health endpoint is responding.
Source: /api/health
This checklist separates the app-owned fallback that is live now from external provider, DNS, and subscriber-notification work that still needs operational setup.
/status renders app-owned health and launch-readiness checks while external hosting is pending.
The global footer and security page direct users to the local status surface.
To make this surface available at status.midas-edge.com, configure the external status provider and DNS target described in the external uptime runbook. The component list above tracks local launch-readiness checks; provider monitor data appears after that external system exists.
Healthy in 104 ms.
Source: Supabase connectivity probe
Plaid client configuration is present for brokerage linking.
Source: Central env configuration
AI insight configuration is incomplete; AI features are setup-pending, but core app health is unaffected.
Source: Central env configuration (Vertex AI production path; direct Gemini only outside production)
Stripe server or webhook configuration is incomplete; billing is not launch-ready.
Source: Central env configuration
QStash dispatch and signature verification configuration is present.
Source: Central env configuration
Provision probes with the existing uptime setup workflow after provider credentials and alert contacts are configured.
Point the subdomain at the chosen status provider after the external page exists.
Enable public incident subscription channels in the external provider before launch.
Map monitors to provider components and require two consecutive failed checks before opening an incident.