Three phases · public direction

First dependable. Then yours.

The roadmap moves from a reliable everyday product to community self-hosting and optional community-run capacity.

Targets, not contracts · status must be verified before public launch

Stable for daily use.

PHASE 01 · IN PROGRESS

A product you recommend without qualification.

Web, Windows, Linux, and mobile surfaces; reliable voice/video/screen sharing; passkeys and QR login; recovery; moderation; profiles; notifications; update safety; and daily-use polish.

Exit direction

  • No unresolved critical public bugs.
  • At least 99.5% crash-free operation over seven consecutive days.
  • Sustained daily use and meaningful in-app review volume.
  • Public Android testing and opt-in crash reporting.

Own your community server.

PHASE 02 · PLANNED

Run NOX on a PC, VPS, or Raspberry Pi.

The same NOX client connects to operator-hosted and self-hosted communities. LAN mode works locally; internet mode uses tunneling without requiring home-router expertise.

  • One-click cross-platform installers.
  • Admin dashboard, backups, moderation, and server migration.
  • Signal Protocol for DMs and MLS planned for community messages.
  • Central abuse reporting that local hosts cannot suppress.

Host for others.

PHASE 03 · PLANNED

Turn spare capacity into nearby infrastructure.

Optional rental of bandwidth, relay, and storage capacity, supported by public host reputation, NOX-level enforcement, and a clear payment split.

  • Regional latency and local alternatives to central hosting.
  • Target marketplace fee of 5–10%.
  • Prepaid bandwidth and GB-month storage concepts.
  • Requires Phase 2 encryption and enforcement first.

Commitments across every phase.

  • No advertisements or sold user data.
  • Normal personal use remains free.
  • Any future paid offer sells capacity, not today’s features.
  • No dark-pattern lock-in; shutdown must include export and migration time.
  • No pivot away from the privacy and community values that started NOX.