Skip to content

NeXuS Cloud Vision

Meeting Cloud Services Head-On and Towering Over Them

The Mission: Deliver ALL the benefits of cloud computing with NONE of the surveillance.


The Problem with "The Cloud"

Traditional Cloud:
Your Device → ISP (sees you) → Cloud Provider (sees EVERYTHING) → Internet

What they collect:
- Real identity (credit card, KYC)
- IP address (location tracking)
- All your traffic (deep packet inspection)
- Usage patterns (behavioral profiling)
- Data at rest (stored on their disks)
- Metadata (who, when, where, what)

You trade privacy for convenience.


The NeXuS Alternative

NeXuS Mesh Cloud:
Your Device → NeXuS Mesh → Your Remote Services → Darknet → Internet

What you keep:
✅ Privacy (encrypted mesh routing)
✅ Anonymity (no KYC, mesh addresses)
✅ Sovereignty (your hardware, your rules)
✅ Freedom (open source, no vendor lock-in)

What you gain:
✅ Remote compute (powerful servers)
✅ Anywhere access (phone, tablet, laptop)
✅ 24/7 availability (always-on services)
✅ Distributed storage (I2P, Reticulum)
✅ Mesh networking (Yggdrasil, B.A.T.M.A.N.)

You keep privacy AND gain power.


NeXuS Cloud Services Stack

Layer 1: Mesh Transport

Tor          → Anonymous routing
I2P          → Distributed storage + messaging
Yggdrasil    → End-to-end encrypted mesh (IPv6)
B.A.T.M.A.N. → Ad-hoc mesh networking
Reticulum    → Off-grid packet radio mesh

Result: Global mesh network, no central authority, encrypted by default.

Layer 2: Remote Compute

Remote Browser  → VPS/Home Server runs browser
                → Your device = display only
                → JavaScript exploits contained
                → Heavy sites = server problem

Remote Desktop  → Full desktop on remote server
                → SSH/VNC tunneled through mesh
                → Zero local processing

Distributed Jobs→ Spread compute across mesh nodes
                → Tor circuits balance load
                → B.A.T.M.A.N. mesh routing

Result: Thin client experience, powerful remote compute, privacy preserved.

Layer 3: Distributed Storage

I2P Distributed Hash Table → Encrypted file storage
Reticulum Packet Bundles   → Off-grid data sync
Tor Hidden Services        → Private file servers
IPFS over I2P/Tor          → Content-addressed storage

Result: Your data, your control, distributed across mesh, encrypted.

Layer 4: Self-Hosted Services

Nextcloud     → File sync (Dropbox alternative)
Jitsi Meet    → Video conferencing (Zoom alternative)
Matrix        → Messaging (Slack/Discord alternative)
Gitea         → Code hosting (GitHub alternative)
Jellyfin      → Media streaming (Netflix alternative)
Mastodon      → Social media (Twitter alternative)

All accessible via:
- Tor .onion addresses
- I2P .i2p addresses
- Yggdrasil IPv6 addresses

Result: Cloud app features, self-hosted privacy, mesh-networked.

Layer 5: Service Discovery

NeXuS Directory → Decentralized service registry
I2P Addressbook → .i2p name resolution
GNS (GNU Name System) → Yggdrasil name resolution
Tor OnionBalance → Load balancing across hidden services

Result: Find services on mesh without central DNS.


Use Cases: NeXuS Cloud in Action

1. Remote Browser (Already Implemented)

Phone (at coffee shop)
  ↓ SSH tunnel
Home Server (running Mullvad Browser in Cage)
  ↓ NeXuS proxy
Tor/I2P mesh
Internet (fully anonymous)

Benefits:
- Coffee shop WiFi sees encrypted SSH only
- Browser fingerprint = server, not your phone
- Heavy sites render on home server CPU
- Close laptop, continue on phone (session persistence)

2. Distributed File Storage

Upload file to NeXuS cloud:
1. File encrypted locally (your key)
2. Split into chunks (erasure coding)
3. Distributed across I2P nodes
4. Tor hidden service serves chunks
5. Yggdrasil mesh provides global routing

Result:
- No single server has your full file
- Encrypted in transit AND at rest
- Accessible from anywhere via mesh
- Survives node failures (redundancy)

3. Mesh Video Conferencing

