Skip to content

FedShield

Cross-studio player reputation, without a central authority.

A federated backend that lets independently operated game servers exchange player reputation data through a common protocol. No central authority holds the record. Studios stay in control of their own enforcement; FedShield only returns advisory scores.

A ban in one game means nothing in another today. Each studio keeps its moderation data in a silo, throwing away the collective signal every other studio has produced about the same player. FedShield closes that loop.

Backend engineers

Self-host the Federation Core, register your server as a peer, start submitting trust events. The API surface is small and boring on purpose.

System architects

Federate with other studios in your trust group. Choose between Privacy-First and High-Security identity modes per group. No global authority required.

Security teams

Augment an existing anti-cheat stack with cross-game reputation signals. Verdicts are advisory; your enforcement policy stays in your code.

Open source contributors

The Federation Core is Go 1.22, PostgreSQL 16, Redis 7. No magic, no enterprise gating, no licence fees. PRs welcome.

  1. Register your game server as a peer. One HTTP call, one API key.
  2. Submit trust events as players misbehave (or get reported, banned, commended).
  3. Query a player’s trust score from any peer in the same federation group.
  4. Apply your own enforcement policy. FedShield never bans anyone for you. It just gives you the collective signal.

The trust score is a Bayesian Beta with exponential time decay, peer-weighted via an EigenTrust-inspired aggregation that resists Sybil attacks. Same player, same federation, same score — across studios.

How FedShield works

The three-layer architecture, the scoring formula, the federation model. Read the overview →

API reference

Every endpoint, every parameter, every response shape. Try requests in your browser. Open the reference →

Self-host

Docker compose for PostgreSQL, Redis, and the Federation Core binary. Self-host guide →