PUGZ brings PUGs, ranked ladders, scrims, tournaments, leagues, coaching, teams and player statistics together in one connected platform.
Find your teammates. Build your team. Climb the rankings. Compete for prizes.
From your first competitive match to your next tournament final, there’s a place for you here.
Built for the community. All revenue reinvested.
Independently developed, personally funded and built to help the competitive scene grow.
Currently in closed beta.
The core platform is built and being tested. Explore the features below and follow our public launch through the Discord linked on pugz.gg.
Play through Discord. Queue, track and manage on the website.
One Discord login connects your matches, team, rankings and achievements.
|
Everything you need to get into a match and keep it moving.
|
Your competitive career, and the tools to take it further.
|
Good competition needs more than a queue. PUGZ connects match results, player reports and moderation records so players know what to expect and staff have the context to act.
| Feature | What it means for players |
|---|---|
| Transparent penalties | Published rules explain warning points and how repeated offences lead to queue bans, timeouts or bans. |
| Ready checks that keep things moving | Players who miss the check are replaced, with escalating penalties for repeat offences. |
| One player, one account | Staff review suspected alternate accounts, so every rating and leaderboard place belongs to one real player. |
| No escaping a loss | A player who leaves an active match and is replaced still takes the loss if their team loses. |
| Confirmed results | The opposing team confirms the score, or staff review the dispute and decide the result. |
| A record behind every decision | Match timelines, moderation cases and staff audit logs provide context for reviews and corrections. |
| Progress that survives a restart | Queues, matches and timers are stored so they can be restored after a restart or deployment. |
| Control over your data | Players can request deletion of their player data. |
- Earn a rank people can see. Your rating connects to a Discord rank role, profile badge and leaderboard position. Promotions and demotions update as you cross rank thresholds.
- Make every result count. Scorelines, opponent strength and placement settings shape the rating system. Each season sets its own starting rating, points and ranks. Corrections, voided results, late disputes and rule changes automatically recalculate the season.
- Compete across seasons. Everyone starts a new season unranked and re-earns their rank role. Complete placements to enter the leaderboard, then work towards your final position. Past seasons keep their standings and ranks, and a match that started before the new season counts towards the old one.
- Take on the 1v1 ladder. A separate rating and rank, with matchmaking that finds the closest available opponent and broadens the search as you wait.
- Race for rewards. Our aim is to offer seasonal leaderboard prizes and prizes in PUGZ-hosted tournaments, including cash and Multibucks codes.
The main 3v3 queue is split into B, A and S tiers, helping players find opponents closer to their level and a leaderboard race of their own.
- Play within your tier. Separate queues keep players in their assigned skill group.
- Start where you belong. Embark ranked history and your previous PUGZ season determine your starting tier, with a placement check after 15 matches.
- Earn your way up. Reach the next tier’s rating threshold and move up immediately, even mid-season.
- Keep your tier for the season. Individual ranks can rise or fall; queue tiers only move upwards during a season.
- Compete in your own prize race. Each tier has its own standings and planned cash prizes.
Every picture is drawn from real match data, in the PUGZ look, ready to post.
- Your player card.
/card, or Player card on anyone in the server, draws your rank, rating, record and form. Choose whether it shows your 3v3 or 1v1 ladder. - A result card for every match. Each confirmed result is posted as a picture with the score, the teams and every player’s rating change. The public match page uses it as its link preview.
- Links that unfurl. Share a profile or a match page on Discord or X and it opens as the card, not a bare link.
- A leaderboard that moves. The live board in Discord opens with an animated banner of the season’s top three, in a Podium or Trio look, and updates as results come in.
- The week in stories.
/recaptells the week’s biggest climbs, streaks and upsets. My week tells you yours. - Panels with some life in them. The queue panel, rules post and ticket panel open with animated PUGZ banners, and the last open slot in a queue pulses until someone takes it.
|
Turn a few good teammates into a team with a history.
|
Spend more time practising and less time arranging it.
|
One place where teams that need players and players who need a team find each other. In development.
- Post that you’re looking. A Looking for team card shows your classes, roles, play times, goals and languages, next to your rank, rating and reliability, read from your matches rather than typed.
- See who fits. Every team and player gets a fit score built from region, rank, overlapping play times, the roles a team needs, goals and language, with the reasons shown: Plays the same times, Needs a Medium.
- Talk before you commit. Applying opens a private Discord thread with the team’s captains. Teams can run a tryout of up to a week, with the scrims and PUGs played together shown on the application.
- Fill a gap at short notice. A team that is one player short for a scrim can call players who are looking, in its region and rank range. The first to accept is on the roster.
- From Discord too. A live Find a team board,
/lftfor the teams that fit you and/lfpfor the players that fit your team. - No pay to be seen. Places are earned by fit and recency, never bought.
Register your team, check in and follow the bracket as results come in. PUGZ handles the competition across Discord and the website, with tools for our own events and independent organisers.
- The format your event needs. Single or double elimination, round robin, Swiss, groups into playoffs and Cashout lobbies. Manual or automatic seeding, with automatically generated and updated brackets.
- Registration that stays organised. Website sign-ups or Discord join codes, pre-event check-in and a waitlist for additional teams.
- A room for every match. Dedicated match spaces with score reporting, confirmation, disputes and map vetoes where the format requires them.
- Practice before event day. Staff can rehearse a full tournament with practice teams.
- Prizes and achievements. Prize pools listed before registration, winner roles and results recorded on team and player profiles.
- Your community can host too. Run tournaments in your own Discord server using the PUGZ bot. This capability is currently in testing.
Explore the PUGZ Beta Cup Invitational on pugz.gg for an example.
A broadcast shouldn’t depend on someone retyping scores. The production desk connects the stream to the tournament it’s showing.
- Overlays fed by live data. Score bug, map veto, bracket, standings, results, the next match and team line-ups come straight from the tournament, the moment a result is confirmed.
- A full stream pack. Around 60 transparent 1920 × 1080 screens in the PUGZ look, from the starting screen to the final results, loaded into OBS as browser sources.
- One desk for the producer. Pick the match that goes on air and every overlay follows it. Ask the mods to hold the next stream match until the broadcast is ready.
- Your words where they matter. Caster names, alerts and highlight moments are typed on the desk, and any live value can be overridden and set back.
- Private per tournament. Overlays are served from pugz.gg behind a stream key that can be changed at any time. An offline pack covers events without a connection.
- A seat for every production role. Producer, observer, caster and broadcaster sit beside the leads, mods and hosts on the tournament dashboard, each with their own shift and job.
A seasonal 3v3 league with free entry, weekly matches and cash prizes for division champions. Build a campaign with your team, earn your place in the playoffs and finish on Finals Night, with division finals played back to back on one evening.
- A regular competitive schedule. Three seasons per year, planned at around 13 weeks each. Seven weeks of regular-season Bo3s lead into top-four semi-finals and a Bo5 final.
- A division to compete in. Four divisions, with additional groups when needed to accommodate more teams. Each division shares one playoff and one champion’s prize.
- A route into the league. New teams play a placement weekend; returning teams keep the division they earned.
- Something to play for next season. Finalists earn promotion where a higher division exists, while the lowest regular-season teams face relegation.
- Rank limits for each division. Rosters must meet the division’s Embark rank limits, keeping higher-ranked teams out of lower-ranked divisions.
- A consistent team. Three players and up to two substitutes, and one team per player each season. Rosters lock after week four, and players need two regular-season appearances to play in the playoffs.
- Scheduling with flexibility. A default weekly match time, with captains able to agree on another slot through the match panel.
- A title that stays with you. Division champions earn a cash prize, a champion role and a profile achievement. Higher divisions carry larger prizes.
Find a coach who understands what you want to improve. Compare experience, specialties, packages, reviews and availability, then arrange your session in one place.
For coaches, PUGZ provides a place to offer paid sessions, set your prices and schedule, and manage bookings. The coaching platform is currently in testing.
- Staff-approved coaches. Profiles show verified peak league, specialties and reviews, covering Light, Medium, Heavy, aim, game sense, team play and VOD reviews.
- Clear packages and availability. See session length, what is included and the next available slot. Coaches manage their availability and accept or decline requests.
- Payments through Stripe. Coaches sell their sessions through the platform, with a PUGZ fee. Card details never touch our servers.
- Completion before payout. Coach payouts are released after session confirmation; reported problems are reviewed before release.
- A space for the session. Booking chat and a private voice room that opens 15 minutes before the start.
- Promotions. Coaches can run a time-limited discount on some or all of their sessions.
- Become a coach. A guided onboarding takes you from application to staff approval to your first listed package.
- Reviews from actual sessions. Only players who complete a session can leave a review, and coaches can reply.
PUGZ is independently developed, and we personally cover a significant portion of its development and running costs. All revenue from donations and platform fees is reinvested into operating the platform, improving its features and funding competitive prize pools. We take no personal income or profit from PUGZ.
The goal is to give the community more opportunities to play, improve and compete, and keep building on what we can offer.
Our vision reaches beyond one server: communities running their own competitions while contributing to a connected competitive scene. Tournament hosting on other servers is in testing. Shared PUG queues, ratings and leaderboards are planned for after public launch.
|
Built and in testing.
|
Planned after public launch.
|
PUGZ is in closed beta. The core platform is built and being tested end to end on our own Discord server. Public access will follow testing.
In testing means the feature is built and being validated. In progress means development is ongoing. Planned means it is part of the roadmap.
Next up, in order: Tournament dashboard → League → PUGs on your own server.
The website, Discord bot and background worker share a PostgreSQL database. The bot manages changes to match data; website actions reach it as commands. Database notifications keep services updated, while a durable job queue handles background tasks and external integrations.
| Layer | Technology |
|---|---|
| Language | TypeScript with strict checking, in one monorepo |
| Bot | Node.js 24, discord.js v14, Components v2 |
| Website | Fastify 5, React 19, Vite, Tailwind CSS v4 |
| Database | PostgreSQL 18, Prisma |
| Background jobs | pg-boss, backed by the same database |
| Payments | Stripe and Stripe Connect |
| Quality | Vitest integration tests against a real database, including restart and concurrency scenarios |
| Designed for | 100+ simultaneous players across queues and matches |
Follow the launch, meet the community and help shape PUGZ during closed beta.
Know someone in the closed beta? Testers can send a friend a private invite with /invite-beta.
Questions, bugs or ideas? Open a ticket in the Discord.
PUGZ is an independent registered business. Not affiliated with Embark Studios.
THE FINALS and Embark Studios are trademarks of their respective owners.
© 2026 PUGZ