Chat, friends and safety in one service
Herald gives your game channels, direct messages, friends, invites and presence, and ships with the trust-and-safety tools a live game is expected to have. One service to run. One SDK call to join a channel.
Every social feature your game needs
You describe your channels. Herald runs them.
Chat
Channel classes
Define a kind of channel once (world, guild, party, trade) and create as many as you like.
Four ways to join
auto, managed by your server, selfJoin, or dm. Pick one per class.
Direct messages
One-to-one and small-group conversations, with block and mute respected.
Exclusive channels
A player is in one party at a time. Joining the next one leaves the last.
Roles
Owner, officer, member, or your own. Each role says who can speak, invite and kick.
Limits and filters
Rate limits, message size limits and word filters, set per class.
Friends and presence
Friends
Requests, accepts and a friend list that follows the player across devices.
Block and mute
Applied everywhere at once: channels, direct messages and invites.
Follow
One-way follows for streamers, guild leaders and rivals.
Invites
Typed invites that expire: party, guild, trade, duel. Your rules decide who may send one.
Presence
Online, away, in a dungeon. Add your own attributes, such as zone and level.
Accounts and characters
One account, many characters. Herald never needs to know who the player is.
Platform
Many games, one install
Each game is a tenant with its own data, settings and limits.
Server API
Your game server creates channels, moves players and posts system messages.
Events and webhooks
Joins, reports, sanctions and flags arrive in your backend as they happen.
SDKs
C++, C#, Java and TypeScript, generated from one schema.
Binary protocol
Versioned, compact frames over WebSocket. No JSON on the hot path.
Standby takeover
A standby instance takes over a game when its active instance stops.
A guild chat in a dozen lines
{
"class": "guild",
"membership": "managed",
"maxMembers": 500,
"roles": ["owner", "officer", "member"],
"rate": { "messages": 10, "per": "10s" },
"maxBytes": 512,
"filters": ["profanity"],
"safety": { "classifier": "wardstone" }
}
herald::Client herald(url, token); auto guild = herald.join("guild", "crimson-order"); guild.onMessage([&](const herald::Message& m) { chat.append(m.from, m.text); }); guild.send("Raid at nine?"); herald.friends().request(playerId); herald.presence().set({.zone = "Ashen Vale", .level = 42}); herald.report(messageId, herald::Reason::Harassment);
Eight safety tools, on from day one
From the report button to the transparency report. A classifier never sanctions a player on its own: a person decides.
Report and mute
Players report a message or a person and mute them on the spot.
Evidence store
A report snapshots the conversation at that moment. Nothing else is kept.
Sanctions and strikes
Warn, mute, suspend, ban. Strikes add up and expire by your rules.
Moderator console
Cases, queues, decisions and appeals in one place.
Classifiers and risk
Wardstone reads small private conversations and ranks who needs a look.
Age assurance
Safe defaults by age group. Direct messages with minors are always checked.
Child-safety escalation
A dedicated path for the worst cases, with reporting to NCMEC.
Transparency and audit
Every decision is logged. The numbers for your transparency report are ready.
Wardstone: grooming detection
Wardstone reads private chat as it happens and sends the few users worth reviewing, with evidence, to your moderators. It never blocks or delays a message.
Private by design
- Messages are never storedChat is relayed in memory. Only a report keeps a snapshot, as evidence.
- A person makes every decisionA classifier flag opens a case. It never mutes or bans by itself.
- No player identity neededPlayers are opaque ids from your game. Herald holds no names or emails.
- Nothing extra to operateNo Redis, no Postgres, no etcd. Herald keeps its state in Rune.
Give your players a place to talk
Herald runs beside your game servers and shares their Rune cluster.