Jitsi Meet on Tor hidden service:
- Each participant connects via Tor
- Server sees Tor exit nodes, not real IPs
- Optional: I2P routing for extra hops
- Yggdrasil mesh for direct peer connections

Result:
- Private video calls, no corporate surveillance
- No phone numbers, no email, no KYC
- Works globally via mesh routing

4. Off-Grid Messaging

Reticulum + Meshtastic radio network:
- Messages route via LoRa radio mesh
- No internet required
- Encrypted end-to-end
- Store-and-forward (delay tolerant)

Result:
- Communication survives internet outages
- No ISP, no monitoring, no shutdown
- Physical mesh network

NeXuS Cloud vs Traditional Cloud

Feature Traditional Cloud NeXuS Mesh Cloud
Remote Compute ✅ AWS/Azure/GCP ✅ Your VPS/Home Server
Anywhere Access ✅ Internet connection ✅ Mesh routing (Tor/I2P/Ygg)
Storage ✅ S3/Drive/Dropbox ✅ I2P DHT/Nextcloud
Services ✅ SaaS apps ✅ Self-hosted alternatives
Privacy ❌ Complete surveillance ✅ Encrypted by default
Anonymity ❌ KYC required ✅ Mesh addresses, no KYC
Sovereignty ❌ Vendor lock-in ✅ Your hardware, your rules
Censorship Resistance ❌ Can be shut down ✅ Decentralized mesh
Cost 💰 Subscription fees 💰 One-time hardware/VPS

Implementation Roadmap

Phase 1: Remote Browser ✅ (COMPLETED)

  • Mullvad Browser + Cage setup
  • NeXuS smart routing (Tor/I2P)
  • CLI-first launch script
  • Remote browser documentation

Phase 2: Distributed Storage (NEXT)

  • I2P distributed hash table integration
  • Nextcloud over Tor hidden service
  • IPFS gateway through I2P/Tor
  • Reticulum file sync for off-grid

Phase 3: Self-Hosted Services

  • Matrix homeserver (I2P + Tor addresses)
  • Jitsi Meet hidden service
  • Gitea code hosting on mesh
  • Jellyfin media server (personal Netflix)

Phase 4: Mesh Service Discovery

  • NeXuS directory service (decentralized registry)
  • I2P addressbook integration
  • Yggdrasil GNS name resolution
  • Service health monitoring across mesh

Phase 5: Advanced Features

  • Load balancing across mesh nodes
  • Distributed compute jobs (BOINC-style)
  • Mesh CDN (content distribution)
  • Tor/I2P bridge nodes for entry/exit

Architecture: NeXuS Cloud Node

┌─────────────────────────────────────────────────┐
│           NeXuS Cloud Node (VPS/Home)           │
├─────────────────────────────────────────────────┤
│                                                 │
│  Services Layer:                                │
│  ┌────────────┬────────────┬──────────────┐    │
│  │ Mullvad    │ Nextcloud  │ Jitsi Meet   │    │
│  │ Browser    │ (Storage)  │ (Video)      │    │
│  └────────────┴────────────┴──────────────┘    │
│         ↓             ↓            ↓            │
│  ┌──────────────────────────────────────────┐  │
│  │      NeXuS Proxy Layer (Privoxy)         │  │
│  │   Smart Routing: .i2p → I2P, rest → Tor │  │
│  └──────────────────────────────────────────┘  │
│         ↓             ↓            ↓            │
│  ┌──────────┬──────────┬──────────┬─────────┐ │
│  │ Tor x3   │ I2P      │Yggdrasil │B.A.T.M.A.N│ │
│  │ (Medusa) │          │          │          │ │
│  └──────────┴──────────┴──────────┴─────────┘ │
│         ↓             ↓            ↓        ↓  │
│  ┌──────────────────────────────────────────┐  │
│  │         Network Interface (eth0)         │  │
│  └──────────────────────────────────────────┘  │
│                      ↓                          │
└─────────────────────────────────────────────────┘
              Internet / Mesh

Access from Any Device

Laptop (CLI-first)
  → SSH to NeXuS node
  → Launch services via tmux
  → VNC to remote browser

Phone (Termux + SSH)
  → SSH to NeXuS node
  → tmux attach
  → Access same browser session

