Service status

/* REPLACE BEFORE LAUNCH: Replace this local status placeholder with the production hosted status page URL and incident process. */

Current status

CryptoCompanion is in local build and pre-launch hardening. A public hosted status page will be connected when staging and production infrastructure are available.

Until then, local health checks, deployment reports, and daily reviews are the source of truth for readiness.

Monitored surfaces

The production status page should cover the web app, API, admin app, PostgreSQL, Redis, queue workers, exchange sync, alert delivery, payment webhooks, and external providers that materially affect user workflows.

Incident communication

Public incidents should include affected surfaces, start time, user impact, current mitigation, recovery time, and post-incident follow-up when warranted.

Planned launch hardening

Before public launch, status monitoring should include API health checks, worker lag, queue failures, payment webhook delivery, database availability, Redis availability, uptime checks, and alert delivery checks.