GHOST DEVELOPERANDROID DEVELOPER
Back to projects
Tools

Ghost Nexora Bot

WhatsApp automation ecosystem with commands, sub-bots, management and a web dashboard.

Website temporarily offlineView source code

Based on a real GitHub project. Features can change during development.

GB / GHOST DEVELOPER
01 / OVERVIEW

What does it do?

Multi-platform community automation, moderation, sub-bots and utility bot.

WhatsApp automation ecosystem with commands, sub-bots, management and a web dashboard.

02 / CAPABILITIES

Key capabilities

  • Baileys and Node.js messaging backend.
  • Moderation, utilities and sub-bots.
  • Next.js and TypeScript dashboard.
  • Self-hosted VPS infrastructure.
03 / MY ROLE

Engineering focus

Full-stack, bots, integration and operations.

TECHNICAL DETAILS

How it is built

Architecture, implementation choices and the current state of the project.

Previously ran on a private VPS · currently offline
01CHALLENGE

What problem does it address?

Organize community automation into a bot supporting multiple platforms and deployment modes without coupling command logic to the dashboard or optional services.

02ARCHITECTURE

Architecture and boundaries

01
Bot runtime

Node.js/TypeScript, Baileys, a WhatsApp session, command routing, moderation and separate service modules.

02
Platform adapters

Normalized-message contracts and a WhatsApp adapter; the repository also contains Telegram/Discord integrations in V2 work.

03
Management and operations

Next.js dashboard, control API, delivery mechanisms and VPS/Termux modes; an optional, configurable local LLM.

03TRADE-OFFS

Engineering decisions

  • Separate platform adapters from shared logic to reduce direct dependency on WhatsApp message formats.
  • Keep bot, web dashboard and Ollama optional so installations need not run the entire stack.
  • Control and update operations have documented boundaries, validation and persistent-state recovery procedures.
04VERIFICATION

How it is checked

  • CI configures Node.js, dependency auditing, typechecking, a build and multiple feature-specific smoke checks.
  • Dedicated smoke checks cover permissions, localization, moderation, updates and web regressions.
  • The V2 release document requires signing, artifact integrity, upgrade/rollback tests and a 72-hour soak before publication.
05LIMITATIONS

Current status and next steps

  • The bot was previously deployed and used on its owner’s VPS, as reported by the developer. Its V2 evolution has separate release qualification gates.
  • The previous VPS subscription expired. The service and website can return once a new server is provisioned and configured.
  • Screenshots and historical operating metrics have not yet been published, so no unmeasured statistics are claimed.
Back to projects