This product was written inside a constraint, and the constraint made it better.

The constraint

LLMsMonitor runs on shared hosting and is deployed over FTP. No process runs in the background, there is no Redis, no Node on the server, a modest memory limit and one cron line:

*/15 * * * * php /home/ACCOUNT/laravel_worker/artisan schedule:loop

Everything hangs off that line. The host will not accept a per-minute cron, so the line fires every quarter of an hour and calls the scheduler once a minute from inside itself: the constraint became part of the answer too. The queue worker is born once a minute and exits on its own when it is done. Sessions, cache and the queue live in the same database. The charts read pre-aggregated daily tables and never touch a raw answer. Every job is small and repeatable, because a notification and a poll can both arrive for the same task.

Silent failure

On this kind of host, failures are silent. If cron stops, nobody says so; if the queue backs up, the screen keeps showing yesterday's numbers. Three things exist for exactly that:

• Health checks

  Is cron actually firing, is the queue draining, do the credentials still authenticate, are the schedules producing runs, is the config cache stale.

• An external status endpoint

  Nothing inside a dead host can report that the host is dead; so there is a status address an outside monitor can ask.

• A deploy screen

  One that exists only on the developer's machine, shows what would change, and uploads only then. On the server the screen is not hidden; it does not exist.

Discipline

As this was written, the product had more than 2,800 automated tests. Two of them sum up the whole product: ratios are summed first and divided last; a day with no runs is a gap, not a zero. A number comes out of the same arithmetic whatever filter it is looked at through.

Language

Turkish is not a localisation line item; it is the language the measuring is done in. The apostrophe, the suffixes, capital İ and dotless ı — all of it is inside the counter. We did not translate the interface; we built the counter for Turkish.

What we do not do

• We do not write answers. We measure what the assistants say; we do not tell them what to say.
• We do not promise rankings. We show where you stand and what changed.
• We do not show customer data as an example. Every figure on this site is invented and labelled as such.