💎 Crystal Uptime

Uptime monitoring for your websites, Discord bots, and servers — from Discord and the web. Built with 💜 by Crystal Studio Labs — github.com/Crystal-Studio-Labs

Crystal Uptime keeps your online services online. It pings your websites, Discord bots, Minecraft servers, and raw IP addresses every 30 seconds, records their uptime history, posts live status embeds to your Discord server, and alerts you — with role pings — the moment something goes down. Manage everything from Discord or from the web dashboard, and share live status pages with your community.

---

✨ Highlights

• Monitor anything — websites (HTTP), Minecraft servers, or raw IPs (ICMP ping).
• Live status embeds in Discord with uptime %, latency, and a recent-history graph.
• Instant up/down alerts with optional role pings to a dedicated error channel.
• Web dashboard — add, remove, and view your monitors from any browser.
• Public status pages — share a live status page for your services.
• Premium & Enterprise tiers with redeemable codes and higher monitor limits.
• Multi-database — Postgres (Supabase, Neon, Railway), SQLite, MySQL, or MongoDB (native driver or Mongoose) via a single env switch.
• Runs on any free host — no native modules in the default path, no local storage, PORT-aware web server.

How it works

┌─ Discord bot ─────────────┐   ┌─ Website (same Express server) ─┐
│ /register  /remove        │   │ Landing · Discord OAuth2 login  │
│ /details   /my-monitors   │   │ Dashboard · Public status pages │
│ ── 30s monitor loop ──────┼──►│ Premium · Stats                 │
└─────────────┬─────────────┘   └──────────────┬──────────────────┘
              └──────────► src/database ◄──────┘
              (multi-DB: Postgres/SQLite/MySQL/MongoDB)

Monitors are owned by a Discord user ID. Monitors added on the website show up in Discord — and vice versa — because both surfaces read the same data.

🖥️ Web app

A React + Vite single-page app served by the same Express server (no separate deploy — the bot hosts it):

Route	Page
/	Landing — hero, features, live bot stats
/login	Discord OAuth2 sign-in (redirects to /api/auth/login)
/dashboard	Manage monitors (add/remove, live status, 30-day uptime), public-page toggle
/status/:username	Public status page (opt-in per user)
/premium	Plan tiers + redeem-code form
/stats	Leaderboard + system counts

Source lives in web/ and talks to the same API the Discord commands use:

• GET/POST/DELETE /api/monitors — list, register, remove (auth)
• GET/POST /api/settings — profile + public-page toggle (auth)
• GET /api/premium/plans · POST /api/premium/redeem (auth)
• GET /api/status/:username — public status page
• GET /api/stats — leaderboard + system counts

Protected routes require the Discord login session; everything is same-origin behind the /api rate limiter and CSP headers.

Quick start

Prerequisites

• Node.js ≥ 18
• A Discord application (bot token + client ID) from the Discord Developer Portal
• A database: Postgres (Supabase, Neon, Railway), MySQL, or SQLite for local dev

1. Install

npm install

2. Configure

cp .env.example .env   # then fill in your values

Required: TOKEN, CLIENT_ID, and a database (DB_TYPE + DATABASE_URL). See .env.example for the full list — including CLIENT_SECRET (website login), log channels, and brand links.

3. Migrate the database

npm run migrate       # creates the schema (also runs automatically at boot)

4. Build the web app (once)

npm run build:web     # builds the React + Vite app into web/dist

The Express server serves web/dist when it exists (SPA fallback for /dashboard, /status/:username, …). For frontend work, npm run dev:web runs Vite with hot reload and proxies /api to the bot.

5. Run

npm start             # boots the Discord bot + web server

The web server binds process.env.PORT (default 8089) and serves the web dashboard and the bot stats API.

Health checks

