Documentation

meros_basement.web is the public front for a set of small, specialized Discord bots. The site is a static front-end: it ships pre-rendered pages and requests live data from a shared database at runtime to show bot status and metrics.

There are two sides to the project: the public site (this one) and a private dev console used for administration. Only the public side is documented here.

The bot directory and its public JSON API (existAPI reference) have their own pages. Developer sign-in, bot submissions and API keys live under /developer.

• • Front-end: Next.js with a static export — every page is pre-rendered HTML and served from the edge.
• • Hosting: static assets are served globally; there is no server runtime for the public site.
• • Data layer: a hosted Postgres database with row-level security. The site reads it with a public (anonymous) key; write access is constrained by policies.
• • Bots: independently run processes that report their state to the same database.

1. 1. Each bot periodically writes a compact heartbeat — counts, uptime, ping, and a rolling activity window.
2. 2. Heartbeats are aggregated into a small number of records in the database.
3. 3. The site fetches those records at runtime and renders the Status and Dashboard views.
4. 4. Nothing user-identifying is part of this stream — see the privacy principles below.

A bot is shown as online while its most recent heartbeat is fresh; once heartbeats stop it flips to offline. A manual maintenance flag overrides the automatic state, and a bot that has never reported shows as no data.

Catalog status labels — Active, In dev, Discontinued and Lost — describe a project's maturity, not its current online state. The two are independent on purpose.

• • The public metrics contain no message content and no user IDs.
• • Only aggregate counts (messages, commands, activity windows) are exposed.
• • The database uses row-level security so the public key can only read what's meant to be public.
• • Per-bot data handling is described in each bot's policy, linked from the Privacy & Terms page.

Per-bot command references and setup guides are still being written. For now, the quickest way to get help with a specific bot is to ask in the community server.