Public Beta — Join as a Founding User and lock in 50% off while the offer is active. Register and create AI agents

KlicForgeKlicForge

Service status

This page describes how KlicForge availability is monitored and how incidents reach you. It is not a live status dashboard.

We do not yet publish automated uptime metrics, and KlicForge is in public beta with no uptime commitment. We would rather say that plainly than show a status indicator nothing measures.

What we monitor today

  • Readiness probes. Every API instance is polled continuously and pulled out of rotation when it cannot reach the database, so traffic is routed away from an unhealthy instance rather than failing against it.
  • Platform alerts. Failed deployments, domain and certificate problems, and repeated restarts or sustained high memory on the API all raise an alert to the engineering team.
  • Error monitoring. Unhandled API errors are captured and alert the engineering team.
  • Channel health checks. WhatsApp connection status is re-verified on a schedule, and a broken connection is surfaced in your dashboard.
  • Automated backups. The database is backed up daily on a rolling 7-day window.

Reporting an incident

If KlicForge is unavailable or degraded, email [email protected] with what you were doing and roughly when it started. During beta we respond to outage reports directly rather than through a status feed.

Security vulnerabilities go to [email protected] instead. If an incident involves personal data, our breach-notification commitments are set out in the Trust Hub.

Services we depend on

Much of what affects KlicForge availability happens at a provider we build on. These are their own live status pages — during an outage they are usually the fastest answer. The full list of providers and what each one processes is on our Subprocessor List.

Telegram does not publish a status page. If the Telegram channel is affected, we report it by email.