Production Ping
Fast Liveness Check
This small public signal confirms the WarpIntel deployment is responding before deeper readiness checks run. Full route, provider, account, and launch-gate evidence remains on the health and monitoring surfaces.
Fast public liveness without provider, database, OAuth, or account checks.
production deployment metadata, sanitized for public monitoring.
Public follow-up routes for status, health, monitoring, and release review.
No database reads, provider calls, OAuth starts, private EVE data, or secrets.
fast liveness signal
Ping stays lightweight and delegates detailed readiness evidence to health and monitoring routes.
deep readiness delegated to health
Ping stays lightweight and delegates detailed readiness evidence to health and monitoring routes.
release metadata only
Ping stays lightweight and delegates detailed readiness evidence to health and monitoring routes.
no database read
Ping stays lightweight and delegates detailed readiness evidence to health and monitoring routes.
no provider call
Ping stays lightweight and delegates detailed readiness evidence to health and monitoring routes.
no OAuth start
Ping stays lightweight and delegates detailed readiness evidence to health and monitoring routes.
no private EVE data
Ping stays lightweight and delegates detailed readiness evidence to health and monitoring routes.
secret exclusion
Ping stays lightweight and delegates detailed readiness evidence to health and monitoring routes.
No-Secret Liveness Rule
Production ping exposes only app identity, sanitized release metadata, fast liveness status, public route links, and no-side-effect booleans. Deep readiness remains on /api/health. The ping route does not read databases, start OAuth, call EVE or CCP, call providers, mutate accounts, expose protected route bodies, expose provider credentials, expose EVE tokens, expose private EVE data, expose account data, or include separate-project details.