Skip to content
ai · discord

Discord server topsiteDiscordSH

A topsite for Discord servers and bots, built to promote them through two mechanics — a monthly vote board and a bump sort. An Astro site served by a small axum, a Rust ballot service over Supabase Postgres, and a companion Discord bot.

Vote vs. bump

Voting is cumulative — once every 12 hours, ranked by this month's votes, with a new month starting at zero. Bumping lifts a listing in the recently-bumped sort for short-term exposure, once every 2 hours.

  • Frontend — Astro/Starlight + React islands.
  • Backend — Rust/axum over Supabase Postgres.
discordshApp
Rust + AxumStack
Supabase PostgresData
activeStatus

What it gives you

Features

Voting system

One vote per listing every 12 hours; the default board ranks by this month's votes, and the all-time total is kept beside it.

Bump system

A bump lifts a listing in the recently-bumped sort — once every 2 hours per listing, 10 a day per user, behind a captcha.

Servers and bots

Both are listings, with categories, tags, reviews, favorites, vote reminders and reports, plus vanity names that point discord.sh/name at a listing.

Server-rendered listings

Listing, category and sitemap pages are written by the axum that serves the site, from the ballot directory, so crawlers never wait on a script.

How it works

Voting, bumping & tips

Overview

DiscordSH is a topsite designed to promote Discord servers and bots through a dual mechanic of voting and bumping. Servers and bots are both listings: each has a page at discord.sh/s/<slug>, categories and tags, reviews, and can be favorited or reported. Owners verify a server through the bot, manage listings from the dashboard, and can claim a vanity name so discord.sh/<name> points at their listing.

Voting System

  • Frequency: A signed-in user can vote for a listing once every 12 hours, with a daily cap.
  • Ranking: The default votes sort ranks by this month’s votes, then the all-time total. A top sort ranks by the all-time total alone.
  • Monthly board: Every vote is kept and counted into its month. A new month starts at zero with no reset job; the all-time total never resets.
  • Reminders: A user can ask to be reminded when their vote cooldown ends.

Bump System

  • Mechanism: A bump stamps the listing’s bumped_at, lifting it in the bumped sort — the stream of recently promoted listings.
  • Limits: Once every 2 hours per listing, and at most 10 bumps per user in 24 hours. Each bump passes a captcha.
  • Purpose: Promotion focused on immediacy rather than cumulative effort, ideal for quick visibility boosts.

Key Differences

FeatureVoting SystemBump System
FrequencyOnce per 12 hoursOnce per 2 hours per listing
RankingThis month’s votes, then all-timeLatest bump only
GoalLong-term visibilityShort-term exposure

The directory also sorts by members, online count, newest and search relevance.

Tips for Server Owners

  1. Maximize Votes: Encourage your community to vote every 12 hours to maintain a high ranking, especially early in the month to build momentum.
  2. Leverage Bumps: Use the bump system for quick visibility spikes, such as during events or recruitment drives.
  3. Combine Strategies: Pair consistent voting with periodic bumps to balance sustained growth and immediate attention.

Architecture

Development & tech stack

discord.sh is one moon project, apps/discordsh, plus a service beside it. The gateway splits the hostname by path (kube/discordsh/manifests/httproute.yaml):

PathWorkloadSource
/api/v1/ballot/*kbve-ballotservices/ballot
/api/*discordsh — the old axum web+API imagebuilt outside this workspace
everything elsediscordsh-webapps/discordsh/web

The bot, discordsh-bot, runs beside them from apps/discordsh/bot.

Tech Stack

  • Database: Supabase Postgres. Listings, votes, bumps, reviews and vanity names live in the discordsh schema, and every rule — cooldowns, daily caps, ownership — is enforced by the discordsh.service_* functions (schemas/sql).
  • Ballot: kbve-ballot, a Rust/axum service that holds the service-role key and the captcha secret, says who is asking, and calls those functions.
  • Frontend: Astro/Starlight with React islands, built static and served by the discordsh-web axum, which also writes listing, category, vanity and sitemap pages from the ballot directory.
  • Deployment: Kubernetes, synced by ArgoCD from kube/discordsh. GitLab CI builds registry.gitlab.com/kbve/workspace/discordsh-web and .../discordsh-bot with buildkit (apps/discordsh/ci.yml).

Working on it

Terminal window
moon run discordsh:build # astro build --root web
moon run discordsh:check # astro check
moon run discordsh:e2e # Playwright against web/
moon run discordsh:server-dev # the axum serving web/dist on 4321
moon run discordsh:web-server-test
moon run discordsh:bot-check

Questions

Frequently asked

What is DiscordSH?

DiscordSH (discord.sh) is a topsite for Discord servers and bots that promotes them through two mechanics — a voting system and a bump system — helping owners increase visibility and attract new members.

How does DiscordSH voting differ from bumping?

Votes are cumulative — one vote per listing every 12 hours, the default board ranks by this month's votes and a new month starts at zero, while the all-time total is kept. Bumping puts a listing at the top of the recently-bumped sort, once every 2 hours per listing and up to 10 bumps a day per user, behind a captcha.

What is the DiscordSH tech stack?

An Astro/Starlight site with React islands, served by a small Rust/axum server (discordsh-web); a Rust/axum service, kbve-ballot, that owns votes, bumps, listings and vanity names over Supabase Postgres functions; and a Rust Discord bot. All run on Kubernetes, synced by ArgoCD from kube/discordsh.

Discuss on the forum

Questions, fixes and notes on this page live in the KBVE forum.