Nodyx

"The network is the people."

The self-hosted community platform you actually own.
Forum + Chat + Voice + P2P + Homepage Builder + Widget SDK — one server, one community, forever.

_{⭐ If Nodyx resonates with you, a star helps others find it — and keeps us going.}

Why Nodyx

• Discord locks communities inside a private platform — your 10 years of history vanish if they close or ban you
• Forums are slow and fragmented — no voice, no real-time, invisible to your members' daily workflow
• Self-hosted tools rarely combine chat + voice + searchable knowledge in a single install — and none let you build your own homepage

Nodyx brings them together. One command. Your server. Forever.

The internet broke something.

Discord, Facebook, Slack — they didn't build communities. They captured them.

Ten years of discussions. Tutorials. Collective knowledge. Memories. Locked in silos. Invisible to search engines. Gone when the platform decides.

You never owned any of it.

Nodyx gives it back.

One command. Your server. Your rules. Your community — permanently.

curl -fsSL https://nodyx.org/install.sh | bash

Works on a Raspberry Pi behind a home router. No domain. No open ports. No cloud account.

What makes Nodyx different

The only platform with all of this in a single install

Nodyx is the only self-hosted platform combining an indexed forum, real-time chat, P2P voice, collaborative canvas, a federated directory, and a fully extensible homepage in a single install.

Homepage Builder + Widget SDK

Nodyx ships with a drag-and-drop Homepage Builder and a complete Widget SDK — two features that no other self-hosted community platform offers.

11 layout zones

Place widgets anywhere on your homepage. Positions include:

banner          → full-width top announcement strip
hero            → main hero section
stats-bar       → community counters (members, online, posts)
main            → above main content
sidebar         → right column (join card, etc.)
half-1 / half-2 → 2-column grid
trio-1/2/3      → 3-column grid
footer-1/2/3    → footer columns
footer-bar      → full-width footer strip

4 native widgets (Phase 1)

Widget Store — install in one click

Any developer can package a widget as a .zip and install it on any Nodyx instance:

my-widget-1.0.0.zip
├── manifest.json     ← id, label, version, schema (config fields)
└── widget.iife.js    ← Web Component — Shadow DOM isolated

The admin panel handles upload, validation, extraction and activation. No rebuild, no deploy.

Widget SDK — build your own, zero build tools

Widgets are standard Custom Elements (Web Components). Plain JavaScript, no React, no Vue, no npm.

class MyWidget extends HTMLElement {
  connectedCallback() { this._render() }

  _render() {
    var cfg = JSON.parse(this.dataset.config || '{}')
    if (!this.shadowRoot) this.attachShadow({ mode: 'open' })
    this.shadowRoot.innerHTML = `<div>Hello ${cfg.title}</div>`
  }
}
customElements.define('nodyx-widget-my-widget', MyWidget)

→ Full step-by-step guide for non-developers → nodyx.dev/create-widget

The P2P Stack — 100% handwritten Rust

This is where Nodyx goes further than anyone else.

nodyx-turn — Rust STUN/TURN server (replaces coturn)

coturn is the industry standard — a mature C server used by Signal, Jitsi, Matrix. We replaced it with a 2.9MB Rust binary that does exactly what Nodyx needs. Nothing more.

RFC 5389 (STUN) + RFC 5766 (TURN) + RFC 6062 (TURN-over-TCP)
HMAC-SHA1 time-based credentials (username={expires}:{userId})
MESSAGE-INTEGRITY on all responses (RFC 5389 §10.3) — Firefox/Chrome compliant
Rate limiting + allocation quotas (MAX_LIFETIME=300s) + ban map
tokio async runtime — UDP:3478 + TCP:3478 (VPN/firewall bypass)
Zero coturn dependency on production

nodyx-relay — Rust P2P TCP tunnel (no domain, no open ports)

A Raspberry Pi under your desk. No domain. No router port forwarding. No Cloudflare account. Run Nodyx anyway.

nodyx-relay server  →  listens TCP:7443 + HTTP:7001
nodyx-relay client  →  persistent TCP tunnel → exposes local port 80

• Automatic reconnection with exponential backoff (1s → 30s max)
• JWT authentication per instance
• Routing by slug: yourclub.nodyx.org → proxied to the Pi behind your router
• Validated on a real Raspberry Pi 4 with zero open ports ✅

WebRTC DataChannels — P2P without the server

Messages between peers that never touch the server.

• Instant typing indicators — < 5ms local latency (vs 80–200ms via server)
• Optimistic emoji reactions — appear instantly, server confirms in background
• P2P file transfer — assets shared directly between peers
• Graceful fallback — if DataChannel unavailable (strict NAT), Socket.IO takes over transparently