npm test              # data-layer smoke test (in-memory SQLite)
npm run test:mongo    # MongoDB backends smoke test (mongodb + mongoose)
npm run security      # secret scan + dependency vulnerability audit
npm run build:web     # production build of the React web app
curl localhost:8089/health   # web liveness probe (200 when DB connected)

Discord commands

Category	Commands
Monitor	register, remove, details, group, checkurl, my-monitors, ssl-reminder, malware-check
Info	about, help, stats, invite, ping, profile, socials, discord, alert
Premium	buy, redeem, gencode, perks
Owner/Staff	announcement, blacklist, control-panel, shutdown
Other	vote, feedback, suggestion, settings

🗄️ Database

Supported backends (up to 5 connections each)

Backend	Type	Notes
Supabase ⭐	postgres	Default / recommended — hosted Postgres, generous free tier
Neon	postgres	Serverless Postgres, always-on free tier
Railway Postgres	postgres	Hosted Postgres add-on
SQLite	sqlite	Local dev only (no server needed)
MySQL / MariaDB	mysql	Any MySQL-compatible host
MongoDB Atlas	mongodb	Native mongodb driver — M0 free tier (512 MB) works
MongoDB Atlas	mongoose	Mongoose ORM on the same Atlas cluster

MongoDB (Phase 2.5): two selectable backends share the exact same repo API (DB_TYPE=mongodb native driver, DB_TYPE=mongoose Mongoose). Both are schemaless — npm run migrate is a no-op and unique/query indexes are ensured at boot. Validate either with npm run test:mongo (in-memory MongoDB, or set SMOKE_MONGO_URL to point at a real Atlas cluster).

Selected default

We use Supabase (Postgres) as the primary database. It's free, hosted, works from any host, and the data layer is written so you can switch or add backends without code changes.

Multiple databases — up to 5 per type

Connect up to 5 databases of the same type at once — for example 5 different Supabase projects. All connections share the same type (DB_TYPE); mixing types is not supported.

# Primary connection
DB_TYPE=postgres
DATABASE_URL=postgres://user:pass@supabase-a/db

# Additional connections (DB_2 … DB_5) — same type, up to 5 total
DB_2_URL=postgres://user:pass@supabase-b/db
DB_3_URL=postgres://user:pass@supabase-c/db

How it works

The data layer (src/database/) is a repository layer over Knex for SQL backends (postgres | sqlite | mysql — shared schema and migrations), and a parallel repository layer for MongoDB (mongodb native driver and mongoose ORM — index management instead of DDL). All backends expose the same repo API and output shape, so switching DB_TYPE needs no code changes. Migrations run automatically at boot and via npm run migrate (no-op on Mongo); npm test validates the SQL layer and npm run test:mongo validates both Mongo backends.

Hosting

• Runs on any free PaaS/VPS that can run a Node.js process and reach the internet.
• Recommended for true 24/7: Oracle Cloud Always Free (ARM) or Railway.
• Free tiers of Render/Koyeb/Replit/Glitch sleep on inactivity — the bot's Discord gateway disconnects while asleep; keep that in mind.
• The default path uses pure-JS database drivers and writes no local files, so ephemeral filesystems are fine.
• Port & shutdown: the web server binds PORT (default 8089); the process handles SIGINT/SIGTERM gracefully (closes the web server, database connections, and the Discord gateway).

🔒 Security

• No secrets in the repository — every credential is read from the environment.
• Secure web login — Discord OAuth2 with a CSRF state param, server-side token exchange, and httpOnly cookies; only SHA-256 session-token hashes are stored.
• Multi-DB connections use least-privilege roles and TLS where available.
• A built-in npm run security scanner checks for leaked secrets and dependency vulnerabilities before every release.

💬 Support & Contact

Need help, have a feature request, or want to report an issue?

• 📧 Email: connect.crystalstudio@gmail.com
• 🐙 GitHub: open an issue
• 📄 Documentation: developers.txt · llms.txt · CONTRIBUTING.md

License

MIT © 2026 Crystal Studio Labs