Status
One live check, in plain words, of the process behind the demo and the API. It says less than a full status dashboard would, on purpose: it only reports what it can actually verify.
This page fetches /demo/health from your browser when it loads. Nothing you type is sent anywhere.
Right now
Checking…
- API process
- —
- Monthly demo budget
- —
- Accepting demo requests
- —
- Checked
- —
Could not reach the API from your browser just now. That can mean the service is down, or that something between you and it, a network, an extension, a firewall, blocked the request. Try reloading, or check GitHub for a known issue.
What this covers
This check calls one endpoint, /demo/health, which reports whether the API process is running and how much of its own monthly demo budget has been spent. That is all it checks.
A green result here means the web process behind the demo and the dashboard's internal API answered. It does not mean every part of jevmod is healthy.
What this does not cover
- The Discord bot itself. Whether jevmod is online and answering in your specific server is a Discord-side fact this page cannot see; run
/mod statusin your server for that. - The moderation model. This page does not call TypeSafe; a message can still fail to judge, and fail open, even while this page reports the API as up. See what happens when the model is unreachable.
- Email and payment. Resend and Stripe are not checked here.
- History. This is a live snapshot, not an uptime log or an incident archive. There is no incident history to show yet.
Something looks wrong
For your own server, start with /mod status: it shows every threshold, every local rule, and your quota for the month, from inside Discord. If the bot itself seems unreachable, or this page disagrees with what you are seeing, write to omarhernandezbastos@gmail.com or open a GitHub issue.