Tablet (Tor Browser)
  → Connect to .onion address
  → Access Nextcloud/Jitsi
  → Web-based interface

All devices:
  → Same services, same data
  → Synchronized state
  → Private mesh routing
  → No corporate surveillance

Why NeXuS Towers Over Cloud Services

1. Privacy by Architecture

Cloud: Your data passes through their servers unencrypted (to them). NeXuS: Encrypted mesh routing, they can't decrypt even if they wanted to.

2. No Vendor Lock-In

Cloud: Move providers? Lose everything, rebuild from scratch. NeXuS: Open protocols, self-hosted, take your data anywhere.

3. Censorship Resistant

Cloud: Government orders? Your service gets shut down. NeXuS: Decentralized mesh, no single point of failure.

4. True Anonymity

Cloud: KYC, credit card, real identity required. NeXuS: Mesh addresses, cryptocurrency payment (if VPS), no personal info.

5. Sovereignty

Cloud: Their hardware, their rules, their terms of service. NeXuS: Your hardware (or trusted VPS), your rules, open source.

6. Cost Effective

Cloud: Monthly subscriptions forever ($50-500/month). NeXuS: One-time VPS ($5/month) or home server (one-time cost).


The Future: NeXuS Mesh Federation

Vision: Thousands of NeXuS nodes forming a global mesh cloud.

Mesh Cloud Architecture:
- Users run NeXuS nodes (home servers, VPS, etc.)
- Nodes discover each other via Yggdrasil/I2P
- Services federate (like email, Matrix, Mastodon)
- Users access ANY node's services via mesh
- Load balanced automatically across nodes
- Redundancy through distributed storage

Result:
- Cloud-level performance
- Better than cloud privacy
- Decentralized architecture
- Community owned
- Censorship impossible

Example:

Alice (USA) → NeXuS node in Iceland → Tor → I2P → Bob's file (Japan)
Charlie (UK) → NeXuS node at home → Yggdrasil → Jitsi (Germany)
Dave (Brazil) → NeXuS VPS (Singapore) → B.A.T.M.A.N. → Matrix (Canada)

All connected via mesh, all private, all sovereign.


Getting Started Today

Minimal NeXuS Cloud Setup

Step 1: Deploy NeXuS Stack

# Already done! You have:
- 3x Tor instances (Medusa load balancing)
- I2P router
- Yggdrasil mesh
- B.A.T.M.A.N. Advanced
- Smart routing (Privoxy)
- DNS privacy (DNSCrypt-Proxy)

Step 2: Add Remote Browser

# Run the setup (already created):
./mullvad-browser-setup.sh
./mullvad-browser-cli.sh

# Now accessible from anywhere via SSH

Step 3: Self-Host First Service

# Pick one:
- Nextcloud (file storage)
- Jitsi Meet (video calls)
- Matrix (messaging)

# Deploy as Tor hidden service
# Access via .onion address
# Route through NeXuS mesh

Step 4: Mobile Access

# Install Termux on phone
# SSH to your NeXuS node
# Use same services
# Full mesh cloud on mobile


NeXuS Cloud Principles

  1. Privacy by Default Encrypted routing is not optional, it's the only way.

  2. Decentralization First No single point of failure, mesh architecture always.

  3. Open Source Everything Community can audit, verify, trust.

  4. Self-Sovereignty Your hardware, your data, your rules.

  5. Accessible to All CLI-first for experts, web interface for everyone.

  6. Censorship Resistance Cannot be shut down, cannot be blocked.

  7. Community Powered Together Everyone Achieves More.


The Mission

Traditional cloud services make you choose: - Convenience OR privacy - Features OR freedom - Performance OR sovereignty

NeXuS delivers ALL of them: - Convenience AND privacy - Features AND freedom - Performance AND sovereignty

We don't compete with the cloud. We tower over it. 🌀


🌀 Together Everyone Achieves More 🌀

The cloud wanted your data. NeXuS gives you power.

The cloud wanted surveillance. NeXuS delivers privacy.

The cloud wanted control. NeXuS brings freedom.

Welcome to the NeXuS Mesh Cloud. Where your device is a smart screen, Your compute is sovereign, And the mesh network is unstoppable.


Next Steps: See NEXUS_CLOUD_ROADMAP.md for implementation plan