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.
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
votessort ranks by this month’s votes, then the all-time total. Atopsort 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 thebumpedsort — 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
| Feature | Voting System | Bump System |
|---|---|---|
| Frequency | Once per 12 hours | Once per 2 hours per listing |
| Ranking | This month’s votes, then all-time | Latest bump only |
| Goal | Long-term visibility | Short-term exposure |
The directory also sorts by members, online count, newest and search relevance.
Tips for Server Owners
- Maximize Votes: Encourage your community to vote every 12 hours to maintain a high ranking, especially early in the month to build momentum.
- Leverage Bumps: Use the bump system for quick visibility spikes, such as during events or recruitment drives.
- 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):
| Path | Workload | Source |
|---|---|---|
/api/v1/ballot/* | kbve-ballot | services/ballot |
/api/* | discordsh — the old axum web+API image | built outside this workspace |
| everything else | discordsh-web | apps/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
discordshschema, and every rule — cooldowns, daily caps, ownership — is enforced by thediscordsh.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-webaxum, which also writes listing, category, vanity and sitemap pages from the ballot directory. - Deployment: Kubernetes, synced by ArgoCD from
kube/discordsh. GitLab CI buildsregistry.gitlab.com/kbve/workspace/discordsh-weband.../discordsh-botwith buildkit (apps/discordsh/ci.yml).
Working on it
moon run discordsh:build # astro build --root webmoon run discordsh:check # astro checkmoon run discordsh:e2e # Playwright against web/moon run discordsh:server-dev # the axum serving web/dist on 4321moon run discordsh:web-server-testmoon run discordsh:bot-checkQuestions
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.