01
Discord Runtime
The persistent bot process handles events, commands, guild state, member state, voice state, and interaction traffic.
DISCORD ON THE FRONT.
NEXUS UNDER THE HOOD.
The website, Discord runtime, module storage, and Nexus are separate surfaces using the same operating model. That is why public proof can be real instead of a marketing counter somebody typed into the homepage.
02
PickleHead Modules
Guardian, tickets, onboarding, Components V2, forms, applications, webhooks, emojis, commands, and automations.
03
Operational Data
Live public telemetry plus private storage for applications, tickets, evidence, aliases, manifests, templates, and audit events.
04
Nexus
The management surface that turns runtime and storage into something owners and staff can actually operate.
THE DATA PATH
ONE EVENT. EVERY SURFACE UPDATED.
Discord eventMember, interaction, command, webhook
→PickleHead runtimeRules, modules, actions
→Storage & auditOperational record
→NexusVisible to staff
PUBLIC PROOF ENDPOINT
IF THE BOT STOPS REPORTING, THE SITE SAYS SO.
Only aggregate runtime information is exposed publicly. Guild names, IDs, member lists, tokens, and private operations stay private.
/api/public/live-stats