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-19T14:14:49.092Z
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 configured for distributed queue operation.
Stripe credentials and billing enforcement are active.
Outbound provider sends are enabled.
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: true
These items turn on provider-backed storage, queues, billing, live sends, and enforcement.
No activation gaps detected by the public readiness check.