All of it, not just the good ones. The status below is a real HTTP probe, run automatically. What's down stays listed — admitting it is part of the point.
Node.js + Sheets API
responding
Static HTML (build script) + Node.js API (PM2 :3120, localhost) + DeepSeek + PWA
responding
Laravel + Blade + PostgreSQL + Docker
responding
Node.js + DeepSeek + Docker
Telegram bot
Flask + Python
responding
Cloudflare Pages
responding
Static HTML + CSS + JS + PWA
responding
Static HTML + Vanilla JS + PWA (client-side, no backend)
responding
Node.js (vanilla http) + PM2
responding
Static HTML + CSS + JS + PWA
responding
Next.js 16 + self-hosted Supabase (Postgres/Auth/PostgREST/Edge Functions) + Telegram bot
responding
Static HTML + PWA, Cloudflare Pages
responding
code-server + PM2
responding
DBgate Docker
auth-protected
Node.js (vanilla http) + PM2
responding
Static HTML + vanilla JS
responding
Static HTML + vanilla JS (frontend) + Node.js/Express (backend url-directory-api)
responding
Node.js + Express + SQLite
responding
Static HTML + Vanilla JS + PWA (client-side, no backend)
responding
Cloudflare Pages (single-file HTML)
responding
PWA (vanilla JS, Web Speech API) + Node.js Express + DeepSeek
responding
Python hermes_cli + DeepSeek
Telegram bot
Node.js + Express + SQLite + Google Sheets/Docs API
responding
Static HTML + CSS + JS + PWA
responding
Next.js 16 + TypeScript + Tailwind v4
responding
Cloudflare Pages
responding
Laravel + SQLite
not responding · —
Node.js + SQLite (Midtrans) + GSheets
not responding · 502
React + Vite + TypeScript + Tailwind v4, IndexedDB
responding
Cloudflare Pages
responding
Flask + Python (SQLite) + gunicorn
responding
Static HTML + CSS + JS + PWA
responding
Static HTML + CSS + JS, tracker Node.js + better-sqlite3 (learn-tracker, PM2, port 3046)
responding
Next.js 14 static export + Caddy
responding
Let's MUV Bot
Node.js + node-telegram-bot-api + OpenAI SDK (DeepSeek)
Next.js (App Router) + Tailwind + better-sqlite3
responding
Static HTML + Vanilla JS + PWA (client-side, no backend)
responding
React + Vite + @excalidraw/excalidraw (static build) + meero-api (Express + better-sqlite3, PM2, port 3100, sync opsional)
responding
Next.js 14 + Prisma + PostgreSQL + Docker
responding
Static HTML + IndexedDB (client-side) + notepad-api (Express + better-sqlite3, PM2, port 3099, localhost-only) untuk fitur Share
responding
OCR Service
Node.js + Tesseract OCR + poppler-utils
Next.js 16 + TypeScript + Docker + local VPS storage + PWA
not responding · 502
Docker
not responding · —
Static HTML + Vanilla JS (client-side, no backend)
responding
Node.js + Express + SQLite + Static HTML
responding
Cloudflare Pages
responding
Static HTML + Vanilla JS + PWA (client-side, no backend)
responding
Node.js
not responding · 502
React + Vite + TypeScript + Tailwind CSS v4 (client-side, no backend)
responding
Node.js + GSheets API
responding
Static HTML + Monitoring API Node.js
responding
Portfolio: Static HTML + Chrome Ext + Figma plugin + VS Code ext + Next.js (PollDeck)
responding
QR Generator
Flutter + Riverpod + go_router + Drift/SQLite + qr_flutter + mobile_scanner (self-test)
QR Scanner
Flutter + Riverpod + go_router + Drift/SQLite + mobile_scanner
Static HTML PWA
responding
Node.js + Express (numpang backend kantinmu-smm, port 3056) + better-sqlite3 + static HTML/JS PWA
responding
Static HTML/CSS/JS + PWA (manifest + SW)
responding
Static HTML/CSS/JS + Node.js/Express + JSON storage
responding
Node.js + Express + Google Sheets API + PWA
responding
Next.js 16 (App Router, basePath) + TypeScript + Tailwind v4 + Prisma 7 (SQLite, driver adapter) + Zod
not responding · 502
Flask + Docker
not responding · 502
Node.js + Express + Google Sheets API + DeepSeek
responding
Docker (upstream image stirlingtools/stirling-pdf)
not responding · 502
Cloudflare Pages
responding
SID Core Automation
Node.js (ESM) + googleapis + dotenv
SID Dev Toolkit
Chrome Extension Manifest V3 (vanilla JS) — webRequest + declarativeNetRequest + storage
Static HTML + vanilla JS + inline SVG, no framework
responding
Node.js Express + Google Sheets API + Telegram Bot
responding
Node.js + Docker
Telegram bot
Static HTML + vanilla JS, PWA
responding
Node.js + Anthropic SDK
Telegram bot
ttyd + bash
not responding · 502
Static HTML + CSS + JS + JSON Registry + PWA + Node admin API (PM2)
responding
Node.js + SQLite
responding
Node.js Express (port 3057) + static SPA (PWA)
responding
Telegram bots can't be judged by an HTTP probe the way a web page can, so they aren't claimed as “responding”.
Not responding at the last check. Some are deliberately retired; some I need to fix.