NEXUS_SIGNING_KEY.
Why Nexus Core?
Single Connection Pool
Every Spigot server used to maintain its own MongoDB connection pool. Nexus Core replaces all of them with a single, optimized pool.
Consistent Cache
Per-server caches go stale and diverge. Nexus Core provides a centralized Redis cache that is always consistent across every node.
Centralized Data Logic
Business rules defined once in a DataAddon are shared everywhere. No more duplicating logic across every server’s codebase.
How It Works
1
Spigot servers publish signed packets to Redis
Each game server constructs a JSON packet with the request type, payload, and HMAC-SHA256 security fields, then publishes it to the shared Redis channel.
2
Nexus Core validates and routes the packet
Nexus Core verifies the signature, timestamp, and nonce, then looks up the matching DataAddon in its registry.
3
Data is served from Redis or MongoDB
The addon checks the Redis L2 cache first. On a cache miss, it queries MongoDB and writes the result back to cache.
4
Signed response published back to the source server
The result is serialized, signed with
NEXUS_SIGNING_KEY, and published to the originating server’s Redis channel.Explore the Docs
Installation
Build Nexus Core from source and launch the web panel.
Quickstart
Register your first DataAddon and send a signed request in minutes.
System Architecture
Understand the hub-and-spoke design connecting Spigot servers, Redis, and MongoDB.
Security
Full symmetric HMAC signing on inbound and outbound packets as of v1.5.1.