Status
CogniLead platform health
Live readout for every component that powers the pipeline. Each row is a synchronous probe (1-second timeout) re-evaluated every 30 seconds. The JSON sibling at /status/json carries the same shape for monitoring tools.
| Component | Status | Mode | Detail | Checked |
|---|---|---|---|---|
| Database | operational | sqlite | 1 tenants · 4ms | 10:16:45 |
| Chainlog | operational | sqlite | verify 3ms | 10:16:45 |
| Stripe | memory | memory | no secret configured — billing in memory | 10:16:45 |
| Resend | memory | memory | dry-run — no transport configured | 10:16:45 |
| Sender domain pool | memory | memory | no active sender_domains rows · using DEFAULT_POOL | 10:16:45 |
| MCP server | operational | npm | @cognilead/mcp-server@0.1.0 | 10:16:45 |
Legend. ok the component is answering well under budget. slow answered but past the comfort threshold. down probe failed. configured a managed third-party (Stripe, Resend) is wired with a credential. memory running on the local stub — fine for the demo, not for production.
Status pages NEVER expose environment values or secrets — only mode labels and elapsed-ms.