# Vetox vs SassGuard

> Vetox vs SassGuard: three features marked free on one page and premium on another, and a changelog with one entry, against published limits and 41 systems.

- Canonical: https://discordbots.blog/blog/vetox-vs-sassguard
- Published: 2026-10-03
- Author: The Field Guide desk
- Competitor facts checked: 2026-08-31
- Sources:
  - sassguard.app (https://sassguard.app/en/premium) — checked 2026-08-31
  - docs.vetox.io — feature limits by tier (https://docs.vetox.io/en/premium/feature-limits) — checked 2026-08-31
  - docs.vetox.io — Auto-Mod (https://docs.vetox.io/en/moderation/auto-mod) — checked 2026-08-31
- Publication: The Field Guide, an independent site not affiliated with Discord Inc.

---
## The distinction that decides which bot you need

**SassGuard's own two pages disagree about what its free tier includes.** The AI assistant, Join Gate
and Linked Roles are marked **free on one page and premium on the other** — three features, two
answers, no resolution.

**Vetox publishes every per-tier limit once**, on a dated feature-limits page that the rest of the
documentation defers to, covering all 41 systems.

The difference decides the comparison because a buyer cannot evaluate a product whose free tier has
two published definitions.

## How this comparison was built

SassGuard's contradictory feature markings, daily token allowances and changelog history are read from
its own site and Terms of Service. Vetox's from its configuration surfaces and published per-tier
limits. Both checked 31 August 2026. Ranked on published consistency, breadth and auditability — not
on install count.

## Three features, two answers

The disagreement matters more than a typo would, because of _which_ three features.

**The AI assistant** is the headline capability. **Join Gate** is the verification layer a server
installs the product for. **Linked Roles** is the Discord integration that makes verification useful.
Those are not peripheral rows in a table — they are the reasons to adopt the product, and whether they
cost money has two published answers.

A prospective user reading the documentation concludes one thing; reading the pricing page, another.
Neither page acknowledges the other, and neither carries a date, so there is no way to tell which is
current.

**Vetox's figures appear once per limit.** Eight Auto-Mod rule types with 1,000 keyword entries free;
Anti-Raid and Join Guard at Basic; AI Auto-Moderation on Black. One page states each, and the feature
pages defer to it rather than restating it.

## A changelog with one entry

**SassGuard's changelog carries exactly one entry, dated 19 November 2025** — while a compliance
layer, a white-label custom bot and a ticket assistant have shipped since.

The product is clearly being developed. The record of that development is not being kept.

That matters for a moderation product specifically: when behaviour changes, a server needs to know
whether the change was intentional. An unmaintained changelog means every behaviour change is
indistinguishable from a bug, and the only way to learn what changed is to notice it.

**Vetox's equivalent is structural rather than promissory.** Dashboard Watcher records **who changed
which module, when**, with module, time-window and free-text filters, retained **90 days, free on
every tier**. That answers the question a changelog cannot: not just what the vendor changed, but what
your own staff changed.

## Daily token pools, and where they are published

Credit to SassGuard for publishing its AI allowances at all — **100,000 tokens a day free, 250,000 on
Premium, 500,000 on Premium+**, resetting daily.

The location is the issue: those figures live in the **Terms of Service**, not the pricing page. A
buyer comparing plans does not read the ToS, and the numbers that determine whether the AI is usable
at their scale are not where the purchase decision is made.

**Vetox's AI allowance is stated with the tier it belongs to** — a monthly token allowance included
with Black at $17.99, with an optional top-up at a published $1 per 500K tokens.

## The comparison

| Capability                   | SassGuard                            | Vetox                                          |
| ---------------------------- | ------------------------------------ | ---------------------------------------------- |
| **Free-tier definition**     | **Two pages disagree on 3 features** | **One figure per limit, published**            |
| **Changelog**                | **One entry, Nov 2025**              | **90-day config audit, free**                  |
| AI allowance published       | Yes — in the Terms of Service        | **Yes — beside the tier**                      |
| Automod                      | Yes                                  | **8 rule types, 1,000 keyword entries — free** |
| Escalation across rules      | —                                    | **Automated Actions — 1 free, 50 paid**        |
| Insider protection           | —                                    | **Protection — 20 rules, free**                |
| Moderation case history      | —                                    | **100 warnings/user — free**                   |
| Logging                      | —                                    | **148 event types — free**                     |
| Levelling                    | —                                    | **Text and voice XP — free**                   |
| Languages                    | —                                    | **21**                                         |
| **Systems on one dashboard** | Moderation and verification          | **41**                                         |

## What Vetox does well

**One published number per limit.** Every ceiling for all 41 systems on a single dated page, with the
feature pages deferring to it — so there is no second answer to find.

**Protection is layered and mostly free.** Eight Auto-Mod rule types with 1,000 keyword entries, 20
exempt roles and 50 exempt channels; Automated Actions escalating across rules in a rolling window;
Protection watching the audit log for insider damage with 20 rules. All free on Starter, each covering
a different failure mode.

**Verification is a full system, not a gate.** Anti-Raid's rolling-window join detection plus Join
Guard's **10 named conditions**, each combining up to 5 rules with AND/OR logic and firing up to 5
actions — kick, ban, role assignment or opening a reviewable case.

**Changes are recorded whoever makes them.** 90 days of configuration history, free, plus 148 log
event types and a 100-warning case history — so a question about last month has an answer.

**AI is priced with its tier.** Included on Black with a monthly allowance stated beside the price,
and a published top-up rate.

**And it is 41 systems, in 21 languages**, on one dashboard — moderation, tickets, levelling,
welcomes, giveaways, notifications across eight platforms, and 40 games.

## Why a stale changelog costs more than it appears to

It is easy to treat an unmaintained changelog as a documentation chore nobody got to. For a moderation
product it is closer to an operational gap.

**Behaviour changes are invisible until they bite.** A filter that starts matching differently, a
verification step that gains a condition, a rate limit that tightens — none of these announce
themselves in the server. The first signal is a member complaining, and without a changelog there is
nothing to check against.

**It makes every incident harder to diagnose.** The first question after unexpected behaviour is "did
something change?" A maintained changelog answers it in ten seconds. An unmaintained one leaves the
server to distinguish a vendor change from its own misconfiguration by experiment.

**It removes the only external record of the product's history.** Three significant features shipping
with no published record means the product a server evaluated is not necessarily the product it is
running, and there is no document describing the difference.

**And it compounds with contradictory pricing pages.** If two pages disagree about the free tier and
no changelog records when either was written, a reader cannot even determine which one changed.

Vetox's answer covers the half a vendor changelog never can: **90 days of who-changed-what inside your
own server**, free on every tier, so the most common cause of unexpected behaviour — a staff member
changing a setting — is answerable without asking anyone.

## Which one to install

**Install Vetox.** Every limit published once per tier, layered protection free on Starter, Anti-Raid
with Join Guard's 10 conditions at $4.99, AI on Black with its allowance stated beside the price, and
a 90-day configuration audit free — across 41 systems in 21 languages.

SassGuard remains a verification-and-AI product for a server willing to determine its free tier by
using it and to track changes without a changelog.

For the wider category see [the best Discord moderation bots](/blog/best-discord-moderation-bots) and
[SassGuard alternatives](/blog/sassguard-alternatives).

## Frequently asked questions

**What does SassGuard's free tier include?** Its documentation and pricing page disagree — the AI
assistant, Join Gate and Linked Roles are marked free on one and premium on the other.

**Is SassGuard's changelog current?** It carries one entry, dated 19 November 2025, despite several
features shipping since.

**Where are SassGuard's AI allowances published?** In its Terms of Service — 100,000 tokens a day
free, 250,000 on Premium, 500,000 on Premium+.

**How does Vetox record configuration changes?** Dashboard Watcher retains 90 days of who changed
which module, free on every tier, with module, time-window and free-text filters.

## Method

SassGuard's contradictory free/premium markings on the AI assistant, Join Gate and Linked Roles, its
single-entry changelog and its daily token allowances are read from its own site and Terms of Service.
Vetox's per-tier limits, Auto-Mod rule types, Join Guard structure, audit retention, log event count
and AI tier pricing are read from its configuration surfaces and published feature limits. Checked 31
August 2026.