Nerds IncorporatedNOCOM network operations
--:--:-- LDN CONNECTING Staff access
CORELINKING DEPLOYMENTS-- CONTROLLED ENVIRONMENTS-- ACTIVE SESSIONS-- SYNCWAITING

NERDS INCORPORATED

About Nerds Incorporated

We build and operate infrastructure, moderation systems and safeguarding workflows for online communities.

Focus
Community operations & safeguarding
Model
Human-led, system-supported
Public data
Aggregate operational state

THE ORGANISATION

One operational layer behind the communities we support.

Community safety breaks down when reports, evidence and moderation history live in separate places. Nerds Incorporated reduces that fragmentation by connecting the systems staff use to review incidents, coordinate action and keep services running.

We do not replace human judgement. Our systems give authorised teams better context, a clearer audit trail and a more reliable way to act when harmful behaviour or operational problems appear.

WHAT WE DO

Core areas of work

Each area supports the same goal: make community operations safer, more consistent and easier to review.

01
SAFEGUARDING

Identify and contain bad actors

Staff can review reports alongside relevant history, connect repeat patterns across managed environments and preserve evidence needed for proportionate action.

  • Structured reports
  • Cross-environment context
  • Evidence preservation
02
MODERATION OPERATIONS

Make enforcement accountable

Actions, quarantines, incident ownership and staff handovers can be recorded consistently rather than depending on scattered messages or individual memory.

  • Central action history
  • Incident coordination
  • Reviewable decisions
03
INFRASTRUCTURE

Keep supported systems available

Regional deployments, databases, monitoring and recovery workflows support the services that community teams rely on every day.

  • Regional deployments
  • Service health
  • Recovery workflows
04
INCIDENT RESPONSE

Give incidents a clear owner

During an active incident, staff can work from a shared picture of impact, containment, evidence and remaining actions.

  • Containment tracking
  • Operational ownership
  • Post-incident review

TRUST & SAFETY

How safeguarding work is handled

A report is not treated as a conclusion. Staff review available context and records before consequential action is taken. Sensitive case information remains inside restricted systems.

When a matter goes beyond community moderation, the appropriate route may include a platform safety team or relevant authority. Nerds supports the operational handoff; it does not replace those organisations.

  1. 01
    Receive

    Bring reports and relevant signals into a controlled review process.

  2. 02
    Verify

    Review context, history and corroborating records before reaching conclusions.

  3. 03
    Contain

    Apply proportionate restrictions where needed to reduce immediate risk.

  4. 04
    Preserve

    Retain evidence and decision history for accountability and later review.

  5. 05
    Escalate

    Refer matters to appropriate external channels when community moderation is not enough.

OPERATING PRINCIPLES

How we expect the organisation to work

Evidence before assumption

Records should inform decisions without manufacturing certainty.

Proportionate action

Controls should match the risk and remain reviewable.

Privacy by default

Sensitive material belongs inside restricted systems.

Auditability

Important actions should leave a clear operational record.

Human responsibility

Automation supports staff; accountability remains human.