NodyxCanvas — Collaborative P2P whiteboard

Draw together in real time. Synchronized via existing DataChannels. No server touches the data. Session-only by default.

CRDT Last-Write-Wins per element (UUID + timestamp)
canvas:op / canvas:clear / canvas:cursor  →  P2P DataChannels
Voice-aware cursors: peer cursor pulses when they're speaking
PNG export (browser-native) + text recap posted to chat channel

Screenshots

Community Home	Forum
Real-time Chat	Voice Channels — WebRTC P2P
Admin Panel	Instance Directory

Quick Start

Prerequisites

The installer handles everything automatically. Your system only needs curl and git to get started.

# Ubuntu / Debian
apt-get install -y git curl

One-click install

curl -fsSL https://nodyx.org/install.sh | bash

Or clone first:

git clone https://github.com/Pokled/Nodyx.git && cd Nodyx && sudo bash install.sh

The installer offers three network modes:

Nodyx Relay is the recommended default — works on a Raspberry Pi behind a home router. No domain. No port forwarding. No cloud account. Just run the script.

Installs automatically: Node.js, PostgreSQL, Redis, nodyx-turn (Rust STUN/TURN), Caddy (HTTPS), PM2. Generates secrets, bootstraps the database, creates your admin account. No manual configuration.

Supported: Ubuntu 22.04 / 24.04, Debian 11 / 12 / 13.

→ Complete installation guide (EN)
→ Guide d'installation complet (FR)

Updating an existing instance

cd /var/www/nexus && git pull && \
  cd nodyx-core && npm run build && sudo -u nodyx pm2 restart nodyx-core && \
  cd ../nodyx-frontend && npm run build && sudo -u nodyx pm2 restart nodyx-frontend

Database migrations are applied automatically on startup — no manual SQL needed.

Architecture

┌─────────────────────────────────────────────────────────────┐
│                        Your Browser                         │
└──────────────┬──────────────────────────────┬───────────────┘
               │ HTTP / WebSocket             │ WebRTC P2P
               ▼                             ▼
┌──────────────────────────┐    ┌────────────────────────────┐
│   nodyx-core (Fastify)   │    │  Direct peer connection    │
│   nodyx-frontend (Svelte)│    │  DataChannels + Canvas     │
│   PostgreSQL + Redis     │    │  Voice + Screen share      │
└──────────────────────────┘    └────────────────────────────┘
               │                             │
        ┌──────┴──────┐               ┌──────┴──────┐
        │ nodyx-relay │               │ nodyx-turn  │
        │ (Rust TCP)  │               │ (Rust TURN) │
        │ home server │               │ NAT bypass  │
        └─────────────┘               └─────────────┘

What's built. What's coming.

Coming

The Vision

Nodyx is not a Discord alternative.

It is a different answer to a different question.

Discord asked: "How do we grow fast and capture communities?"
Nodyx asks: "How do we give communities sovereignty over their own existence?"

Every Nodyx instance is a sovereign node. It runs where you run it — a VPS, a Pi, a spare laptop. It stores what you choose to store. It shares what you choose to share. It shuts down when you decide — not when a company pivots.

The internet was decentralized by design. SMTP, IRC, NNTP — anyone could run a server and talk to anyone else's server. That was the promise. Big Tech centralized it into silos over two decades.

Nodyx is the promise, kept.

And it spreads the same way. Each instance that goes live exposes others to the idea. Each public event indexed by Google brings in someone new. Each community that chooses sovereignty inspires another.

"Fork us if we betray you." — AGPL-3.0

Documentation

Language	Docs
English	nodyx.dev · docs/en/
Français	docs/fr/
Español	coming soon
Deutsch	coming soon

• nodyx.dev — Full documentation wiki
• Create a Widget — Step-by-step Widget SDK guide
• Manifesto — Why Nodyx exists
• Architecture — How it's built
• Roadmap — Where we're going
• Audio Engine — Broadcast EQ, RNNoise, full audio chain
• Neural Engine — Local AI with Ollama
• NODYX-ETHER — The physical layer vision (LoRa / HF radio / ionosphere)

Contributing

Nodyx belongs to its community.

1. Browse open Issues or open a Discussion
2. Read CONTRIBUTING.md before opening a PR
3. Commits follow Conventional Commits, written in English

Contribute freely — no prior validation required:

docs/        →  improve or translate documentation
docs/ideas/  →  design thinking, UX proposals, new ideas

The core (nodyx-core/src/) requires discussion first — open an Issue.

License

AGPL-3.0 — The strongest open source license for networked software.

If you use Nodyx, even over a network, your modifications must be open source. If Nodyx ever betrays its principles, this license lets anyone fork it and continue in the spirit of the Manifesto.