Why we built PixelShield

2026-02-15 · 5 min read

The problem

If you've ever run a Minecraft server, you know DDoS attacks aren't a matter of "if" but "when." The bigger your community grows, the more you become a target. And the solutions available today? They're built for websites, not game servers.

Generic DDoS protection services sit in front of your server and filter traffic based on volume and rate patterns. That works for HTTP. It doesn't work for Minecraft — or any game protocol, really.

A bot joining your Java server looks like a legitimate TCP connection. A RakNet flood targeting your Bedrock server uses the same UDP port as real players. Without understanding the protocol, you can't tell attacks from players.

Protocol-aware filtering

We built PixelShield to understand game protocols at the packet level. For Java Edition, we parse the full handshake, login, and play flow and validate every field. For Bedrock, we implement the RakNet state machine and track sessions. For Geyser, we run both parsers on the same port.

This means we can catch attacks that generic solutions miss: bot tools that send valid-looking TCP connections, amplification attacks using RakNet's unconnected pong, and slow-drip attacks that stay under rate limits but flood your login handler.

Kernel-level performance

Filtering at the application level means the attack traffic already hit your server's network stack. We use XDP (eXpress Data Path) with eBPF to drop malicious packets at the kernel level — before they ever reach userspace. On our edge nodes, known-bad traffic never even makes it to the proxy process.

The result: sub-millisecond filtering overhead, even under heavy attack. Your players don't notice any latency difference.

Built with Rust

The entire proxy is written in Rust. The protocol parsers, the filter engine, the load balancer, the health checker — all Rust. This gives us memory safety guarantees, fearless concurrency with Tokio, and zero-cost abstractions for the hot path.

We use ArcSwap for lock-free config hot-reload (no downtime when you change settings), DashMap for concurrent session tables, and SO_REUSEPORT for zero-downtime binary upgrades.

What's next

We're expanding our edge network, adding more attack detection heuristics, and building deeper analytics. If you're running a game server and want protection that actually understands your traffic, give PixelShield a try. The free tier covers most small servers, and there's no credit card required.