Loading…
Loading…
Use this page to see the Vercel production runtime clearly. Lead OS can create solution outputs; external actions such as durable storage, queues, billing, and live sends activate when the required account access is connected.
Public URL and environment context.
URL: https://lead-os-hosted-runtime-wt-hybrid.vercel.app
Environment: production
Vercel: true
Checked: 2026-05-19T12:55:44.265Z
These are the public or operator-facing pieces deployed in the current production build.
The Next.js application is deployed to Vercel and publicly viewable.
Returns live API, pricing runtime, worker, and database configuration status.
Returns public service identity without leaking integration secrets.
The dashboard route is deployed; sensitive mutations require operator authentication.
A production database URL is present.
Redis is not attached, so queue-backed work runs only through fallbacks or remains idle.
Stripe credentials are present, but billing enforcement is disabled.
Live sends are disabled until provider credentials are verified.
Assessment based on the production runtime, not local assumptions.
View public site: true
Assess public health: true
Open operator dashboard route: true
Production persistence ready: true
Monetization ready: false
These items turn on provider-backed storage, queues, billing, live sends, and enforcement.