# Wonek

> Wonek (by Arte Soft EOOD, UIC 202787570, Sofia, Bulgaria) is an end-to-end encrypted peer-to-peer (P2P) communication and collaboration platform currently in pre-release / early-access preparation for iPhone, iPad, Mac, and Apple Watch. Wonek combines a native Rust MLS (RFC 9420) cryptographic core, mandatory TLS 1.3 over QUIC / WebTransport, and a proprietary port-prediction NAT traversal algorithm that establishes direct device-to-device P2P links at a high success rate even behind mobile 4G/5G Carrier-Grade NAT (CGNAT)—with automatic latency-measured encrypted relay fallback and ciphertext-only offline message queuing.

- Website: https://wonek.com/
- Release Status: Pre-release / early-access preparation for iPhone, iPad, Mac, and Apple Watch (inquiries: support@wonek.com)
- Features: https://wonek.com/features/
- Security Architecture: https://wonek.com/security/
- Technical Guides (10): https://wonek.com/guides/
- Side-by-Side Comparisons (30): https://wonek.com/compare/
- Support & Early Access: https://wonek.com/support/
- Privacy Policy: https://wonek.com/privacy-policy/
- Terms of Service: https://wonek.com/terms-of-service/
- Related Product — Wonek Video Studio for macOS: https://studio.wonek.com/

## Educational Guides

## Core Platform Matrices

**Wonek Architecture vs Typical Cloud & Legacy E2EE Messengers**

| Architectural Pillar | Wonek (Pre-Release · Apple Ecosystem) | Cloud Team Apps (Slack / Discord / Teams) | Legacy v1 E2EE Apps |
| --- | --- | --- | --- |
| Content End-to-End Encryption | Mandatory IETF MLS (RFC 9420) in native Rust core | None on text/docs (servers hold decryptable data) | Pairwise Double Ratchet + O(N) Sender Keys |
| Wire Transport Layer | Native QUIC / WebTransport with mandatory TLS 1.3 | TCP WebSockets + separate WebRTC SFU | TCP WebSockets + classic WebRTC |
| 4G/5G Mobile CGNAT Call Routing | Proprietary port-prediction NAT traversal for direct P2P | 100% routed through central cloud servers | Standard STUN/ICE (frequently falls back to TURN) |
| Strict Firewall & Offline Resilience | Latency-measured encrypted relay + ciphertext offline queue | Cloud storage & cloud SFU | TURN relay + server message queue |
| Large File Transfers | Direct P2P streaming with chunk-level resumption | Cloud storage buckets with paywall/quota caps | Encrypted cloud blobs capped at 50–100 MB |
| Docs & Shared Calendar | Built-in E2EE Yjs/Yrs CRDT docs + 5-view Calendar | Plaintext cloud docs & external calendar bots | Not included (forces external cloud links) |
| Apple Hardware Coverage | Native iPhone, iPad, Mac & Apple Watch (with PTT) | Electron desktop wrappers; rare Watch calling | Phone-first; limited watchOS & PTT support |

**Verified Wonek Capabilities Across Communication & Collaboration**

| Module | What Is Included | Security & Network Path |
| --- | --- | --- |
| Rich E2EE Messaging | Formatting, inline code, math formulas, replies, edits, pins, read receipts & disappearing timers | MLS (RFC 9420) E2EE + ciphertext-only offline queue |
| Voice & HD Video Calls | 1:1 & group calls, Opus audio, AEC, noise suppression & Picture-in-Picture (PiP) | Direct QUIC P2P primary + latency-measured encrypted relay |
| Native Screen Sharing | Broadcast display or app context during 1:1 & group calls on iPhone, iPad & Mac | End-to-end encrypted media stream over QUIC TLS 1.3 |
| Push-to-Talk & Voice Notes | Instant 1:1 & group walkie-talkie PTT plus async voice messages on iPhone, Mac & Watch | Low-latency Opus frames encrypted client-side |
| Direct P2P File Transfer | Large files & original-quality photo albums with automatic chunk-level resumption | Device-to-device QUIC streams; resumes from exact stopped chunk |
| CRDT Collaborative Docs | Real-time & offline multi-user documents powered by Yjs/Yrs conflict-free data types | Synced across authorized devices without server plaintext |
| 5-View Shared Calendar | Day, Multi-Day, Month, Year, and List views integrated beside conversations | Scoped cleanly per Personal or Work profile |

**Native Apple Platform Role Matrix (Pre-Release Preparation)**

| Platform | Enrollment & Crypto | Primary Everyday Workflows |
| --- | --- | --- |
| iPhone (iOS) | Primary phone-verified root + Rust MLS core | 5G CGNAT direct P2P calls, mobile screen share, PTT, camera albums & Personal/Work switch |
| iPad (iPadOS) | Noise-protocol QR linked MLS leaf device | Split-view CRDT document editing, PiP video calls, tablet screen sharing & Multi-Day calendar |
| Mac (macOS) | Noise-protocol QR linked MLS leaf device | Code/math messaging, crisp full-screen code reviews, multi-GB P2P file drops & Work workspace |
| Apple Watch (watchOS) | Companion / authorized wrist endpoint | Wrist voice calling, quick audio playback & instant 1:1 or group Push-to-Talk |

**Wonek Dual-Layer Cryptographic & Enrollment Architecture**

| Layer | Standard / Mechanism | What It Protects Against |
| --- | --- | --- |
| 1. Client Content E2EE | IETF MLS (RFC 9420) in dedicated native Rust core | Prevents relays, queues, ISPs, or cloud hosts from reading messages, calls, files, or docs |
| 2. Multi-Device Linking | Authenticated QR enrollment over Noise protocol | Prevents unauthenticated server key injection when adding iPad, Mac, or Watch |
| 3. Wire Transport Security | QUIC / WebTransport with mandatory TLS 1.3 | Encrypts transport framing, eliminates TCP head-of-line stalls & secures hop-by-hop packets |
| 4. Forward & Post-Compromise Security | MLS TreeKEM O(log N) epoch key ratcheting | Protects past messages and heals group secrets rapidly across multi-device rooms |

**Strict Infrastructure Data-Visibility Boundaries in Wonek**

| System Component | When Active | What Infrastructure Sees | What Infrastructure NEVER Sees |
| --- | --- | --- | --- |
| Direct P2P QUIC Session | Default call, screen share & file path (incl. high rate on CGNAT) | Nothing — packets travel directly between peer devices | Plaintext audio, video, screen pixels, file contents, or MLS keys |
| Latency-Measured Encrypted Relay | Only when strict corporate/hotel firewalls block direct UDP | Transient TLS 1.3 + MLS encrypted packet envelopes for forwarding | Decrypted voice/video frames or group epoch secrets |
| Offline Message Queue | When a recipient's Apple device is asleep or offline | Opaque MLS-encrypted ciphertext queued temporarily until delivery | Message text, inline code/math, CRDT doc body, or private keys |
| Account Verification | Initial account setup & anti-abuse verification | Verified phone identifier & Noise-enrolled public key packages | Personal vs Work conversation contents or decrypted contact notes |

**Direct Contact & Product Directory — Arte Soft EOOD**

| Inquiry Type | Destination | Notes |
| --- | --- | --- |
| Wonek Early Access & Beta Inquiries | support@wonek.com | Share which Apple devices you use (iPhone, iPad, Mac, Apple Watch) or team size |
| Company, Press & Legal Inquiries | office@arte-soft.com | Arte Soft EOOD · UIC 202787570 · Sofia, Bulgaria |
| Wonek Video Studio for macOS | https://studio.wonek.com/ | Dedicated website & Mac App Store home for our AI creator video studio |
| GPT Realtime Assistant | https://realtime-assistant.arte-soft.com/ | Live 58-language voice AI & meeting workspace for iPhone, iPad, and Mac |

## Educational Guides (Full Text & Tables)

### Why Mobile CGNAT Breaks Standard P2P Video Calls—and How Smart NAT Traversal Fixes Latency
URL: https://wonek.com/guides/p2p-video-calls-behind-mobile-cgnat/

When two smartphones call each other over 4G or 5G cellular networks, Carrier-Grade NAT (CGNAT) sits between both devices and the public internet. Conventional STUN/ICE hole-punching frequently gives up and routes your voice and video through a cloud relay—adding latency and hair-pinning traffic across regions.

**Key Takeaway:** Direct peer-to-peer routing keeps voice, video, and file payloads on the shortest physical network path between devices; Wonek pairs proprietary port-prediction NAT traversal over QUIC with automatic latency-aware encrypted relay fallback when UDP is completely blocked.

**Network Path Comparison on Cellular & Home Networks**

| Network Scenario | Conventional STUN / TURN Apps | Wonek Direct P2P + Encrypted Fallback | Real-World Call Impact |
| --- | --- | --- | --- |
| Home Wi-Fi to Home Wi-Fi ( Cone NAT ) | Direct UDP via standard STUN | Direct P2P over QUIC / WebTransport (TLS 1.3) | Lowest round-trip latency and crisp HD video |
| 4G / 5G Mobile CGNAT to Home Wi-Fi | Often falls back to cloud TURN relay | High-success direct P2P via proprietary port prediction | Avoids unnecessary cloud detour and reduces audio delay |
| Mobile CGNAT to Mobile CGNAT | Almost always relayed through central TURN servers | Frequently establishes direct device-to-device P2P link | Natural conversation cadence without talk-over collisions |
| Strict Corporate Firewall (UDP Blocked) | TCP/TLS TURN relay fallback | Automatic latency-measured encrypted relay fallback | Call connects reliably while MLS E2EE keeps media private |

#### Why Cellular Carrier-Grade NAT Defeats Naive Hole Punching
IPv4 address exhaustion forced mobile carriers worldwide to place thousands of phones behind shared Carrier-Grade NAT gateways. Unlike a simple home router that often reuses the same external port mapping across destinations, mobile CGNAT gateways dynamically assign external ports per destination session.

Standard WebRTC ICE agents query a public STUN server, learn the port assigned for that STUN server, and hand that single coordinate to the other peer. The moment the peer sends traffic from a different IP address, a strict or symmetric CGNAT gateway rejects the incoming packet and maps outbound traffic to an entirely new external port—causing standard P2P negotiation to time out and fall back to a central TURN relay.
#### High-Success Direct P2P with Proprietary Port Prediction
Wonek was engineered from the transport layer up to solve mobile-to-mobile connectivity without compromising security. Instead of relying solely on naive single-port STUN assumptions, Wonek uses a proprietary port-prediction NAT traversal algorithm designed specifically for real-world cellular CGNAT and restricted gateways.

When a direct path is achievable, both Apple devices lock onto a direct QUIC / WebTransport session protected by mandatory TLS 1.3 transport encryption underneath client-side MLS (RFC 9420) end-to-end encryption. Voice frames (Opus with acoustic echo cancellation and noise suppression), HD video, screen sharing, and large files travel straight between peers.
1. Both peers authenticate session keys end-to-end via Wonek's native Rust MLS cryptographic core before media flows.
2. Wonek coordinates NAT traversal and applies its proprietary port-prediction engine to establish a direct encrypted QUIC link even across difficult mobile CGNAT networks.
3. If a restrictive enterprise or hotel firewall blocks direct UDP entirely, Wonek automatically selects the lowest-latency encrypted relay so the call still connects immediately.
4. Throughout the call, relays and signaling nodes only ever observe opaque TLS 1.3 + MLS ciphertext—never plaintext audio, video, or keys.
#### Why Milliseconds Matter in Two-Way Voice & Video
Human conversation relies on subtle vocal cues under 150 milliseconds. When a mobile call between two people in the same city is hair-pinned through a cloud relay in another country, round-trip latency climbs and speakers accidentally interrupt each other.

By achieving direct peer-to-peer links across mobile CGNAT far more often than standard STUN/ICE stacks, Wonek keeps local calls local—preserving Opus voice clarity, smooth Picture-in-Picture video, and high-throughput direct file transfers.
#### Frequently Asked Questions
- **Does direct P2P expose my conversation content to my mobile carrier?** No. Every Wonek connection combines two encryption layers: mandatory TLS 1.3 wire encryption via QUIC / WebTransport plus client-side MLS (RFC 9420) end-to-end encryption. Neither your carrier nor any fallback relay can read your calls, messages, or files.
- **What happens when a firewall blocks UDP completely?** Wonek automatically falls back to a latency-measured encrypted relay path. The connection remains end-to-end encrypted via MLS, so the relay forwards only opaque ciphertext.
- **Is Wonek available to download today?** Wonek by Arte Soft EOOD is currently in pre-release and early-access preparation for iPhone, iPad, Mac, and Apple Watch. You can request early access at support@wonek.com.

### QUIC and WebTransport vs Legacy TCP and WebRTC Stacks in Modern Messengers
URL: https://wonek.com/guides/quic-and-webtransport-vs-tcp-webrtc-messaging/

Most chat apps glue together two separate networking worlds: a TCP WebSocket connection for text messages and a sprawling legacy WebRTC/SCTP/DTLS/SRTP stack for calls. Building natively on QUIC and WebTransport unifies multiplexed streams, datagrams, and mandatory TLS 1.3 encryption into one modern transport.

**Key Takeaway:** QUIC eliminates TCP head-of-line blocking across independent streams, completes TLS 1.3 cryptographic handshakes in fewer round trips, and unifies messaging, calls, and resumable P2P file transfers on a single encrypted transport foundation.

**Transport Protocol Comparison for Real-Time Communication**

| Architectural Dimension | Legacy TCP / WebSockets | Classic WebRTC Stack | Wonek QUIC / WebTransport |
| --- | --- | --- | --- |
| Wire Encryption | Separate TLS handshake over TCP | Split DTLS + SRTP + SCTP layers | Mandatory built-in TLS 1.3 from packet one |
| Head-of-Line Blocking | Severe — one lost packet stalls all messages | Avoided on RTP, complex on data channels | Eliminated across independent QUIC streams |
| Connection Establishment | TCP 3-way handshake + TLS (2–3 RTTs) | Multi-stage ICE + DTLS negotiation | Combined transport + TLS 1.3 (1-RTT / 0-RTT) |
| Network Roaming (Wi-Fi to 5G) | IP change breaks socket; full reconnect | Requires ICE restart and media pause | QUIC connection migration survives IP changes |
| Unified Chat + Media + Files | Poor for real-time voice/video | Focused on media; separate signaling socket | Single protocol for chat, voice/video, PTT & P2P files |

#### How TCP Head-of-Line Blocking Slows Mobile Messaging
On a train, elevator, or congested café Wi-Fi, 1–3% packet loss is routine. Over a single TCP WebSocket connection, the operating system kernel must deliver bytes strictly in order. If packet #42 carrying a thumbnail chunk drops, packets #43 through #60—carrying typing indicators, Push-to-Talk signaling, or text edits—sit frozen in the receive buffer waiting for retransmission.

QUIC solves this at the transport layer. Built atop UDP with per-stream sequencing and congestion control, QUIC lets each stream progress independently. A lost packet in a large photo album transfer never stalls an urgent text reply, calendar update, or voice frame.
#### Mandatory TLS 1.3 Underneath End-to-End Encryption
In QUIC and WebTransport, encryption is not an optional add-on—TLS 1.3 is baked directly into the transport handshake, encrypting even transport control metadata that legacy TCP leaves visible in cleartext headers.

Wonek pairs this mandatory QUIC / WebTransport TLS 1.3 wire security with client-side MLS (RFC 9420) end-to-end encryption. Even before application payloads are decrypted on your iPhone, iPad, Mac, or Apple Watch, every packet crossing Wi-Fi, cellular CGNAT, or an encrypted fallback relay enjoys dual-layer cryptographic protection.
1. Establish a QUIC / WebTransport session with integrated TLS 1.3 transport security in a single round trip.
2. Open dedicated, independent QUIC streams for control signaling, CRDT document deltas, and chunked P2P file transfers.
3. Transmit latency-sensitive Opus audio and HD video without cross-stream head-of-line stalls.
4. Migrate active sessions smoothly across local interface transitions when stepping from office Wi-Fi onto 5G.
#### One Cohesive Stack Across iPhone, iPad, Mac & Apple Watch
Maintaining separate WebSocket, HTTP upload, and legacy WebRTC stacks multiplies battery drain and edge-case bugs. By standardizing on QUIC / WebTransport alongside a shared Rust cryptographic core, Wonek delivers consistent behavior across Apple devices.
#### Frequently Asked Questions
- **Is QUIC encryption a replacement for End-to-End Encryption?** No—in Wonek they work together as two distinct layers. QUIC / WebTransport provides mandatory TLS 1.3 wire encryption on every hop, while MLS (RFC 9420) encrypts messages, calls, and files end-to-end between user devices so servers and relays never possess decryption keys.
- **Why does WebTransport matter alongside QUIC?** WebTransport brings standardized bidirectional streams and low-latency datagrams over HTTP/3 and QUIC, enabling clean multiplexing without legacy TCP WebSocket bottlenecks.
- **Does QUIC work when a network blocks UDP?** When strict firewalls block direct UDP traffic, Wonek automatically transitions to its latency-measured encrypted relay fallback so messages and calls continue without manual configuration.

### MLS (RFC 9420) End-to-End Encryption Explained: Scaling Private Groups & Multi-Device Chat
URL: https://wonek.com/guides/mls-rfc-9420-end-to-end-encryption-explained/

First-generation encrypted messengers used pairwise ratchets designed for two phones—forcing group chats and multi-device setups to encrypt keys repeatedly for every participant device. Standardized by the IETF as RFC 9420, Messaging Layer Security (MLS) upgrades group and multi-device E2EE to logarithmic efficiency.

**Key Takeaway:** Wonek implements MLS (RFC 9420) inside a dedicated Rust cryptographic core, delivering forward secrecy, post-compromise security, efficient group key rotation, and authenticated Noise-protocol QR multi-device enrollment.

**Pairwise Double Ratchet vs IETF MLS (RFC 9420) Architecture**

| Cryptographic Property | Legacy Pairwise Ratchet (v1 E2EE) | IETF MLS — RFC 9420 (Used in Wonek) | Why Users Notice the Difference |
| --- | --- | --- | --- |
| Member Key Update Cost | O(N) — scales linearly with devices | O(log N) via asynchronous ratcheting trees | Instant membership & key updates across multi-device groups |
| Multi-Device Synchronization | Separate pairwise session per linked device | Each authorized device is a first-class leaf node | Reliable sync across iPhone, iPad, Mac & Apple Watch |
| Forward Secrecy | Yes — per pairwise chain | Yes — epoch-based group key ratcheting | Past messages stay unreadable if future state is exposed |
| Post-Compromise Security | Requires pairwise message exchange with each peer | Single tree update heals group secret for all members | Faster cryptographic self-healing across entire rooms |
| Open IETF Standardization | Proprietary / de-facto variants | Peer-reviewed IETF RFC 9420 standard | Auditable, modern cryptographic design |

#### Why Multi-Device Apple Ecosystems Outgrew Pairwise Sessions
Suppose a 25-person project team uses iPhones, iPads, Macs, and Apple Watches—totaling nearly 80 active client endpoints. Under older pairwise encryption designs, adding or removing a teammate or rotating compromised keys requires linear work across dozens of individual sessions, often causing out-of-sync 'waiting for this message' placeholders.

MLS (RFC 9420) organizes authorized client devices as leaves in a balanced cryptographic tree (TreeKEM). Updating a device's leaf secret refreshes the shared epoch key in O(log N) operations—even when offline teammates are not currently connected.
#### Inside Wonek's Native Rust Cryptographic Core & Noise QR Enrollment
In Wonek, plaintext never leaves your device unencrypted. Encryption and key schedule derivation run inside a memory-safe native Rust cryptographic core shared across Apple platforms.

When you add your Mac or iPad to your account, Wonek does not upload raw private keys to a cloud backup. Instead, you scan an authenticated QR code that establishes a direct Noise-protocol encrypted enrollment channel between your existing iPhone and the new device.
1. Install Wonek on your primary iPhone and generate device-local cryptographic identity keys in the native Rust core.
2. Open Wonek on your Mac or iPad and scan the enrollment QR code to complete an authenticated Noise-protocol device handshake.
3. Create 1:1 or group conversations where every message, voice/video call key, CRDT document update, and file transfer is protected under MLS (RFC 9420).
4. Send messages freely to offline contacts—Wonek's offline server queue holds only opaque ciphertext until their devices reconnect.
#### What Servers and Relays Can—and Cannot—See
Wonek's signaling infrastructure, offline message queues, and fallback media relays never possess group epoch keys or private device keys. Combined with QUIC / WebTransport TLS 1.3 wire encryption, infrastructure nodes handle exclusively encrypted payloads.
#### Frequently Asked Questions
- **Is end-to-end encryption enabled by default in Wonek group chats?** Yes. Unlike messengers where only 1:1 'Secret Chats' are end-to-end encrypted, Wonek applies MLS (RFC 9420) end-to-end encryption by default across 1:1 chats, group chats, voice/video calls, screen sharing, and file transfers.
- **How do offline messages work with end-to-end encryption?** When a recipient's device is offline or in Airplane Mode, Wonek queues the already-encrypted MLS ciphertext on the server and delivers it the moment their device reconnects. The server cannot decrypt the queued payload.
- **How does QR multi-device linking protect my keys?** Scanning the enrollment QR establishes a mutually authenticated Noise-protocol channel directly between your trusted device and the new Apple device, preventing man-in-the-middle server key injection.

### Keeping Encrypted Voice & Video Calls Alive When Switching Between Wi-Fi and 5G
URL: https://wonek.com/guides/seamless-wifi-to-5g-call-handoff-with-quic/

Everyone knows the classic VoIP dead zone: you walk out of your apartment or office while talking, your iPhone clings to fading Wi-Fi before switching to 5G, and the call freezes for five seconds or disconnects. Legacy TCP/IP sockets tie your session identity directly to an IP address that just vanished.

**Key Takeaway:** Because QUIC identifies sessions by cryptographic Connection IDs rather than brittle IP-and-port tuples, Wonek recovers smoothly across Wi-Fi-to-5G transitions while preserving TLS 1.3 and MLS end-to-end encryption.

**What Happens During a Wi-Fi-to-5G Network Transition**

| Transition Stage | Legacy TCP / Classic VoIP | Wonek over QUIC / WebTransport |
| --- | --- | --- |
| 1. Edge of Wi-Fi Range (Packet Loss) | Head-of-line blocking stalls signaling & chat | Independent QUIC streams isolate packet loss |
| 2. Cellular Radio Takes Over (New IP) | Old 4-tuple breaks; full socket + TLS teardown | QUIC Connection ID decouples session from old IP |
| 3. NAT Path Re-validation | Slow full ICE restart & audible call silence | Fast path validation — direct P2P or encrypted relay |
| 4. In-Flight File Transfers | Upload fails and restarts from 0% | Chunk-level resumption continues from exact byte offset |

#### The Four-Tuple Trap in Traditional Calling Apps
Traditional networking identifies a connection by four numbers: source IP, source port, destination IP, and destination port. The instant you step into an elevator or out onto the sidewalk, your iPhone drops your home router's broadband IP and switches to your carrier's 5G CGNAT address.

Apps built on legacy TCP sockets must detect the dead socket, establish a new TCP handshake, repeat the TLS handshake, re-authenticate session state, and renegotiate media paths—creating the dreaded robotic audio freeze.
#### How QUIC & Resumable P2P Keep Conversations Moving
QUIC (RFC 9000) separates logical connections from underlying network addresses using Connection IDs and authenticated path validation. When your network interface shifts from Wi-Fi to cellular—or between two Wi-Fi access points—the cryptographic context remains intact.

In Wonek, this transport resilience combines with smart NAT traversal and chunk-resumable file transfers. Voice calls with Opus audio recover cleanly, Picture-in-Picture video continues without tearing down your call room, and multi-gigabyte file transfers resume at the exact chunk where Wi-Fi dropped.
1. Start your E2EE voice or HD video call on home or office Wi-Fi—Picture-in-Picture lets you navigate other apps freely.
2. Walk outdoors onto 4G/5G cellular without hanging up or manually redialing.
3. Wonek validates the new cellular path—establishing direct P2P across CGNAT when available or seamlessly routing via the lowest-latency encrypted relay.
4. Any background P2P photo album or large file transfer automatically resumes from the last verified chunk.
#### Audio Engineering That Masks Micro-Jitter
Transport speed is half the equation; acoustic resilience is the other. Wonek pairs QUIC transport with adaptive Opus audio encoding, acoustic echo cancellation (AEC), and real-time noise suppression—keeping speech intelligible even as street noise rises.
#### Frequently Asked Questions
- **Do large file transfers restart at 0% if I lose signal in an elevator?** No. Wonek's direct peer-to-peer file transfer engine tracks verified chunks and resumes directly from where the transfer paused once connectivity returns.
- **Does switching from Wi-Fi to 5G weaken encryption during the handoff?** Never. Both QUIC TLS 1.3 path validation and MLS (RFC 9420) end-to-end encryption remain strictly enforced across every network change.
- **Can I take voice calls on Apple Watch when away from my Mac?** Yes. Wonek is designed across iPhone, iPad, Mac, and Apple Watch, including wrist-ready calling, voice messages, and Push-to-Talk audio.

### End-to-End Encrypted Screen Sharing Across iPhone, iPad, and Mac
URL: https://wonek.com/guides/end-to-end-encrypted-screen-sharing-iphone-ipad-mac/

Most popular team chat and gaming apps decrypt your shared screen on central media servers—or skip end-to-end encryption for voice and screen sharing altogether. When you are walking a colleague through source code, production logs, or private finances, your pixels should only be readable by the people on the call.

**Key Takeaway:** Wonek encrypts screen-sharing video streams end-to-end alongside Opus voice and camera feeds, routing pixels directly peer-to-peer over QUIC whenever possible for sharp text legibility and responsive cursor feedback.

**Screen Sharing Security & Latency Across Communication Tools**

| Capability | Typical Gaming / Workspace Chat | Browser Meeting Links | Wonek Native Apple App |
| --- | --- | --- | --- |
| End-to-End Encryption on Screen Share | Often terminated at central SFU servers | Usually cloud-decrypted by default | End-to-end encrypted by default (MLS + QUIC) |
| Network Media Path | Always routed via cloud voice region | Cloud media cluster | Direct P2P primary + encrypted relay fallback |
| Supported Apple Devices | Desktop-centric; clunky mobile broadcast | Requires browser tabs or meeting links | Native iPhone, iPad, and Mac screen sharing |
| Picture-in-Picture (PiP) Multitasking | Inconsistent on iOS/iPadOS | Limited inside mobile browsers | Native PiP while viewing docs or code |

#### Why Shared Screens Demand Strict End-to-End Encryption
A five-minute screen share routinely flashes API keys in terminal tabs, customer email addresses, unreleased designs, banking rows, or personal notifications. On platforms where voice and video terminate on server-side Selective Forwarding Units (SFUs) without E2EE, raw video frames exist in server memory.

Wonek treats screen sharing with the exact same cryptographic rigor as text messaging. Frames captured on your iPhone, iPad, or Mac are encrypted on-device before leaving your network interface and can only be decrypted by authenticated call participants.
#### Why Direct P2P Makes Small Code & Spreadsheet Text Sharper
Camera faces tolerate soft compression, whereas 12-point monospace code in Xcode or dense numbers in a spreadsheet blur immediately when a cloud server aggressively downscales bitrate.

Because Wonek establishes direct peer-to-peer QUIC connections at a high rate—even across mobile CGNAT—screen-share frames travel straight between peers with lower round-trip latency and quick congestion feedback, keeping text crisp while you talk simultaneously over Opus audio.
1. Enable Focus / Do Not Disturb on your Mac, iPad, or iPhone so unrelated banners stay hidden.
2. Start a 1:1 or group E2EE voice or video call inside Wonek.
3. Tap or click Share Screen to broadcast your Mac display/window or iOS/iPadOS screen.
4. Open a shared Wonek CRDT collaborative document alongside the call so teammates can type live notes while watching your screen.
#### Everyday Workflows: From Pair Programming to Family Tech Support
Whether pair-debugging Swift and Rust on macOS, reviewing architectural diagrams on an iPad, or helping a parent configure iPhone privacy settings remotely, native Apple integration means zero meeting URLs to copy and zero browser plugins to install.
#### Frequently Asked Questions
- **Can Wonek servers record or inspect what is on my shared screen?** No. Screen sharing in Wonek is end-to-end encrypted on your device before transmission. Even if a strict firewall triggers an encrypted relay fallback, the relay sees only unreadable ciphertext.
- **Does screen sharing work from iPhone and iPad as well as Mac?** Yes. Wonek supports native screen sharing across iPhone, iPad, and Mac during 1:1 and group calls.
- **Can I keep watching someone's shared screen in Picture-in-Picture?** Yes. Native Picture-in-Picture (PiP) support lets you keep the video call visible while switching into another app or collaborative note.

### Resumable Direct Peer-to-Peer File Transfer: Sending Large Files Without Cloud Quotas
URL: https://wonek.com/guides/resumable-peer-to-peer-large-file-transfer/

Sending a 4 GB video archive or 200-photo RAW album through a typical chat app hits an artificial 25 MB–2 GB attachment wall—or forces you to upload everything to a cloud drive, burn storage quota, create a share link, and wait twice. Direct peer-to-peer transfer with chunk-level resumption removes the middleman.

**Key Takeaway:** Wonek streams large files and photo albums directly between authorized peers over QUIC with MLS end-to-end encryption and chunk-level resumption—if Wi-Fi drops at 87%, the transfer resumes at 87% instead of 0%.

**Large File Sharing Methods Compared**

| Transfer Attribute | Standard Cloud Chat Apps | Cloud Drive Share Links | Wonek Direct P2P File Transfer |
| --- | --- | --- | --- |
| Transfer Path | Upload to cloud -> recipient downloads | Upload to cloud -> link -> download | Direct device-to-device P2P over QUIC (primary) |
| Cloud Storage Quota Used | Capped by strict per-file limits (e.g., 25–100 MB) | Consumes paid cloud drive storage | Zero cloud drive quota consumed on direct P2P |
| Interrupted Connection at 87% | Often fails and restarts at 0% | Browser upload frequently resets | Chunk-level resumption continues from 87% |
| End-to-End Encryption | Varies; many scan or store cloud copies | Rarely E2EE by default | Always E2EE (MLS) + TLS 1.3 over QUIC |
| Distance & Cross-Network Reach | Works globally up to tiny size cap | Works globally (double transfer wait) | Works across cities & mobile CGNAT (unlike AirDrop) |

#### AirDrop Convenience—Across Cities and Mobile Networks
Apple users love AirDrop when sitting two meters apart, because files jump straight from Mac to iPhone without waiting on a cloud bucket. The moment your collaborator is across town or in another country, AirDrop stops working and traditional messengers punish you with tiny file-size caps or lossless-to-blurry photo recompression.

Wonek brings direct peer-to-peer file and photo album transfers across the internet. Using its proprietary port-prediction NAT traversal over QUIC, Wonek establishes direct encrypted pipes between devices—even across mobile 4G/5G CGNAT networks—so sender upload speed feeds recipient download speed simultaneously.
#### Why Chunk-Level Resumption Saves Hours on Mobile Networks
Large transfers fail in traditional apps because they treat a multi-gigabyte archive as one fragile HTTP upload. Closing a MacBook lid at a train stop or walking through a cellular dead spot aborts the stream and wastes gigabytes of mobile data.

Wonek slices large files and photo albums into cryptographically verified chunks over multiplexed QUIC streams. Both peers track exact chunk completion state: if a device sleeps or switches from Wi-Fi to 5G, Wonek resumes seamlessly from the next missing chunk—never restarting at zero.
1. Drop original-quality photo albums, ZIP archives, code bundles, or ProRes video files directly into any 1:1 or group Wonek chat.
2. Wonek encrypts chunks on-device and opens dedicated QUIC streams so your text messages and voice calls stay completely responsive while files move in parallel.
3. Monitor real-time transfer progress; if either peer changes networks or pauses briefly, chunk-level resumption picks up automatically where it stopped.
4. Verify received files locally on your iPhone, iPad, or Mac with zero server-side plaintext copies left behind.
#### Zero Plaintext Copies Sitting in Forgotten Cloud Buckets
Every time you paste a third-party cloud drive link for a tax PDF, contract archive, or private family video, a copy lingers on remote servers until someone remembers to revoke it. Direct P2P E2EE transfers keep your files on the devices that actually belong in the conversation.
#### Frequently Asked Questions
- **Does sending a large file block text messages in the same chat?** No. Because Wonek runs over multiplexed QUIC streams, text messages, edits, reactions, and voice frames travel on separate streams without waiting behind large file chunks.
- **What if I close my MacBook halfway through sending a 5 GB archive?** Wonek's chunk-level resumption records every verified chunk already received. When your Mac wakes and reconnects, the transfer continues from the exact remaining chunks rather than restarting at 0%.
- **Are transferred photos and files end-to-end encrypted?** Yes. All files and photo albums are end-to-end encrypted client-side in Wonek's MLS cryptographic layer and transmitted over TLS 1.3 QUIC.

### Encrypted Push-to-Talk (PTT) on iPhone and Apple Watch: Faster Than Typing, Lighter Than a Call
URL: https://wonek.com/guides/push-to-talk-walkie-talkie-on-iphone-and-apple-watch/

Texting takes two thumbs and eyes glued to glass; dialing a full phone call demands formal greetings and uninterrupted attention. Push-to-Talk (PTT) hits the sweet spot for field teams, families in motion, events, and Apple Watch wearers—delivering instant spoken bursts without sacrificing end-to-end encryption.

**Key Takeaway:** Unlike legacy walkie-talkie apps that route unencrypted voice through ad-supported cloud servers, Wonek delivers 1:1 and group Push-to-Talk with full MLS end-to-end encryption across iPhone, iPad, Mac, and Apple Watch.

**Choosing Between Text, Voice Notes, Push-to-Talk, and Live Calls**

| Mode in Wonek | Interaction Speed | Hands / Eyes Needed | Best Real-World Scenario |
| --- | --- | --- | --- |
| Push-to-Talk (PTT) | Instant live burst (< 1s) | Single press on iPhone or Apple Watch | Field coordination, skiing/cycling, event crews, quick check-ins |
| Async Voice Messages | Record & listen anytime | Tap once to record, tap to play | Thoughtful updates across time zones without interrupting |
| Full E2EE Voice / Video Call | Continuous bidirectional duplex | Hands-free once connected (PiP) | Deep 1:1 discussions, group standups, screen-share reviews |
| Rich Text + Code / Math | Asynchronous & searchable | Typing on keyboard or phone | Exact addresses, inline code, LaTeX math, pinned specs |

#### Why Legacy Walkie-Talkie Apps Fall Short on Privacy
Standalone consumer walkie-talkie apps became popular with logistics crews and outdoor groups, yet most terminate audio in plaintext on central servers, bundle heavy ad trackers, or charge per-seat dispatch fees just to add encryption. Apple's built-in Watch Walkie-Talkie, meanwhile, is strictly 1:1 and lacks group channels, Mac desktop participation, or persistent chat history.

Wonek builds 1:1 and group Push-to-Talk right inside your end-to-end encrypted messenger. Every spoken burst is protected by MLS (RFC 9420) E2EE and carried over low-latency QUIC.
#### Wrist-First Communication on Apple Watch
When you are carrying groceries, configuring rack hardware, cycling, or coordinating backstage at an event, pulling out a laptop or typing on a phone slows everyone down. Wonek's Apple Watch support brings voice calling, audio playback, and instant PTT right to your wrist—staying synchronized with your iPhone, iPad, and Mac.

Opus voice compression paired with acoustic echo cancellation and noise suppression keeps brief outdoor transmissions crisp even in wind or crowd noise.
1. Open a 1:1 chat or dedicated team channel in Wonek on your iPhone, Mac, or Apple Watch.
2. Hold to transmit a concise spoken update via Push-to-Talk—Opus encoding starts streaming immediately over QUIC.
3. Release to listen as teammates reply from their Apple Watch, iPhone, or Mac desktop.
4. Switch seamlessly to an asynchronous voice message or full HD screen-share call whenever a quick burst turns into a deeper discussion.
#### Personal & Work Profile Respect Built In
Instant voice only works when you control who can reach you. Because Wonek separates Personal and Work profiles under one account, an operations PTT channel never intrudes on family evenings once you step off shift.
#### Frequently Asked Questions
- **Does Wonek Push-to-Talk work in groups as well as 1:1?** Yes. Unlike 1:1-only wrist walkie-talkie tools, Wonek supports both 1:1 and group Push-to-Talk with full MLS end-to-end encryption.
- **Are Push-to-Talk audio bursts end-to-end encrypted?** Yes. Every PTT transmission, voice message, and live call uses Wonek's dual-layer security: client-side MLS (RFC 9420) E2EE over TLS 1.3 QUIC.
- **Which Apple devices support Wonek voice and PTT?** Wonek is being prepared for pre-release across iPhone, iPad, Mac, and Apple Watch.

### CRDT Collaborative Documents & Shared Calendars Inside Encrypted Chat
URL: https://wonek.com/guides/crdt-collaborative-documents-and-shared-calendars-in-chat/

Teams and families often adopt an encrypted messenger for chat—then immediately paste links to unencrypted Google Docs and shared cloud calendars where every sensitive roadmap, travel itinerary, and meeting note sits in cleartext. Wonek builds real-time CRDT documents and a 5-view shared calendar straight into the encrypted workspace.

**Key Takeaway:** Powered by conflict-free replicated data types (Yjs/Yrs CRDTs), Wonek documents let multiple people edit simultaneously—even offline on a flight—and merge cleanly without central plaintext cloud editors.

**Fragmented App Stack vs Wonek Integrated Workspace**

| Workflow Layer | Fragmented Cloud Tool Stack | Wonek All-in-One E2EE Platform |
| --- | --- | --- |
| Real-Time Messaging & Math/Code | Separate chat app (plain cloud or chat-only E2EE) | MLS E2EE chat with rich text, inline code & math formulas |
| Live Co-Edited Documents | External cloud docs (server holds full plaintext) | Built-in Yjs/Yrs CRDT collaborative docs synced E2EE |
| Offline Document Editing | Browser cache breaks or creates duplicate copies | Mathematically conflict-free CRDT merge upon reconnect |
| Group Scheduling | External calendar links & third-party bots | Built-in Shared Calendar (Day, Multi-Day, Month, Year, List) |
| Reviewing Specs Live | Switch to third video-call app | 1-tap E2EE voice/video & screen share right beside the doc |

#### Why Encrypted Chat Alone Leaves a Privacy Gap
Security is only as strong as where your permanent decisions live. If two founders discuss an acquisition or patent strategy in an encrypted chat, then write the actual term sheet in a conventional cloud document editor and schedule milestones on an ad-tech calendar, metadata and document contents are still exposed to third-party servers.

Bringing collaborative documents and shared scheduling inside Wonek closes that gap—keeping conversations, living notes, and dates under one cryptographic roof.
#### How Yjs / Yrs CRDTs Enable Offline-First Co-Editing
Traditional cloud word processors rely on Operational Transformation (OT) coordinated by a central server that must read every character in plaintext to resolve edit order. Conflict-Free Replicated Data Types (CRDTs)—implemented in Wonek with high-performance Yjs/Yrs data structures—guarantee mathematically deterministic convergence on client devices without requiring a server to read the document.

Two teammates can edit the same project spec on a MacBook and an iPad while one is offline on an airplane. The moment connectivity returns, encrypted CRDT state vectors exchange and merge cleanly without overwriting anyone's paragraphs.
1. Create a collaborative document directly alongside a Personal or Work conversation in Wonek.
2. Co-edit checklists, technical specs, travel plans, or meeting agendas simultaneously across Mac, iPad, and iPhone—even while offline.
3. Switch to the built-in Shared Calendar across Day, Multi-Day, Month, Year, or List views to lock in deadlines without leaving the app.
4. Launch an E2EE voice, video, or screen-share call directly from the conversation when synchronous review is faster.
#### Five Calendar Views Tailored to Real Planning
Whether scanning a full Year overview for product launches, planning a 3-day offsite in Multi-Day view, checking today's hour-by-hour agenda in Day view, or triaging upcoming milestones in List and Month views, Wonek's shared calendar keeps schedules tied to the people who need them.
#### Frequently Asked Questions
- **What happens if two people edit the same paragraph while one is offline?** Wonek uses Yjs/Yrs Conflict-Free Replicated Data Types (CRDTs). Both devices record fine-grained state updates locally and merge them deterministically without lost edits when back online.
- **Which calendar views are built into Wonek?** Wonek includes five built-in calendar views—Day, Multi-Day, Month, Year, and List—directly alongside your conversations.
- **Can Wonek servers read our collaborative documents?** No. CRDT updates sync across authorized devices inside Wonek's end-to-end encrypted architecture so servers never inspect plaintext document contents.

### Separating Personal and Work Profiles in One Encrypted Messenger—Without Two Phones
URL: https://wonek.com/guides/separating-personal-and-work-profiles-in-one-messenger/

Using consumer WhatsApp or Telegram for client work dumps Saturday morning bug reports right next to family birthday photos—and risks accidentally forwarding a work PDF to a personal group. Carrying two iPhones is expensive and awkward. Wonek solves this with dedicated Personal and Work profile contexts under one account.

**Key Takeaway:** One phone-verified Wonek identity unlocks clearly separated Personal and Work/Team contexts—isolating chats, shared calendars, collaborative CRDT documents, and Push-to-Talk channels without juggling SIM cards.

**Approaches to Separating Personal & Professional Communication**

| Approach | Context Separation | Hardware & Cost Friction | Encryption & Feature Parity |
| --- | --- | --- | --- |
| Single Consumer Chat Feed | None — clients & family mixed together | Zero extra hardware, high mistake risk | Often lacks docs, calendar & work boundaries |
| Separate Enterprise App (Slack/Teams) | High app separation | Per-seat cloud SaaS cost; heavy desktop RAM | No default E2EE — admins/cloud index messages |
| Two Physical Phones / Dual SIM | Strict hardware split | Expensive second device & extra charging | Fragmented Mac & Apple Watch pairing |
| Wonek Personal + Work Profiles | Clean profile switch inside one native app | One Apple device ecosystem, one account | Full MLS E2EE, QUIC P2P, CRDT docs & calendars in both |

#### The Hidden Cost of Mixed Chat Feeds
Context collapse happens silently: you open your messenger at 9 PM to check a message from your spouse and spot three unread work threads at the top of the list. Worse, autocomplete muscle memory makes it dangerously easy to drop an internal screenshot or voice note into the wrong group when personal and professional rooms share one flat inbox.

Dedicated enterprise tools like Slack or Microsoft Teams separate the inbox, yet they sacrifice client-side end-to-end encryption—storing every conversation in searchable cloud databases.
#### How Wonek's Dual-Context Profiles Work
Wonek gives every user clean Personal and Work/Team profile contexts under a single phone-verified account. Each context maintains its own organized conversation list, shared calendar views, collaborative CRDT documents, and group rooms.

Because both profiles run on the exact same native Rust MLS cryptographic core and QUIC / WebTransport engine, you never have to trade away end-to-end encryption when switching from family mode to engineering or client work.
1. Verify your account once and enroll your iPhone, iPad, Mac, and Apple Watch via Noise QR device linking.
2. Keep family groups, personal photo albums, and household shared calendars inside your Personal profile.
3. Organize engineering rooms, client screen-share calls, sprint calendars, and technical CRDT docs inside your Work profile.
4. Switch contexts intentionally so work threads never clutter family time—and accidental cross-posting becomes far harder.
#### Built for Founders, Consultants, Engineers & Privacy-Conscious Teams
Independent consultants, distributed startups, legal/medical advisors, and security teams need both fast collaboration (inline code, LaTeX math, screen sharing, resumable P2P files) and calm personal messaging—without maintaining enterprise servers.
#### Frequently Asked Questions
- **Do I need two phone numbers to use Personal and Work profiles in Wonek?** No. Both Personal and Work/Team profile contexts operate cleanly under a single phone-verified Wonek account.
- **Are Work profile chats and calls still end-to-end encrypted?** Yes. Both Personal and Work profiles enforce identical client-side MLS (RFC 9420) end-to-end encryption and QUIC TLS 1.3 transport security.
- **Do collaborative docs and shared calendars respect profile separation?** Yes. Conversations, CRDT documents, and shared calendar views stay organized within their respective Personal or Work context.

### Direct Peer-to-Peer vs Encrypted Relay Fallback: Understanding Latency, Firewalls & Privacy
URL: https://wonek.com/guides/direct-p2p-vs-cloud-relay-servers-latency-and-privacy/

Pure serverless P2P messengers often fail to deliver messages when one phone is asleep or behind corporate Wi-Fi, while cloud-only messengers force 100% of calls through central servers even when two devices sit in the same neighborhood. A resilient communication architecture combines the best of both—without ever surrendering encryption keys.

**Key Takeaway:** Wonek prioritizes direct device-to-device P2P paths over QUIC for lowest latency and zero-middleman media, while providing automatic latency-measured encrypted relays for strict firewalls and ciphertext-only offline queues when peers are asleep.

**Pure Serverless P2P vs Cloud-Only vs Wonek Hybrid E2EE Architecture**

| Real-World Requirement | Pure Serverless P2P Apps | Centralized Cloud Messengers | Wonek Direct P2P + Ciphertext Fallback |
| --- | --- | --- | --- |
| Call Latency on 4G/5G & Wi-Fi | Low if connected; often fails behind CGNAT | Higher — always routed via cloud servers | Lowest — high-success direct P2P across CGNAT |
| Strict Corporate / Hotel Firewall (No UDP) | Connection fails completely | Connects via cloud TCP/TLS | Connects via latency-measured encrypted relay |
| Sending Text While Recipient Is Offline | Undelivered until both apps open together | Delivered instantly on wake | Queued as opaque MLS ciphertext; delivered on wake |
| iOS Battery & Background Wake | Heavy background DHT drain | Efficient push wakeup | Battery-friendly wakeup without background DHT churn |
| Server Access to Plaintext or Keys | None | Varies (many hold group/cloud keys) | Zero — servers/relays handle ciphertext only |

#### Why Pure Serverless P2P Breaks on Mobile Operating Systems
On paper, eliminating every server sounds ideal. On iOS and watchOS, however, Apple aggressively suspends background sockets to protect multi-day battery life. Pure DHT or Tor-only messengers struggle whenever Alice sends a message at 10:05 AM while Bob's iPhone is in a subway tunnel, and Alice boards a flight at 10:15 AM before Bob surfaces—because both devices are never online simultaneously.

Similarly, hospital, university, and enterprise networks routinely block arbitrary UDP ports. Without an encrypted fallback path, pure P2P calls simply fail when you need them most.
#### How Wonek Achieves Direct P2P Without Sacrificing Reliability
Wonek follows a clear principle: route directly peer-to-peer whenever physically possible, fall back gracefully when a firewall forbids direct UDP, and never let any intermediary decrypt user data.

During live calls, screen shares, and large file transfers, Wonek's proprietary port-prediction NAT traversal establishes direct QUIC sessions at a high rate across home broadband and mobile CGNAT. When UDP is completely blocked, Wonek selects the lowest-latency encrypted relay automatically. And when a recipient is offline, encrypted MLS messages wait safely in an opaque ciphertext queue until their device wakes.
1. Encrypt every message, call stream, file chunk, and CRDT edit client-side inside Wonek's Rust MLS (RFC 9420) core.
2. Attempt direct device-to-device P2P over QUIC / WebTransport (TLS 1.3) first using smart NAT traversal.
3. If strict firewall rules block direct UDP packets, route encrypted packets automatically through the lowest-latency relay.
4. If a recipient is offline, hold only encrypted ciphertext in the delivery queue until their Apple device reconnects.
#### Cryptographic Separation of Routing from Content
Because MLS end-to-end encryption happens strictly on enrolled client devices before QUIC transport framing, fallback relays and offline queues act purely as blind packet forwarders—delivering enterprise-grade reliability with zero plaintext exposure.
#### Frequently Asked Questions
- **Can a Wonek fallback relay decrypt my call if direct P2P is blocked by corporate Wi-Fi?** No. Media and data remain end-to-end encrypted between participant devices using MLS (RFC 9420). Fallback relays forward opaque encrypted packets without ever holding session decryption keys.
- **Do both users need to have Wonek open at the same time to exchange text messages?** No. When a recipient is offline, Wonek temporarily holds the end-to-end encrypted ciphertext in an offline queue and delivers it as soon as their device comes back online.
- **Where can I find Wonek Video Studio for macOS?** Wonek Video Studio—Arte Soft's AI video creation studio for macOS—lives at https://studio.wonek.com/, while https://wonek.com is dedicated to the Wonek E2EE P2P communication platform.

## Side-by-Side Comparisons (Full Verdicts & 90 GFM Tables)

### Wonek vs Signal: Port-Predicted QUIC P2P, MLS Groups & Workspace Tools Compared
URL: https://wonek.com/compare/wonek-vs-signal/

Signal set the global benchmark for private consumer messaging with the Signal Protocol. Wonek builds for the next architectural generation on Apple devices—combining IETF MLS (RFC 9420) encryption in a Rust core, QUIC/WebTransport, high-success direct P2P behind mobile CGNAT, and built-in collaborative docs and calendars.

**Direct Answer / Verdict:** Choose Signal today if you need an immediately available cross-platform messenger across Android, iOS, Windows, and Linux with a decade-long track record. Follow and request early access to Wonek (pre-release for iPhone, iPad, Mac, and Apple Watch) when you want high-success direct P2P calls across 4G/5G CGNAT over QUIC, resumable multi-gigabyte P2P file transfers, Apple Watch calling & Push-to-Talk, real-time CRDT documents, a 5-view shared calendar, and separate Personal/Work profiles.

**Table 1: Core Feature & Collaboration Matrix — Wonek vs Signal**

| Capability | Wonek (Pre-Release · Apple Ecosystem) | Signal |
| --- | --- | --- |
| 1:1 & Group E2EE Messaging | Default MLS (RFC 9420) E2EE with rich text, code & math | Default Signal Protocol (Double Ratchet / Sender Keys) |
| Voice, Video & Screen Sharing | E2EE HD calls, PiP, Opus AEC, native iPhone/iPad/Mac screen share | E2EE voice/video calls; desktop screen sharing |
| Push-to-Talk (PTT) & Apple Watch | 1:1 & group E2EE PTT plus dedicated Apple Watch calling/audio | Async voice notes only; no native standalone watchOS calling app |
| Large File Transfers | Direct P2P file & album transfer with chunk-level resumption | Cloud attachment upload capped around 100 MB per file |
| Collaborative Docs & Shared Calendar | Built-in Yjs/Yrs CRDT offline-capable docs + 5-view Calendar | Not included (requires external apps) |
| Personal & Work Profile Separation | Built-in Personal and Work contexts under one account | Single flat inbox per phone number |

**Table 2: Cryptography, Wire Transport & NAT Traversal Specs**

| Technical Layer | Wonek | Signal |
| --- | --- | --- |
| End-to-End Encryption Standard | IETF MLS (RFC 9420) in native Rust core + Noise QR linking | Signal Protocol (X3DH / PQXDH + Double Ratchet) |
| Group Key Update Scaling | O(log N) asynchronous TreeKEM updates across devices | Pairwise + Sender Keys distribution |
| Wire Transport Protocol | Native QUIC / WebTransport with mandatory TLS 1.3 | TCP/TLS WebSockets for chat + WebRTC ICE for calls |
| Mobile 4G/5G CGNAT Call Routing | Proprietary port-prediction NAT traversal for high-rate direct P2P | Standard WebRTC ICE/STUN; relays calls when CGNAT blocks ICE |
| Strict Firewall & Offline Handling | Latency-measured encrypted relay fallback + ciphertext offline queue | Signal TURN relays + encrypted server message queue |

**Table 3: Availability, Ecosystem & Best-Fit Scenarios**

| Scenario / Requirement | Better Fit | Why |
| --- | --- | --- |
| Availability today across Android, Windows & Linux | Signal | Signal is live on all major mobile and desktop OSes; Wonek is in Apple pre-release |
| Low-latency mobile-to-mobile calls across 4G/5G CGNAT | Wonek | Smart port-prediction P2P avoids unnecessary TURN relay detours |
| Sending multi-gigabyte video shoots or RAW albums | Wonek | Direct P2P streaming with chunk-level resumption avoids 100 MB caps |
| Wrist Push-to-Talk & co-editing private specs/calendars | Wonek | Includes watchOS audio/PTT, CRDT docs, and Personal/Work profiles |
| Minimalist text-first activist chat with Android contacts | Signal | Focused purely on messaging and calls across every smartphone OS |

#### Cryptographic Evolution: IETF MLS (RFC 9420) Alongside QUIC
Signal pioneered modern consumer E2EE with the Double Ratchet, which excels at two-party chats. As users add iPads, Macs, and Apple Watches—and collaborate in multi-person rooms—Wonek adopts the newer IETF Messaging Layer Security (MLS, RFC 9420) standard inside a dedicated Rust cryptographic core, updating group and multi-device secrets in logarithmic O(log N) steps.

Underneath MLS, Wonek replaces legacy TCP WebSockets with native QUIC / WebTransport, adding mandatory TLS 1.3 transport encryption without head-of-line blocking.

#### Direct P2P Across Mobile CGNAT & Resumable Large Files
On cellular 4G/5G networks, standard WebRTC STUN/ICE frequently fails against Carrier-Grade NAT and routes calls through central relays—or forces users to enable 'Always Relay Calls' at the cost of higher latency. Wonek's proprietary port-prediction NAT traversal establishes direct peer-to-peer links across mobile CGNAT at a high success rate, falling back to latency-measured encrypted relays only when strict firewalls block UDP.

That direct QUIC pipe also powers chunk-resumable P2P file transfers, removing frustrating 100 MB attachment ceilings.

#### From Pure Chat to an Encrypted Personal & Work Workspace
Even Signal users often end up pasting links to unencrypted cloud docs and calendars to plan trips or sprints. Wonek integrates offline-capable Yjs/Yrs CRDT documents, a 5-view shared calendar, Push-to-Talk, Apple Watch support, and separate Personal/Work profiles under one roof.

#### Frequently Asked Questions
- **Is Wonek trying to replace Signal on Android?** Wonek is currently focused on native Apple platforms—iPhone, iPad, Mac, and Apple Watch—where it is in pre-release preparation. Signal remains an excellent choice whenever you need Android, Windows, or Linux support.
- **Can Wonek servers read messages or calls when a relay is used?** No. All messages, calls, screen shares, and files are end-to-end encrypted on client devices using MLS (RFC 9420) on top of QUIC TLS 1.3. Relays and offline queues handle only opaque ciphertext.
- **How can I join the Wonek early-access beta?** Email support@wonek.com with the Apple devices you use (iPhone, iPad, Mac, Apple Watch) to request early-access updates from Arte Soft EOOD.

### Wonek vs WhatsApp: Zero Ad-Ecosystem Metadata, QUIC P2P & Work Profiles
URL: https://wonek.com/compare/wonek-vs-whatsapp/

WhatsApp encrypts message bodies, yet operates inside Meta's social and business advertising ecosystem—without a native standalone Apple Watch calling app, collaborative documents, or clean Personal/Work profile switching inside one installation.

**Direct Answer / Verdict:** Keep WhatsApp when you must reach its massive global network across iOS and Android. Request early access to Wonek (pre-release for iPhone, iPad, Mac, and Apple Watch) when you want an independent European E2EE platform by Arte Soft EOOD with zero ad profiling, high-success direct P2P calls over QUIC, chunk-resumable large file transfers, Apple Watch voice/PTT, CRDT docs, a shared calendar, and isolated Personal/Work profiles.

**Table 1: Core Feature Matrix — Wonek vs WhatsApp**

| Capability | Wonek (Pre-Release) | WhatsApp (Meta) |
| --- | --- | --- |
| Business Model & Ad Ecosystem | Independent software by Arte Soft EOOD; zero ad-tech graph | Owned by Meta; business messaging & ecosystem telemetry |
| Rich Technical Formatting | Rich text, inline code, math formulas, edits & pins | Basic bold/italic/code blocks; no native LaTeX math |
| Apple Watch Support | Native Apple Watch calling, audio & Push-to-Talk | Notification mirroring only — no full standalone Watch call app |
| Large File Sharing | Direct P2P transfer with chunk-level resumption | Cloud-relayed attachments capped at 2 GB |
| Collaborative Docs & Calendar | Real-time Yjs/Yrs CRDT docs + 5-view Shared Calendar | None built in |
| Personal & Work Separation | Dedicated Personal + Work profiles under one account | Requires separate WhatsApp Business app & second number |

**Table 2: Security, Backup & Network Transport Architecture**

| Architecture Layer | Wonek | WhatsApp |
| --- | --- | --- |
| End-to-End Encryption | MLS (RFC 9420) in native Rust core | Signal-derived pairwise + Sender Keys |
| Multi-Device Key Enrollment | Direct Noise-protocol authenticated QR handshake | Linked companion device sync via WhatsApp servers |
| Transport Protocol | QUIC / WebTransport with mandatory TLS 1.3 | Custom TCP/Noise socket + VoIP/WebRTC media |
| Mobile CGNAT Call Path | Proprietary port-prediction NAT traversal for direct P2P | Frequently falls back to Meta relay servers on 4G/5G |
| Offline Delivery Queue | Opaque MLS ciphertext queued until device wakes | Encrypted store-and-forward queue on Meta infrastructure |

**Table 3: Best Fit by Communication Scenario**

| Use Case | Recommended Platform | Reason |
| --- | --- | --- |
| Messaging international contacts on Android & iOS today | WhatsApp | Universal global address-book reach already installed everywhere |
| Separating client projects from family chats on one iPhone | Wonek | Built-in Personal and Work profiles under a single phone-verified account |
| Co-editing private notes & shared schedules inside chat | Wonek | Native offline-capable CRDT documents and 5-view shared calendar |
| Direct device-to-device HD calls & multi-GB files on 5G | Wonek | Port-predicted QUIC P2P minimizes relay detours and resumes interrupted chunks |
| Quick Push-to-Talk bursts from Apple Watch | Wonek | First-class watchOS audio, calling, and 1:1/group PTT |

#### Zero Ad-Graph Incentives vs Social Conglomerate Infrastructure
While WhatsApp protects message text in transit, its parent company's core business revolves around commercial engagement and business metadata. Many teams and families want private communication built by an independent software studio whose incentives align purely with product quality.

Published by Arte Soft EOOD in Sofia, Bulgaria, Wonek contains zero advertising SDKs and pairs client-side MLS (RFC 9420) encryption with QUIC TLS 1.3 transport.

#### Native Apple Watch, Mac, iPad & iPhone Cohesion
Apple Watch owners have waited years for a first-party WhatsApp calling experience on watchOS. Wonek treats iPhone, iPad, Mac, and Apple Watch as first-class peers enrolled via Noise QR verification—bringing voice calls, audio messages, and Push-to-Talk right to your wrist.

#### One Account, Two Clean Worlds: Personal & Work
Instead of forcing consultants and founders to carry a second SIM card for WhatsApp Business, Wonek isolates Personal and Work/Team profiles—each with its own CRDT documents, shared calendar views, and screen-share calls.

#### Frequently Asked Questions
- **Does Wonek use my contact graph for advertising?** Never. Wonek has zero advertising trackers and zero ad-targeting business model.
- **Do I need a second phone number for a Work profile in Wonek?** No. One phone-verified Wonek account supports separate Personal and Work/Team profile contexts.
- **When can I install Wonek on my iPhone and Mac?** Wonek is currently in pre-release preparation for iPhone, iPad, Mac, and Apple Watch. Contact support@wonek.com to request early access.

### Wonek vs Telegram: Default MLS End-to-End Encryption vs Cloud-by-Default Chats
URL: https://wonek.com/compare/wonek-vs-telegram/

Telegram is famous for fast UI and massive public channels, but many users are surprised to learn that regular Telegram chats and all Telegram group chats are NOT end-to-end encrypted—they are stored decryptably in Telegram's cloud. Wonek delivers modern multi-device speed with mandatory MLS E2EE by default everywhere.

**Direct Answer / Verdict:** Use Telegram for public broadcast channels, bots, and massive open communities across all OSes. Choose Wonek (in pre-release for iPhone, iPad, Mac, and Apple Watch) when you want fast multi-device sync WITHOUT surrendering group and desktop chats to cloud decryption—backed by IETF MLS (RFC 9420) E2EE, QUIC P2P calls, chunk-resumable P2P files, CRDT docs, and shared calendars.

**Table 1: Encryption & Feature Matrix — Wonek vs Telegram**

| Feature | Wonek (Pre-Release) | Telegram |
| --- | --- | --- |
| Default 1:1 Chat Encryption | End-to-end encrypted by default (MLS RFC 9420) | Cloud-encrypted only unless manual 'Secret Chat' opened |
| Group Chat End-to-End Encryption | Yes — full MLS E2EE for all groups | No — Telegram group chats have no E2EE option |
| Multi-Device E2EE Sync (iPad + Mac) | Yes — all linked Apple devices sync E2EE via MLS | Secret Chats locked to single device; cloud chats readable by server |
| Group Voice, Video & Screen Share E2EE | End-to-end encrypted 1:1 & group calls + screen share | 1:1 calls E2EE; large group voice chats use server clusters |
| Large File Transfer Architecture | Direct P2P over QUIC with chunk-level resumption | Uploaded to Telegram cloud servers (2 GB free / 4 GB paid) |
| Built-in Collaborative Docs & Calendar | Yjs/Yrs CRDT docs + 5-view Shared Calendar | No native CRDT doc editor or multi-view calendar |

**Table 2: Cryptographic Standard & Transport Comparison**

| Technical Dimension | Wonek | Telegram |
| --- | --- | --- |
| Cryptographic Protocol | Open IETF Standard MLS (RFC 9420) + Noise QR + TLS 1.3 | Custom MTProto 2.0 protocol |
| Wire Transport | QUIC / WebTransport (zero TCP head-of-line blocking) | Primarily TCP / custom obfuscated MTProto transport |
| Call NAT Traversal | Proprietary port-prediction P2P across mobile CGNAT | Standard P2P or Telegram relay servers |
| Server Plaintext Exposure | Zero — relays & offline queues hold opaque ciphertext only | Server holds keys to decrypt all standard & group cloud chats |
| Push-to-Talk & Apple Watch | 1:1 & group E2EE PTT + Apple Watch calling/audio | Voice notes; legacy Watch support discontinued/limited |

**Table 3: When to Pick Wonek vs Telegram**

| Use Case | Best Choice | Key Difference |
| --- | --- | --- |
| Following 50,000-member public news channels & bots | Telegram | Built as a public social broadcast network across every OS |
| Private family or team group chats synced across iPhone & Mac | Wonek | Telegram groups are never E2EE; Wonek encrypts all groups end-to-end via MLS |
| Sending confidential archives without cloud server retention | Wonek | Direct P2P streaming between devices rather than permanent cloud storage |
| Sharing inline code, math formulas & co-edited specs | Wonek | Includes math/code formatting plus live CRDT collaborative documents |
| Isolating Work channels from Personal threads | Wonek | Dedicated Personal and Work profile switching |

#### Solving Telegram's Multi-Device vs Privacy Trade-Off
Historically, Telegram argued that cloud storage was necessary so your iPad and Mac could see your group history seamlessly—leaving 'Secret Chats' trapped on a single phone and completely unavailable for groups. IETF Messaging Layer Security (MLS, RFC 9420) eliminates that compromise.

In Wonek, every enrolled Apple device joins the MLS cryptographic tree via authenticated Noise QR linking. Your iPhone, iPad, Mac, and Apple Watch stay seamlessly synchronized while servers never possess keys to read a single 1:1 or group message.

#### Direct P2P Files Instead of Cloud Storage Vaults
Uploading sensitive project archives or family videos to a permanent cloud chat means copies reside on remote data centers indefinitely. Wonek transfers large files and photo albums directly peer-to-peer over QUIC with chunk-level resumption—delivering fast speeds without leaving plaintext on third-party servers.

#### Built-In Workspace Tools Without Third-Party Bots
Rather than relying on unencrypted third-party webhook bots for scheduling and notes, Wonek ships native CRDT collaborative documents and a 5-view shared calendar inside the encrypted boundary.

#### Frequently Asked Questions
- **Are Telegram group chats end-to-end encrypted?** No. Telegram's Secret Chats only work 1:1 on a single device; all Telegram group chats are cloud chats stored on Telegram's infrastructure. Wonek encrypts both 1:1 and group chats end-to-end by default using MLS (RFC 9420).
- **Does Wonek use a custom homegrown encryption cipher?** No. Wonek uses standardized IETF MLS (RFC 9420), Noise-protocol device enrollment, and TLS 1.3 over QUIC.
- **Is Wonek live on the App Store yet?** Wonek is in pre-release preparation for iPhone, iPad, Mac, and Apple Watch. Contact support@wonek.com for early-access inquiries.

### Wonek vs Apple FaceTime: Full E2EE Messaging, Direct QUIC P2P, PTT & Workspace
URL: https://wonek.com/compare/wonek-vs-facetime/

FaceTime is preinstalled on every Apple device for quick video calls and SharePlay, yet it has no persistent text chat, file sharing, collaborative notes, or Work/Personal separation—and relies on Apple's relay infrastructure when cellular NAT gets tough.

**Direct Answer / Verdict:** Use FaceTime for instant zero-install calls with anyone already using an Apple ID. Request early access to Wonek when you want a complete end-to-end encrypted communication workspace across iPhone, iPad, Mac, and Apple Watch—combining low-latency QUIC P2P audio/video and screen sharing with rich messaging, chunk-resumable P2P file transfers, Push-to-Talk, CRDT docs, and shared calendars.

**Table 1: Communication Capabilities — Wonek vs FaceTime**

| Capability | Wonek (Pre-Release) | Apple FaceTime |
| --- | --- | --- |
| 1:1 & Group E2EE Voice / Video | Yes — Opus AEC, noise suppression, HD video & PiP | Yes — preinstalled Apple E2EE audio & video |
| Screen Sharing (iPhone, iPad, Mac) | Yes — native E2EE screen sharing | Yes — built into iOS, iPadOS & macOS |
| Persistent Rich Messaging | Full MLS E2EE chat (code, math, edits, pins, timers) | None (must jump to separate Messages app) |
| Large Direct P2P File Transfer | Yes — chunk-resumable direct P2P files & albums | None inside FaceTime |
| Push-to-Talk (1:1 & Group) + Watch | 1:1 & group E2EE PTT + Apple Watch calling/audio | FaceTime Audio on Watch; separate 1:1-only Walkie-Talkie |
| Collaborative Docs & Shared Calendar | Built-in Yjs/Yrs CRDT docs + 5-view Calendar | None built in |

**Table 2: Transport, NAT Traversal & Identity Architecture**

| Technical Aspect | Wonek | Apple FaceTime |
| --- | --- | --- |
| Wire & Media Transport | Native QUIC / WebTransport (TLS 1.3) | Apple ICE / STUN / Cloud Relay media transport |
| 4G/5G Mobile CGNAT Routing | Proprietary port-prediction NAT traversal for high-rate direct P2P | Frequently transitions onto Apple relay servers behind CGNAT |
| End-to-End Encryption Layer | IETF MLS (RFC 9420) in dedicated Rust core | Apple Identity Services (IDS) E2EE |
| Personal vs Work Separation | Isolated Personal and Work profiles under one account | Tied directly to your single device Apple Account |
| Multi-Device Enrollment | Explicit Noise QR device linking | Automatic across all devices signed into same iCloud |

**Table 3: Best Fit on Apple Devices**

| Scenario | Recommended Tool | Why |
| --- | --- | --- |
| Calling a grandparent on iPhone with zero app setup | FaceTime | Preinstalled out of the box on every iPhone and iPad |
| Keeping work calls separate from your personal Apple ID | Wonek | Dedicated Work profile without sharing personal iCloud email/number |
| Screen sharing code while co-editing specs & sending 5 GB builds | Wonek | Combines calls, screen share, CRDT docs, inline code, and P2P files |
| Group Push-to-Talk coordination from Apple Watch | Wonek | Supports encrypted group PTT channels beyond 1:1 Walkie-Talkie |
| Low-latency calls across international 4G/5G CGNAT networks | Wonek | Port-predicted QUIC P2P establishes direct peer paths more often |

#### Why Calls Need Context Before and After Hanging Up
A FaceTime call starts and ends in a vacuum: any links, code snippets, files, follow-up notes, or calendar dates discussed on the call have to be scattered across Messages, AirDrop, Notes, and Calendar afterward.

Wonek keeps the call, screen share, persistent MLS-encrypted thread, chunk-resumable P2P file drops, CRDT document, and 5-view shared calendar together in one coherent conversation.

#### Work Calls Without Blending Into Your Personal iCloud
Taking professional calls on FaceTime exposes your personal Apple ID or phone number into your personal call log. Wonek separates Personal and Work contexts cleanly inside one app.

#### QUIC Transport & Smart Mobile CGNAT Traversal
Built on QUIC / WebTransport with proprietary port-prediction NAT traversal, Wonek targets direct peer-to-peer links across mobile CGNAT networks and smooth Wi-Fi-to-5G transitions.

#### Frequently Asked Questions
- **Does Wonek support Picture-in-Picture and screen sharing like FaceTime?** Yes. Wonek supports Picture-in-Picture (PiP) multitasking and native E2EE screen sharing across iPhone, iPad, and Mac.
- **Do I have to sign into the same iCloud account on a work Mac to use Wonek?** No. Wonek links authorized devices via authenticated Noise QR codes independently of iCloud account sign-in.
- **How do I get early access to Wonek?** Reach out to support@wonek.com to join the pre-release list for iPhone, iPad, Mac, and Apple Watch.

### Wonek vs Apple Messages (iMessage): QUIC P2P, CRDT Docs, PTT & Work Profiles
URL: https://wonek.com/compare/wonek-vs-imessage/

Apple Messages is effortless for everyday texting on iPhone, but its end-to-end encryption depends on whether every participant enables Advanced Data Protection for iCloud—and it lacks inline code/math, chunk-resumable multi-GB P2P files, group PTT, CRDT docs, and Work profile isolation.

**Direct Answer / Verdict:** Keep iMessage for casual everyday texts with friends and SMS/RCS carrier contacts. Request early access to Wonek when you want strict client-side MLS (RFC 9420) encryption unaffected by cloud backup defaults, direct QUIC P2P calls and multi-gigabyte file transfers, inline code & math formatting, Push-to-Talk, collaborative CRDT documents, shared calendars, and Personal/Work profiles.

**Table 1: Messaging & Productivity Matrix — Wonek vs iMessage**

| Capability | Wonek (Pre-Release) | Apple Messages (iMessage) |
| --- | --- | --- |
| Rich Text, Code & Math Formulas | Full rich formatting, inline code, math formulas, edits & pins | Basic text effects, bold/italic; no native code blocks or LaTeX math |
| Disappearing Message Timers | Built-in per-conversation disappearing message timers | No automatic expiring message timer for standard threads |
| Large File Transfers | Direct P2P streaming with chunk-level resumption | iCloud-relayed attachments with size limits & slow re-uploads |
| Push-to-Talk (PTT) | 1:1 and group E2EE live Push-to-Talk on iPhone, Mac & Watch | Asynchronous audio messages only |
| Built-in Collaborative Docs | Offline-capable Yjs/Yrs CRDT documents inside workspace | Requires switching to Apple Notes via iCloud sharing |
| Personal & Work Profiles | Clean Personal and Work separation under one account | Single Apple ID inbox mixes everything |

**Table 2: Encryption Boundaries & Network Architecture**

| Security / Network Layer | Wonek | Apple iMessage |
| --- | --- | --- |
| E2EE Protocol | IETF MLS (RFC 9420) in native Rust core | Apple PQ3 E2EE between Apple devices |
| Cloud Backup Key Caveat | No server-escrowed chat backups; Noise QR device linking | Standard iCloud Backup stores recoverable key unless ADP enabled by all |
| SMS / Carrier Fallback Downgrade | Never downgrades E2EE messages to unencrypted carrier SMS | Can fall back to unencrypted SMS/RCS when data fails unless disabled |
| Transport & Call Stack | Unified QUIC / WebTransport + port-predicted CGNAT P2P | APNs + separate FaceTime framework for calls |
| Shared Calendar Integration | 5-view Shared Calendar (Day, Multi-Day, Month, Year, List) | Separate Apple Calendar app |

**Table 3: Best Fit Across Everyday & Technical Workflows**

| Workflow | Recommended App | Why |
| --- | --- | --- |
| Carrier SMS codes & texting any iPhone number instantly | Apple Messages | Built into iOS telephony and carrier routing |
| Guaranteed E2EE even if a contact uses default iCloud settings | Wonek | MLS keys stay strictly on Noise-enrolled devices—no cloud backup escrow |
| Engineering & research chats with code, math & multi-GB files | Wonek | Native code/math rendering plus chunk-resumable direct P2P file transfers |
| Separating work team rooms from personal family texts | Wonek | Switch between Personal and Work profiles in one app |
| Self-destructing sensitive messages | Wonek | Built-in disappearing message timers |

#### Eliminating the Cloud-Backup Loophole & SMS Downgrades
Apple upgraded iMessage with strong PQ3 encryption in transit, yet in a 10-person group chat, if even one participant uses standard iCloud Backup without Advanced Data Protection enabled, a copy of the conversation backup key can reside in cloud storage. Worse, weak cellular coverage can silently downgrade blue bubbles to unencrypted carrier SMS.

Wonek never downgrades to carrier SMS and never uploads unencrypted backup keys—linking your Mac, iPad, and Watch strictly through authenticated Noise QR handshakes.

#### Engineered for Technical Teams & Power Users Too
With inline code, mathematical formula rendering, pinned messages, disappearing timers, CRDT collaborative docs, and chunk-resumable P2P file transfers, Wonek handles serious technical and creative collaboration that outgrows casual bubble texting.

#### Calls, PTT, Docs, and Calendar in One Native App
Instead of bouncing across four separate system apps, Wonek unifies voice/video calls, screen sharing, Push-to-Talk, docs, and a 5-view calendar over one QUIC/MLS engine.

#### Frequently Asked Questions
- **Can Wonek accidentally send an encrypted message as unencrypted SMS?** No. Every message in Wonek travels exclusively through its MLS (RFC 9420) end-to-end encrypted pipeline over QUIC TLS 1.3; if a recipient is offline, ciphertext waits in Wonek's encrypted queue.
- **Does Wonek support mathematical formulas and code formatting?** Yes. Wonek supports rich text formatting, inline code, and math formulas alongside edits, replies, and pinned messages.
- **Does Wonek require enabling iCloud on a company MacBook?** No. You link your Mac directly via an authenticated Noise QR handshake from your iPhone without signing your personal Apple Account into a work machine.

### Wonek vs Discord: End-to-End Encrypted Voice, Screen Share & Direct P2P Files
URL: https://wonek.com/compare/wonek-vs-discord/

Discord popularized instant voice channels, Push-to-Talk, and screen sharing, yet every text message, code snippet, and uploaded file in Discord is stored unencrypted on Discord's cloud servers—and attachments hit strict paywall size limits. Wonek brings low-latency voice, PTT, and screen sharing into a fully end-to-end encrypted native Apple app.

**Direct Answer / Verdict:** Choose Discord for huge public gaming servers, streaming communities, and cross-platform bot ecosystems. Request early access to Wonek (for iPhone, iPad, Mac, and Apple Watch) when your private group, startup, or friend circle wants low-latency Opus voice, Push-to-Talk, HD screen sharing, and multi-GB P2P file transfers protected end-to-end—including text chats, files, CRDT docs, and shared calendars.

**Table 1: Privacy & Collaboration Matrix — Wonek vs Discord**

| Capability | Wonek (Pre-Release) | Discord |
| --- | --- | --- |
| Text Chat & History Encryption | 100% end-to-end encrypted (MLS RFC 9420) | Not E2EE — all text & DMs readable on Discord servers |
| Voice, Video & Screen Share Security | Default MLS E2EE + QUIC TLS 1.3 | DAVE audio/video E2EE rolling out; servers still route all media |
| File Upload Limits | Direct P2P streaming with chunk resumption (no tiny MB wall) | 10 MB free limit (requires paid Nitro up to 500 MB) |
| Desktop App Footprint on Mac | Lightweight native macOS + Rust core | Heavy Electron wrapper consuming high RAM/battery |
| Push-to-Talk & Apple Watch | Native iPhone, iPad, Mac & Apple Watch E2EE PTT | Desktop/mobile PTT; no native standalone Apple Watch app |
| Docs & Calendar | Built-in CRDT collaborative docs + 5-view Calendar | Forum/text threads & basic event banners only |

**Table 2: Media Path, Latency & Cryptographic Specs**

| Technical Layer | Wonek | Discord |
| --- | --- | --- |
| Media Network Path | Direct device-to-device P2P primary + encrypted relay fallback | 100% routed through centralized Discord cloud voice servers |
| Transport Protocol | QUIC / WebTransport (TLS 1.3) | WebSockets over TCP + WebRTC/RTP to cloud SFU |
| Audio Pipeline | Opus codec with AEC & noise suppression | Opus codec with Krisp/standard suppression |
| Cryptographic Scope | Messages, calls, screen share, files & CRDT docs all E2EE | Text, attachments, embeds & pins stored in plaintext cloud DB |
| Profile Contexts | Clean Personal and Work profiles in one account | Single account list across gaming & work servers |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended Platform | Why |
| --- | --- | --- |
| 10,000-member public gaming or open-source community | Discord | Role hierarchies, bots, and cross-platform web/Windows/Android reach |
| Private pair-programming screen shares & code snippets | Wonek | Both screen pixels AND pasted inline code/secrets stay strictly E2EE |
| Sending 3 GB video edits or RAW photo folders to friends | Wonek | Direct chunk-resumable P2P avoids Discord's 10 MB / Nitro paywalls |
| Battery-friendly native Mac & Apple Watch voice/PTT | Wonek | Native Apple architecture instead of background Electron overhead |
| Co-planning trips or sprints with private docs & calendars | Wonek | Includes offline-capable CRDT docs and 5-view shared calendar |

#### Why Encrypting Voice While Leaving Text Unencrypted Isn't Enough
While Discord introduced audio/video E2EE initiatives for calls, every single direct message, private server channel, pasted credential, and uploaded PDF remains stored unencrypted in Discord's cloud databases.

Wonek encrypts the entire workspace end-to-end under MLS (RFC 9420): text, inline code, math formulas, voice, video, PTT, screen shares, P2P files, and CRDT documents.

#### No 10 MB Attachment Walls—Direct P2P Over QUIC
Discord caps free file uploads at a tiny 10 MB because Discord pays to host every file in cloud buckets. Because Wonek transfers files directly peer-to-peer over QUIC with chunk-level resumption, you can send large builds, videos, and photo albums without artificial megabyte paywalls.

#### Native Apple Efficiency vs Heavy Electron Wrappers
Keeping an Electron chat app running all day drains MacBook battery life. Wonek pairs native Apple UI with a lean Rust cryptographic and QUIC networking core across Mac, iPad, iPhone, and Apple Watch.

#### Frequently Asked Questions
- **Are Discord text messages and DMs end-to-end encrypted?** No. Discord text channels and direct messages are stored on Discord's cloud servers without end-to-end encryption. Wonek encrypts all messages, files, and calls end-to-end via MLS (RFC 9420).
- **Does Wonek have Push-to-Talk like Discord?** Yes. Wonek supports 1:1 and group E2EE Push-to-Talk across Mac, iPhone, iPad, and Apple Watch.
- **Can I share large video files without hitting a 10 MB error?** Yes. Wonek uses direct peer-to-peer file transfers with chunk-level resumption over QUIC.

### Wonek vs Slack: True Client-Side E2EE Team Chat, Direct P2P Calls & CRDT Docs
URL: https://wonek.com/compare/wonek-vs-slack/

Slack shaped modern team communication, yet every message, Canvas note, and uploaded file in Slack is stored on cloud servers without client-side end-to-end encryption. Wonek gives Apple-first teams fast rich chat, live calls, screen sharing, CRDT docs, and a built-in shared calendar with true zero-knowledge MLS E2EE.

**Direct Answer / Verdict:** Choose Slack when your company relies on hundreds of SaaS webhook integrations across Windows, Linux, Android, and browsers. Request early access to Wonek when your founding team, agency, legal/research group, or engineering crew on Apple devices wants client-side MLS E2EE by default, low-latency direct P2P calls and screen shares, chunk-resumable P2P file transfers, offline-capable CRDT docs, and an integrated 5-view calendar.

**Table 1: Workspace & Security Matrix — Wonek vs Slack**

| Capability | Wonek (Pre-Release) | Slack |
| --- | --- | --- |
| Client-Side End-to-End Encryption | Yes — default MLS (RFC 9420) for all chats, calls & docs | No E2EE (even Enterprise EKM still decrypts in Slack cloud RAM) |
| Rich Technical Messaging | Rich text, inline code, math formulas, edits, pins & timers | Markdown/code blocks, threads, pins (no native LaTeX math) |
| Voice, Video & Screen Sharing | Direct P2P E2EE calls + screen share across iPhone, iPad & Mac | Cloud SFU Huddles (not end-to-end encrypted) |
| Collaborative Documents | Offline-capable Yjs/Yrs CRDT docs synced E2EE | Slack Canvas stored in cloud plaintext |
| Built-in Team Calendar | Native 5-view Shared Calendar (Day, Multi-Day, Month, Year, List) | Requires external Google/Outlook Calendar connector |
| Large File Sharing | Direct P2P transfer with chunk-level resumption | Cloud bucket uploads counted against workspace storage quota |

**Table 2: Architecture, Native Performance & Boundaries**

| Technical Dimension | Wonek | Slack |
| --- | --- | --- |
| Cryptographic Key Custody | Keys stay strictly on user devices (Rust MLS + Noise QR) | Slack cloud holds keys or decrypts payloads for indexing/AI |
| Network Transport | QUIC / WebTransport (TLS 1.3) + port-predicted CGNAT P2P | HTTPS / TCP WebSockets + cloud WebRTC SFUs |
| Desktop & Watch Experience | Native macOS, iOS, iPadOS + Apple Watch calling/PTT | Electron desktop app; no Apple Watch calling/PTT |
| Personal + Work Separation | Dedicated Personal & Work contexts in one app | Separate workspace sign-ins; work-only focus |
| Offline Document Editing | Conflict-free Yjs/Yrs CRDT local edits merge on reconnect | Limited offline Canvas support |

**Table 3: Best Fit for Teams & Organizations**

| Team Profile | Recommended Platform | Why |
| --- | --- | --- |
| 500-person cross-OS enterprise using 80 SaaS bots | Slack | Deep third-party SaaS app directory and Windows/Android/Web parity |
| Security, executive, R&D, legal, or founder rooms on Apple gear | Wonek | True client-side MLS E2EE keeps IP, code, and M&A talk off cloud servers |
| Field + desk teams needing Apple Watch Push-to-Talk | Wonek | Instant E2EE wrist & mobile PTT alongside rich desktop chat |
| Sharing multi-gigabyte builds, datasets, or video renders | Wonek | Direct P2P chunk-resumable transfers consume zero cloud workspace quota |
| Teams wanting chat + docs + calendar without 3 cloud subscriptions | Wonek | All three live natively inside one E2EE workspace |

#### Why Enterprise Key Management (EKM) Is Not End-to-End Encryption
Even on Slack's highest enterprise tiers, Slack's servers must decrypt your messages in memory to index search, generate previews, and run server-side features—meaning a cloud breach, subpoena, or misconfigured export exposes plaintext history.

Wonek encrypts messages, calls, CRDT documents, and files on your Apple device before a single byte hits the wire. Neither Wonek relays nor offline message queues ever see plaintext.

#### Huddles That Travel Directly Peer-to-Peer
Instead of routing a quick screen-share code review between two engineers in the same city through a distant cloud SFU, Wonek's QUIC + port-prediction NAT traversal connects peers directly whenever possible for snappier cursor response and sharper text.

#### Docs and Shared Calendars Without Leaving the Encrypted Boundary
With Yjs/Yrs CRDT collaborative documents and five built-in calendar views right beside Work profile conversations, teams stop leaking confidential roadmaps into external cloud tabs.

#### Frequently Asked Questions
- **Does Slack offer true end-to-end encryption for channels or Huddles?** No. Slack encrypts data in transit and at rest on its servers, where Slack infrastructure can decrypt it. Wonek enforces client-side MLS (RFC 9420) end-to-end encryption across all chats, calls, screen shares, and docs.
- **Can teammates edit Wonek documents offline on a flight?** Yes. Wonek's collaborative documents use Yjs/Yrs CRDTs so offline edits merge cleanly without conflicts once back online.
- **How can our Apple-based team test Wonek?** Wonek is in pre-release preparation for Mac, iPhone, iPad, and Apple Watch. Email support@wonek.com to inquire about team early access.

### Wonek vs Microsoft Teams: Lightweight Native Apple Speed, QUIC P2P & Default E2EE
URL: https://wonek.com/compare/wonek-vs-microsoft-teams/

Microsoft Teams bundles corporate IT compliance for Windows shops, but on macOS and iOS it feels heavy—and group chats, shared SharePoint files, and most multi-person meetings are not end-to-end encrypted by default. Wonek is purpose-built for fast, native Apple performance with mandatory MLS E2EE everywhere.

**Direct Answer / Verdict:** Stick with Microsoft Teams if your organization mandates Microsoft 365 Windows IT governance, PSTN phone systems, and 300-person corporate town halls. Request early access to Wonek when your Mac, iPad, iPhone, and Apple Watch team wants instant native responsiveness, default MLS (RFC 9420) E2EE across all chats, calls, screen shares, and CRDT docs, plus direct QUIC P2P media and resumable file transfers.

**Table 1: Security & Experience Matrix — Wonek vs Microsoft Teams**

| Capability | Wonek (Pre-Release) | Microsoft Teams |
| --- | --- | --- |
| Default Chat & Channel E2EE | Yes — 100% MLS (RFC 9420) E2EE | No — stored in Microsoft cloud / Exchange / SharePoint |
| Call & Screen Share E2EE | Default E2EE for 1:1 & group calls + screen sharing | Optional opt-in 1:1 E2EE (disables several features); meetings require Premium |
| macOS & iOS App Responsiveness | Lean native Apple UI + Rust core | Heavy multi-gigabyte desktop footprint & complex tenant switching |
| Large File Sharing | Direct P2P over QUIC with chunk-level resumption | Uploads into OneDrive / SharePoint cloud storage |
| Collaborative Notes & Calendar | E2EE Yjs/Yrs CRDT docs + built-in 5-view Calendar | Loop / Word / Exchange Calendar stored in Microsoft cloud |
| Push-to-Talk & Apple Watch | 1:1 & group E2EE PTT across iPhone, Mac & Apple Watch | Walkie Talkie limited to Frontline mobile configurations |

**Table 2: Network & Cryptographic Architecture**

| Technical Layer | Wonek | Microsoft Teams |
| --- | --- | --- |
| Cryptographic Core | Native Rust MLS (RFC 9420) + Noise QR device linking | Cloud TLS/at-rest encryption; narrow opt-in E2EE |
| Wire Transport | QUIC / WebTransport (TLS 1.3) | HTTPS / WebSockets + Azure media relays/SFUs |
| Mobile CGNAT Call Path | Proprietary port-prediction NAT traversal for direct P2P | Routes most multi-party & enterprise calls via Azure relays |
| Tenant vs Profile Switching | Instant Personal & Work profile toggle in one account | Slow multi-tenant guest reloads |
| Offline Message Handling | Ciphertext-only server queue | Cloud mailbox storage |

**Table 3: Best Fit by Organization Type**

| Scenario | Recommended Tool | Why |
| --- | --- | --- |
| Windows-first enterprise tied to SharePoint & Outlook IT | Microsoft Teams | Bundled into existing Microsoft 365 corporate licensing |
| Mac & iPhone engineering, design, or executive teams | Wonek | Snappy native Apple experience without Microsoft tenant bloat |
| Confidential client advisory (legal, finance, security, M&A) | Wonek | Every chat, doc, screen share, and file is E2EE by default |
| Instant switching between Personal life & Work projects | Wonek | Clean Personal and Work profiles without guest-tenant sign-out loops |
| Sending multi-GB media directly without OneDrive sync delays | Wonek | Direct P2P streaming with chunk-level resumption |

#### Ending 'Guest Tenant' Friction on Apple Devices
Anyone who collaborates with external clients on a MacBook knows the pain of Microsoft Teams tenant switching, missed notifications across orgs, and sluggish startup times. Wonek is designed natively for Apple hardware with instant Personal and Work profile switching.

#### Default End-to-End Encryption—Not a Hidden IT Toggle
In Teams, enabling end-to-end encryption requires IT policy configuration, applies primarily to 1:1 calls or specific Premium tiers, and never covers standard channel chat or OneDrive files. Wonek makes MLS (RFC 9420) E2EE universal and automatic across chats, groups, calls, screen shares, files, and CRDT docs.

#### Direct QUIC P2P Speed Across Wi-Fi and 5G
With QUIC / WebTransport and smart port-prediction NAT traversal, Wonek connects peers directly whenever possible and transitions smoothly when you walk from office Wi-Fi onto 5G.

#### Frequently Asked Questions
- **Are Microsoft Teams chats end-to-end encrypted?** No. Teams chat messages and files are stored in Microsoft's cloud so compliance and search services can read them. Wonek encrypts all chats, files, docs, and calls end-to-end on client devices.
- **Does Wonek run natively on Apple Silicon Macs?** Yes. Wonek is engineered natively for Mac, iPhone, iPad, and Apple Watch backed by a compiled Rust cryptographic core.
- **Does Wonek include a calendar so we can plan calls?** Yes. Wonek includes a built-in 5-view Shared Calendar (Day, Multi-Day, Month, Year, and List) right alongside your conversations.

### Wonek vs Zoom: Always-On E2EE P2P Calling, Persistent Chat & Workspace vs Meeting Rooms
URL: https://wonek.com/compare/wonek-vs-zoom/

Zoom excels at scheduled 100-person webinars with external dial-in links, but its end-to-end encryption is an opt-in toggle that disables cloud features, and meetings vanish unless you buy into Zoom's cloud suite. Wonek delivers instant direct-P2P E2EE calling inside a persistent, zero-knowledge Apple workspace.

**Direct Answer / Verdict:** Choose Zoom for large external webinars, PSTN telephone dial-in bridges, and cross-OS client links. Request early access to Wonek when you want default end-to-end encrypted 1:1 and group HD video, Opus voice, and native screen sharing paired with persistent MLS chat, chunk-resumable P2P file transfers, Push-to-Talk, CRDT docs, and a 5-view shared calendar across iPhone, iPad, Mac, and Apple Watch.

**Table 1: Video, Messaging & Workspace Matrix — Wonek vs Zoom**

| Capability | Wonek (Pre-Release) | Zoom Workplace |
| --- | --- | --- |
| End-to-End Encryption Default | Always on by default (MLS RFC 9420) for calls, chat & files | Opt-in toggle for meetings; Team Chat E2EE requires Advanced enterprise setup |
| Call Initiation Friction | 1-tap call or PTT directly inside persistent E2EE thread | Meeting IDs, passcodes, waiting rooms & URL invites |
| Screen Sharing & PiP | Native E2EE screen share + PiP on iPhone, iPad & Mac | Desktop/mobile screen share (cloud-routed unless E2EE toggled) |
| Persistent Rich Chat & Files | Full MLS chat (code, math, pins) + resumable direct P2P files | In-meeting chat disappears unless using cloud Zoom Team Chat |
| Collaborative Docs & Calendar | Offline-capable Yjs/Yrs CRDT docs + 5-view Calendar (E2EE) | Zoom Docs & AI Companion process content in cloud |
| Apple Watch & Push-to-Talk | Apple Watch calling/audio + 1:1/group E2EE PTT | No standalone watchOS calling/PTT workflow |

**Table 2: Network Routing & Cryptographic Specs**

| Technical Dimension | Wonek | Zoom |
| --- | --- | --- |
| Primary Media Path | Direct device-to-device P2P over QUIC (even across CGNAT) | Primarily routed through Zoom cloud Multimedia Routers |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | Custom UDP/TCP/HTTPS Zoom media transport |
| Cryptographic Standard | Open IETF MLS (RFC 9420) in Rust core + Noise QR | Zoom custom/MLS-inspired opt-in meeting E2EE |
| 40-Minute Free Cutoff | No artificial 40-minute meetingroom cutoff architecture | 40-minute group limit on Zoom Basic free tier |
| Audio Processing | Opus codec with AEC & noise suppression | Zoom custom audio with background noise suppression |

**Table 3: Best Fit by Communication Scenario**

| Scenario | Recommended Platform | Why |
| --- | --- | --- |
| 200-attendee public webinar with browser/phone dial-in | Zoom | Purpose-built for large external broadcasts and PSTN dial-ins |
| Low-latency 1:1 & small-team E2EE calls across 4G/5G | Wonek | Direct port-predicted QUIC P2P cuts cloud routing lag |
| Ongoing team & family collaboration before/after calls | Wonek | Persistent MLS chat, CRDT docs, P2P files & calendar stay in one place |
| Quick spoken check-ins without scheduling a meeting link | Wonek | Instant 1:1 & group Push-to-Talk on iPhone, Mac & Watch |
| Zero-knowledge privacy where cloud servers never see media | Wonek | E2EE is mandatory—never an easily forgotten host checkbox |

#### Mandatory E2EE vs Easily Forgotten Meeting Checkboxes
In Zoom, end-to-end encryption must be explicitly enabled in account settings before a meeting starts, and turning it on disables several cloud conveniences—so the vast majority of Zoom calls run decrypted through Zoom's cloud routers.

In Wonek, MLS (RFC 9420) end-to-end encryption is always on across every voice call, HD video call, screen share, message, file transfer, and CRDT document.

#### Direct Peer-to-Peer Latency Advantage
Routing two people in the same city through a regional cloud data center adds avoidable delay. Wonek's proprietary port-prediction NAT traversal establishes direct QUIC peer-to-peer paths at a high success rate—even on cellular CGNAT—falling back to latency-measured encrypted relays only when strict firewalls block UDP.

#### Your Conversation Doesn't Evaporate When the Call Ends
Instead of losing in-call links when the host clicks 'End Meeting for All,' Wonek anchors calls inside persistent Personal or Work threads alongside CRDT docs, chunk-resumable P2P files, and your 5-view shared calendar.

#### Frequently Asked Questions
- **Are Zoom calls end-to-end encrypted by default?** No. Standard Zoom meetings use transport encryption terminated at Zoom's servers unless the host specifically configures End-to-End Encrypted meetings. Wonek encrypts all calls and screen shares end-to-end by default.
- **Can I share my iPhone or iPad screen in Wonek?** Yes. Wonek supports native E2EE screen sharing across iPhone, iPad, and Mac.
- **Does Wonek also make AI video creation software?** Yes—Arte Soft EOOD publishes Wonek Video Studio for macOS separately at https://studio.wonek.com/, while https://wonek.com is the home of the Wonek E2EE P2P communication app.

### Wonek vs Google Meet: Direct P2P E2EE Audio/Video & Persistent Workspace vs Cloud Tabs
URL: https://wonek.com/compare/wonek-vs-google-meet/

Google Meet is convenient inside Chrome for Google Workspace users, yet every standard call flows through Google's cloud media servers without default client-side E2EE, and closing the browser tab ends the context. Wonek brings native Apple speed, direct P2P QUIC media, and mandatory MLS E2EE to calls, chat, files, and docs.

**Direct Answer / Verdict:** Use Google Meet for zero-install browser calls with external guests across ChromeOS, Windows, and Android. Request early access to Wonek when you want native iPhone, iPad, Mac, and Apple Watch performance with default client-side MLS E2EE, high-success direct P2P calls over QUIC, persistent rich messaging, chunk-resumable P2P file transfers, CRDT docs, and a private 5-view shared calendar.

**Table 1: Core Capability Matrix — Wonek vs Google Meet**

| Capability | Wonek (Pre-Release) | Google Meet |
| --- | --- | --- |
| Client-Side End-to-End Encryption | Default MLS (RFC 9420) for all calls, chats, files & docs | Cloud-decrypted by default (CSE limited to complex enterprise setup) |
| Native macOS Desktop App | Yes — native Mac app (plus iPhone, iPad & Apple Watch) | Browser tab / PWA only on macOS |
| Persistent Messaging & Files | Full E2EE rich chat + direct P2P resumable large files | Ephemeral in-call chat (or separate Google Chat cloud app) |
| Collaborative Docs & Calendar | Built-in E2EE CRDT docs + 5-view Shared Calendar | External Google Docs & Google Calendar (stored in Google cloud) |
| Push-to-Talk (PTT) | 1:1 & group E2EE PTT on iPhone, Mac & Watch | None |
| Personal & Work Separation | Built-in Personal and Work profiles in one app | Requires switching Google browser profiles/accounts |

**Table 2: Network & Privacy Architecture**

| Technical Dimension | Wonek | Google Meet |
| --- | --- | --- |
| Media Routing | Direct device-to-device P2P primary + encrypted relay fallback | Routed via Google cloud media servers |
| Transport Protocol | QUIC / WebTransport with mandatory TLS 1.3 | WebRTC over UDP/TCP to Google infrastructure |
| Mobile CGNAT Optimization | Proprietary port-prediction NAT traversal for direct P2P | Cloud SFU / TURN relay |
| Data & Metadata Ecosystem | Independent Arte Soft EOOD; zero ad-ecosystem linkage | Integrated with Google account & Workspace cloud ecosystem |
| Offline Resilience | Offline CRDT doc edits + ciphertext message queue | Requires active browser connection |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended Tool | Why |
| --- | --- | --- |
| Quick external sales call via a Chrome calendar link | Google Meet | Runs in any desktop web browser with zero download |
| Private team or family hub outside Google's cloud | Wonek | Zero plaintext exposure on cloud servers across chat, calls, docs & calendar |
| Native Mac & iPad screen sharing without browser fan spin | Wonek | Compiled native Apple app with hardware media efficiency |
| Sending multi-GB deliverables during a call without Google Drive | Wonek | Direct P2P file streaming with chunk-level resumption |
| Seamless Wi-Fi-to-5G mobile calls & Apple Watch audio | Wonek | QUIC connection resilience + native watchOS integration |

#### True Native macOS & Apple Watch Integration vs Browser Tabs
Hunting through 40 open Safari or Chrome tabs just to unmute your microphone—while browser WebRTC spins up CPU usage—gets old quickly. Wonek runs as a dedicated native application across Mac, iPad, iPhone, and Apple Watch with system-level Picture-in-Picture and screen sharing.

#### Replacing Cloud Docs + Cloud Calendar + Cloud Meet with One E2EE Suite
Google Workspace is convenient precisely because Meet, Docs, Drive, and Calendar talk to each other—at the cost of storing your entire personal or company life in Google's cloud. Wonek delivers that integrated workflow (calls, chat, P2P files, Yjs/Yrs CRDT docs, and a 5-view shared calendar) inside client-side MLS end-to-end encryption.

#### Direct QUIC P2P Media Paths
Whenever network conditions allow—including across difficult mobile CGNAT—Wonek connects peers directly over QUIC TLS 1.3 for crisp Opus audio and low-latency video.

#### Frequently Asked Questions
- **Does Google Meet use end-to-end encryption by default?** No. Standard Google Meet calls are encrypted in transit to Google's servers, which process the media streams. Wonek applies client-side MLS (RFC 9420) end-to-end encryption by default to every call, screen share, message, and document.
- **Does Wonek have a native Mac app instead of a web wrapper?** Yes. Wonek is built natively for macOS, iOS, iPadOS, and watchOS.
- **How can I request early access to Wonek?** Email support@wonek.com to request pre-release early access updates from Arte Soft EOOD.

### Wonek vs Element (Matrix): QUIC/MLS Native Speed vs Federated Homeserver Sync
URL: https://wonek.com/compare/wonek-vs-element-matrix/

Matrix and Element pioneered federated open-source rooms, yet everyday users frequently wrestle with slow initial syncs, 'Unable to decrypt' Megolm key warnings, and heavy homeserver RAM requirements. Wonek delivers crisp native Apple UX over QUIC and IETF MLS (RFC 9420) with zero server administration.

**Direct Answer / Verdict:** Choose Element (Matrix) if you specifically require federated open-source self-hosting bridged across Linux, Android, Windows, and web rooms. Request early access to Wonek (pre-release for iPhone, iPad, Mac, and Apple Watch) when you want instant QUIC responsiveness, native MLS (RFC 9420) multi-device key reliability via Noise QR linking, direct P2P calls across 4G/5G CGNAT, chunk-resumable P2P files, CRDT docs, and a 5-view shared calendar.

**Table 1: User Experience & Workspace Matrix — Wonek vs Element (Matrix)**

| Capability | Wonek (Pre-Release) | Element / Matrix |
| --- | --- | --- |
| Multi-Device Key UX | Simple Noise QR linking + MLS (RFC 9420) tree sync | Cross-signing phrases, recovery keys & occasional Megolm gaps |
| Sync & Startup Speed | Instant QUIC / WebTransport stream multiplexing | Federated DAG sync can lag on large homeservers |
| Voice, Video & Screen Share | Direct CGNAT P2P primary + encrypted relay fallback | Element Call / LiveKit SFU or basic 1:1 WebRTC |
| Large File Transfers | Direct P2P streaming with chunk-level resumption | HTTP media repository uploads capped by homeserver |
| Collaborative Docs & Calendar | Built-in Yjs/Yrs CRDT docs + 5-view Shared Calendar | Requires external widgets/third-party integrations |
| Apple Watch & Push-to-Talk | Native watchOS calling/audio + 1:1 & group E2EE PTT | No first-party Apple Watch calling/PTT workflow |

**Table 2: Cryptographic & Network Architecture**

| Technical Layer | Wonek | Element (Matrix) |
| --- | --- | --- |
| E2EE Protocol | IETF MLS (RFC 9420) in native Rust core | Olm / Megolm (vodozemac); Matrix MLS still experimental |
| Transport Layer | QUIC / WebTransport with mandatory TLS 1.3 | HTTPS JSON REST polling / Sliding Sync |
| 4G/5G Mobile CGNAT Calls | Proprietary port-prediction NAT traversal for direct P2P | Standard WebRTC ICE/TURN or LiveKit SFU |
| Server Administration Required | Zero — ready out of the box | High if self-hosting Synapse/Dendrite + PostgreSQL + TURN |
| Profile Separation | Personal & Work profiles under one account | Spaces or separate homeserver logins |

**Table 3: Best Fit by Use Case**

| Scenario | Recommended Platform | Why |
| --- | --- | --- |
| Public federated Linux/FOSS foundation rooms | Element (Matrix) | Open federation across independent community homeservers |
| Non-technical families & Apple teams wanting E2EE that just works | Wonek | Zero homeserver URLs, zero recovery-passphrase confusion |
| Low-latency mobile calls & multi-GB P2P file transfers | Wonek | Port-predicted QUIC P2P bypasses homeserver upload caps |
| Integrated private docs & 5-view team/family calendar | Wonek | Native offline-capable CRDT documents and shared calendar |
| Wrist calling & Push-to-Talk on Apple Watch | Wonek | Built natively across iOS, iPadOS, macOS & watchOS |

#### MLS From Day One Instead of Retrofitting Legacy Megolm
Matrix's original Megolm session sharing made multi-device verification notoriously tricky for non-engineers. By building directly on IETF MLS (RFC 9420) in a clean Rust cryptographic core with Noise QR enrollment, Wonek keeps multi-device group keys fast and predictable across iPhone, iPad, Mac, and Apple Watch.

#### QUIC Binary Streams vs Chatty JSON Homeserver Sync
Instead of syncing massive JSON state graphs over HTTPS, Wonek multiplexes compact binary frames over QUIC / WebTransport with TLS 1.3—delivering snappy wakeups even on weak cellular reception.

#### Direct P2P Media & Built-In Collaboration
Wonek pairs smart CGNAT P2P calling and chunk-resumable file transfers with native CRDT documents and a 5-view shared calendar—no widget servers or TURN daemons to maintain.

#### Frequently Asked Questions
- **Do I need to host my own server or TURN relay to use Wonek?** No. Wonek handles signaling, ciphertext-only offline queuing, and fallback encrypted relays automatically while prioritizing direct P2P paths.
- **Why does Wonek use MLS (RFC 9420)?** MLS is the modern IETF standard purpose-built for efficient O(log N) group key updates, forward secrecy, and post-compromise security across multiple devices.
- **Is Wonek available for pre-release testing?** Wonek is in pre-release preparation for iPhone, iPad, Mac, and Apple Watch. Contact support@wonek.com for early-access inquiries.

### Wonek vs Threema: QUIC P2P Video, Screen Sharing, PTT & CRDT Docs Compared
URL: https://wonek.com/compare/wonek-vs-threema/

Threema is a respected Swiss paid messenger focused on minimalist 1:1 and small-group privacy, though multi-device desktop/iPad independence, large file transfers, and rich collaboration remain constrained compared to a modern MLS + QUIC workspace.

**Direct Answer / Verdict:** Pick Threema today if you want a mature one-time-purchase anonymous ID messenger across Android and iOS. Request early access to Wonek when you want true independent multi-device Apple sync (iPhone, iPad, Mac, Apple Watch) powered by IETF MLS (RFC 9420), high-success direct QUIC P2P voice/video and screen sharing, Push-to-Talk, chunk-resumable multi-GB file transfers, CRDT docs, and a 5-view shared calendar.

**Table 1: Feature & Multi-Device Matrix — Wonek vs Threema**

| Capability | Wonek (Pre-Release) | Threema |
| --- | --- | --- |
| Independent Multi-Device Sync | Native independent iPhone, iPad, Mac & Watch via MLS | Historically phone-tethered desktop; multi-device still evolving |
| Screen Sharing (iOS, iPadOS, Mac) | Native E2EE screen sharing across iPhone, iPad & Mac | Desktop-focused call features; limited mobile screen share |
| Large File Transfers | Direct P2P streaming with chunk-level resumption | Encrypted server attachment cap (~50 MB per file) |
| Push-to-Talk & Apple Watch | 1:1 & group E2EE PTT + Apple Watch calling/audio | Async voice messages; no standalone Watch calling/PTT |
| Collaborative Docs & Calendar | Built-in Yjs/Yrs CRDT docs + 5-view Shared Calendar | Polls & text messages only |
| Personal & Work Separation | Personal + Work profiles in one app | Separate Threema Work app & license required |

**Table 2: Cryptography & Transport Architecture**

| Technical Layer | Wonek | Threema |
| --- | --- | --- |
| End-to-End Encryption | IETF MLS (RFC 9420) in Rust core + forward secrecy | NaCl / Ibex cryptographic protocol |
| Group Key Efficiency | O(log N) TreeKEM group key updates | Pairwise fan-out encryption to group members |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | Custom TCP socket + WebRTC calls |
| Mobile CGNAT Call Routing | Proprietary port-prediction NAT traversal for direct P2P | Standard WebRTC ICE/STUN with TURN fallback |
| European Engineering | Arte Soft EOOD (Sofia, Bulgaria — EU) | Threema GmbH (Switzerland) |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended App | Why |
| --- | --- | --- |
| Phone-number-free ID texting with Android contacts right now | Threema | Established cross-platform app live on Android & iOS |
| Using Mac, iPad & Watch even when your iPhone battery dies | Wonek | First-class independent MLS leaf nodes per enrolled Apple device |
| Transferring multi-GB video & RAW archives without 50 MB caps | Wonek | Direct P2P QUIC streaming with chunk-level resumption |
| Co-editing private documents & schedules inside the messenger | Wonek | Built-in offline-capable CRDT docs and 5-view calendar |
| Combining Personal & Work contexts without buying two apps | Wonek | Integrated Personal and Work profile switcher |

#### True Multi-Device Independence Across iPhone, iPad, Mac & Watch
Apple users expect their Mac and iPad to stay fully functional even if their iPhone is in another room or out of battery. Because Wonek enrolls each Apple device as an authenticated MLS (RFC 9420) leaf via Noise QR, every device sends and receives independently without phone-tethered browser relays.

#### Breaking Past 50 MB Attachment Caps
Server-relayed messengers cap attachments tightly to protect storage budgets. Wonek streams large files directly device-to-device over QUIC with chunk-level resumption.

#### European Privacy Standards Plus Full Collaboration
Built in the EU by Arte Soft EOOD, Wonek extends strict client-side E2EE beyond text into screen sharing, Push-to-Talk, CRDT docs, and shared calendars.

#### Frequently Asked Questions
- **Does my iPhone need to stay online for Wonek on Mac to work?** No. Once enrolled via authenticated Noise QR linking, your Mac and iPad participate directly in Wonek's MLS cryptographic groups.
- **Does Wonek provide forward secrecy for group chats?** Yes. Wonek uses IETF MLS (RFC 9420), providing both forward secrecy and post-compromise security across 1:1 and group conversations.
- **Do I need a second app for work chats?** No. Wonek includes dedicated Personal and Work profile contexts inside a single app.

### Wonek vs Wire: Direct CGNAT P2P over QUIC, CRDT Docs & Shared Calendar
URL: https://wonek.com/compare/wonek-vs-wire/

Wire was an early enterprise champion of Messaging Layer Security (MLS). Where Wire focuses on enterprise B2B SFU cloud deployments, Wonek pairs MLS (RFC 9420) with native QUIC / WebTransport, high-success direct P2P across mobile CGNAT, chunk-resumable P2P files, CRDT docs, a 5-view calendar, and Apple Watch support.

**Direct Answer / Verdict:** Choose Wire for established cross-platform enterprise B2B contracts spanning Windows, Linux, Android, and on-prem government servers. Request early access to Wonek when you want a fast, native Apple experience (iPhone, iPad, Mac, Apple Watch) uniting MLS (RFC 9420) E2EE with direct QUIC P2P calls, resumable multi-GB file transfers, Push-to-Talk, CRDT collaborative docs, shared calendars, and Personal + Work profiles.

**Table 1: Collaboration & Device Matrix — Wonek vs Wire**

| Capability | Wonek (Pre-Release) | Wire |
| --- | --- | --- |
| IETF MLS (RFC 9420) E2EE | Yes — native Rust cryptographic core | Yes — Proteus + MLS support |
| Call Media Routing | Direct device-to-device P2P primary + encrypted relay fallback | Cloud SFU / TURN media routing |
| Large File Transfers | Direct P2P with chunk-level resumption | Cloud asset upload capped (~25–100 MB tier limits) |
| Collaborative Documents | Built-in offline-capable Yjs/Yrs CRDT docs | Not built in |
| Built-in Shared Calendar | 5-view Calendar (Day, Multi-Day, Month, Year, List) | Not built in |
| Push-to-Talk & Apple Watch | 1:1 & group E2EE PTT + native watchOS calling/audio | No standalone watchOS calling/PTT |

**Table 2: Transport, Desktop Footprint & NAT Specs**

| Technical Dimension | Wonek | Wire |
| --- | --- | --- |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | HTTPS / WebSockets + WebRTC |
| Mobile CGNAT Optimization | Proprietary port-prediction NAT traversal for direct P2P | Standard WebRTC ICE/TURN + SFU |
| macOS App Architecture | Native Apple UI + compiled Rust core | Electron wrapper on desktop |
| Multi-Device Enrollment | Authenticated Noise-protocol QR linking | Account login + key verification |
| Audience Fit | Personal + Work/Team profiles in one intuitive app | Primarily B2B / public-sector enterprise sales |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended Platform | Why |
| --- | --- | --- |
| Self-hosted Linux/Windows/Android ministry deployment today | Wire | Mature enterprise on-prem and cross-OS B2B governance |
| Native Mac, iPad, iPhone & Watch speed without Electron lag | Wonek | Purpose-built native Apple client with Rust crypto core |
| Low-latency direct P2P calls & screen shares across 5G | Wonek | Port-predicted QUIC P2P avoids mandatory SFU cloud hops |
| Sending multi-gigabyte files without 25–100 MB attachment limits | Wonek | Direct P2P streaming with chunk-level resumption |
| Co-editing encrypted docs & team calendars without extra SaaS | Wonek | Native Yjs/Yrs CRDT docs and 5-view shared calendar |

#### Shared Belief in MLS—Different Transport & Media Philosophy
Both Wonek and Wire recognize IETF MLS (RFC 9420) as the gold standard for modern multi-device and group end-to-end encryption. Wonek goes a step further underneath MLS by replacing TCP WebSockets and Electron desktop shells with native QUIC / WebTransport and native Apple UI.

#### Direct P2P Calls & Multi-GB Files Instead of Small Cloud Caps
Enterprise cloud messengers restrict file sizes tightly because every attachment lands in S3 buckets. Wonek's direct P2P QUIC engine moves large videos and archives straight between peers with chunk-level resumption.

#### Built for Both Everyday Personal Life and Deep Team Work
With Personal and Work profiles, Apple Watch PTT, CRDT docs, and a 5-view shared calendar, Wonek feels just as natural for families as for engineering teams.

#### Frequently Asked Questions
- **Do both Wonek and Wire support RFC 9420 MLS?** Yes. Both embrace IETF Messaging Layer Security (RFC 9420); Wonek pairs its Rust MLS core with QUIC/WebTransport and direct CGNAT P2P routing.
- **Does Wonek use Electron on macOS?** No. Wonek is built natively for Mac, iPhone, iPad, and Apple Watch.
- **Can I edit collaborative documents offline in Wonek?** Yes. Wonek's Yjs/Yrs CRDT documents allow offline edits that merge cleanly upon reconnection.

### Wonek vs Session: Low-Latency QUIC P2P Voice/Video & Large Files vs Onion Routing
URL: https://wonek.com/compare/wonek-vs-session/

Session routes messages through a multi-hop decentralized onion network without phone numbers—great for pseudonymous text, but multi-hop onion latency limits HD video, screen sharing, and large file transfers. Wonek optimizes for crisp real-time encrypted communication and collaboration.

**Direct Answer / Verdict:** Choose Session if strict phone-numberless onion-routed anonymity across Android/desktop outweighs call quality and file size. Request early access to Wonek when you want crisp HD E2EE voice and video calls, native screen sharing, Push-to-Talk, Apple Watch support, chunk-resumable multi-GB P2P file transfers, CRDT collaborative docs, and shared calendars over low-latency QUIC.

**Table 1: Real-Time Media & Workspace Matrix — Wonek vs Session**

| Capability | Wonek (Pre-Release) | Session |
| --- | --- | --- |
| 1:1 & Group HD Voice/Video Calls | Full MLS E2EE 1:1 & group calls with Opus AEC & PiP | Experimental 1:1 calls; onion latency makes group HD calls hard |
| Native Screen Sharing | Yes — iPhone, iPad, and Mac E2EE screen sharing | Limited / not designed for crisp multi-platform screen review |
| Large File Transfers | Direct P2P over QUIC with chunk-level resumption | Strict small swarm file-size cap (~10 MB) |
| Push-to-Talk & Apple Watch | 1:1 & group E2EE PTT + Apple Watch calling/audio | Async voice clips only; no Apple Watch calling |
| Collaborative Docs & Calendar | Built-in Yjs/Yrs CRDT docs + 5-view Shared Calendar | None |
| Account Identity Model | Phone-verified account with Personal & Work profiles | Random anonymous Session ID (no phone number) |

**Table 2: Routing Latency, Encryption & Transport**

| Technical Dimension | Wonek | Session |
| --- | --- | --- |
| Network Routing Design | Direct P2P over QUIC primary + low-latency encrypted relay | 3-hop Oxen/Session onion routing nodes |
| Typical Media Latency | Ultra-low single-hop P2P latency across Wi-Fi & 5G CGNAT | High multi-hop onion delay |
| End-to-End Encryption | IETF MLS (RFC 9420) in native Rust core | Session Protocol encryption |
| Multi-Device Enrollment | Authenticated Noise-protocol QR linking | Recovery seed phrase sync across swarms |
| Transport Protocol | QUIC / WebTransport (TLS 1.3) | Onion-routed HTTPS/QUIC swarm requests |

**Table 3: Best Fit by Threat Model & Workflow**

| Priority | Recommended App | Why |
| --- | --- | --- |
| Pseudonymous whistleblowing text with zero phone number | Session | No phone verification + multi-hop IP hiding |
| Daily HD video calls, screen sharing & crisp Opus voice | Wonek | Single-hop direct QUIC P2P eliminates multi-hop audio lag |
| Sending gigabytes of video or photo albums privately | Wonek | Resumable direct P2P beats Session's ~10 MB swarm cap |
| Team & family collaboration (docs, calendar, Watch PTT) | Wonek | Complete encrypted workspace across Apple devices |
| Reliable mobile wakeup & battery life on iOS/watchOS | Wonek | Engineered natively for Apple device power management |

#### Why Onion Routing and Real-Time HD Video Pull in Opposite Directions
Bouncing every packet through three volunteer nodes around the globe hides IP metadata at a steep physical cost: hundreds of milliseconds of added round-trip delay and strict 10 MB attachment ceilings.

For trusted contacts, families, and teams who want uncompromising content encryption (MLS RFC 9420 + QUIC TLS 1.3) WITH natural real-time conversation, Wonek establishes direct peer-to-peer links across mobile CGNAT—or uses latency-measured encrypted relays when firewalls require it.

#### Gigabyte-Scale P2P Transfers vs 10 MB Swarm Limits
Because Wonek streams encrypted chunks directly peer-to-peer with automatic resumption, sharing a full photo shoot or build archive never hits a 10 MB wall.

#### Complete Apple Ecosystem Integration
From Apple Watch Push-to-Talk to Mac screen sharing, CRDT collaborative docs, and a 5-view shared calendar, Wonek turns encrypted communication into a daily productivity hub.

#### Frequently Asked Questions
- **Why does Wonek use phone verification instead of anonymous IDs?** Phone verification prevents spam bots and lets real-world contacts and teams connect reliably, while Personal and Work profiles keep your contexts separated and MLS E2EE keeps all content strictly private.
- **Can Wonek fallback relays read my calls?** No. Even when strict firewalls trigger an encrypted relay fallback, MLS (RFC 9420) end-to-end encryption keeps all audio, video, and data unreadable to the relay.
- **Does Wonek limit file transfers to 10 MB?** No. Wonek uses direct P2P file streaming over QUIC with chunk-level resumption for large files and photo albums.

### Wonek vs SimpleX Chat: Direct QUIC P2P Video, Apple Watch & Collaborative Docs
URL: https://wonek.com/compare/wonek-vs-simplex-chat/

SimpleX Chat innovated unidirectional message queues with zero user IDs for high-anonymity text, whereas Wonek focuses on seamless Apple-native real-time voice/video, screen sharing, resumable multi-GB P2P files, Apple Watch PTT, CRDT docs, and shared calendars.

**Direct Answer / Verdict:** Choose SimpleX Chat when identifier-free unidirectional queue anonymity across Android/Linux is your primary goal. Request early access to Wonek when you want effortless multi-device Apple sync (iPhone, iPad, Mac, Apple Watch), direct QUIC P2P group HD calls and screen shares across 4G/5G CGNAT, Push-to-Talk, chunk-resumable large file transfers, CRDT docs, and a 5-view shared calendar.

**Table 1: Real-Time Calling & Workspace Matrix — Wonek vs SimpleX Chat**

| Capability | Wonek (Pre-Release) | SimpleX Chat |
| --- | --- | --- |
| 1:1 & Group HD Video + Screen Share | Native E2EE group calls, PiP & iOS/iPadOS/Mac screen share | Basic 1:1 WebRTC calls; limited group video & screen share |
| Multi-Device Apple Sync | First-class independent iPhone, iPad, Mac & Watch via MLS | Primarily single-profile mobile or linked desktop bridge |
| Large File Transfers | Direct P2P over QUIC with chunk-level resumption | SMP relay chunked files with relay limits |
| Push-to-Talk & Apple Watch | 1:1 & group E2EE PTT + native Apple Watch support | No standalone watchOS app or live PTT rooms |
| Collaborative Docs & Calendar | Offline-capable Yjs/Yrs CRDT docs + 5-view Calendar | Not included |
| Onboarding Simplicity | Familiar phone-verified account + Personal/Work profiles | One-time invitation links / QR per contact |

**Table 2: Cryptographic & Transport Architecture**

| Technical Dimension | Wonek | SimpleX Chat |
| --- | --- | --- |
| Group Encryption Scaling | O(log N) IETF MLS (RFC 9420) in native Rust core | Pairwise Double Ratchet fan-out across SMP queues |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | SMP over TLS / Tor optional |
| Mobile CGNAT Call Traversal | Proprietary port-prediction NAT traversal for direct P2P | Standard WebRTC ICE/TURN |
| iOS Background Battery Impact | Lean native push + ciphertext offline queue | Maintaining multiple queue sockets can increase battery use |
| Device Linking | Authenticated Noise-protocol QR handshake | Local network / export-import |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended App | Why |
| --- | --- | --- |
| Zero-identifier anonymous queues over Tor on Android | SimpleX Chat | Unidirectional SMP queues with no global user identifiers |
| Seamless sync across iPhone, iPad, Mac & Apple Watch | Wonek | Native MLS multi-device tree keeps all Apple devices in lockstep |
| Group HD video calls & code/design screen sharing | Wonek | Direct QUIC P2P media with Opus AEC and native screen share |
| Team & family planning with shared calendars & live docs | Wonek | Built-in CRDT collaborative docs and 5-view shared calendar |
| Sending multi-gigabyte archives without relay caps | Wonek | Direct P2P file transfer with chunk-level resumption |

#### Logarithmic MLS Group Scaling vs Pairwise Queue Fan-Out
In SimpleX, groups operate via pairwise fan-out across individual queues—which works for small text rooms but multiplies bandwidth as members and devices grow. Wonek uses IETF MLS (RFC 9420) so multi-device groups scale cleanly in O(log N) operations.

#### First-Class Voice, Video, Screen Share & Watch PTT
Real-time media is a core pillar in Wonek, combining Opus audio processing, Picture-in-Picture HD video, native screen sharing across iPhone/iPad/Mac, and wrist Push-to-Talk over QUIC.

#### Everyday Usability Without Sacrificing Client-Side E2EE
With Personal and Work profiles, CRDT docs, and a 5-view shared calendar, Wonek makes strong client-side E2EE approachable for whole teams and families.

#### Frequently Asked Questions
- **Does Wonek keep my iPad and Mac synced automatically?** Yes. Once linked via Noise QR enrollment, all your authorized Apple devices participate natively in MLS-encrypted conversations.
- **How does Wonek handle calls across 4G/5G mobile networks?** Wonek uses proprietary port-prediction NAT traversal over QUIC to establish direct peer-to-peer calls at a high rate across mobile CGNAT, with encrypted relay fallback when UDP is blocked.
- **Can I use Wonek offline to draft shared notes?** Yes. Collaborative CRDT documents support offline editing and merge automatically without conflicts once reconnected.

### Wonek vs Briar: Native iPhone/Mac/Watch Support, HD Video & Offline Queue
URL: https://wonek.com/compare/wonek-vs-briar/

Briar is a specialized offline/Tor mesh text messenger built for Android—meaning it does not exist on iPhone, iPad, or Apple Watch, and has no real-time voice or video calls. Wonek delivers native E2EE peer-to-peer communication specifically across the Apple ecosystem.

**Direct Answer / Verdict:** Use Briar on Android during internet blackouts where local Bluetooth/Wi-Fi Tor text syncing is vital. Request early access to Wonek for iPhone, iPad, Mac, and Apple Watch—bringing high-success direct QUIC P2P HD voice/video calls, screen sharing, Push-to-Talk, chunk-resumable large file transfers, ciphertext offline message queuing, CRDT docs, and shared calendars.

**Table 1: Platform & Capability Matrix — Wonek vs Briar**

| Capability | Wonek (Pre-Release) | Briar |
| --- | --- | --- |
| iPhone, iPad & Apple Watch Apps | Yes — native iOS, iPadOS, macOS & watchOS | No iOS, iPadOS, or watchOS app (Android + desktop beta only) |
| Voice, Video & Screen Share | 1:1 & group E2EE HD calls, PiP & native screen share | None — text/forum/blog sync only |
| Push-to-Talk (PTT) | 1:1 & group E2EE PTT on iPhone, Mac & Watch | None |
| Async Delivery When Peer Is Offline | Instant delivery on wake via ciphertext-only queue | Requires both peers online simultaneously (unless Briareus mailbox setup) |
| Large File Transfers | Direct QUIC P2P with chunk-level resumption | Small images only over Tor |
| Collaborative Docs & Calendar | Yjs/Yrs CRDT docs + 5-view Shared Calendar | Basic forums/blogs; no calendar or live CRDT docs |

**Table 2: Network, Battery & Cryptographic Specs**

| Technical Dimension | Wonek | Briar |
| --- | --- | --- |
| Transport Layer | QUIC / WebTransport (TLS 1.3) + port-predicted CGNAT P2P | Tor hidden services / local Bluetooth & Wi-Fi |
| Encryption Standard | IETF MLS (RFC 9420) in native Rust core | Bramble cryptographic protocol |
| Mobile Battery Consumption | Optimized for iOS/watchOS power efficiency | Continuous background Tor daemon drains mobile battery |
| Multi-Device Support | Seamless sync across iPhone, iPad, Mac & Watch | Single-device bound identity |
| Strict Firewall Fallback | Automatic latency-measured encrypted relay | Tor bridges |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended App | Why |
| --- | --- | --- |
| Bluetooth mesh texting on Android with zero internet | Briar | Built specifically for local mesh & Tor hidden services on Android |
| Any iPhone, iPad, Mac, or Apple Watch user | Wonek | Briar has no iOS/watchOS support; Wonek is built natively for Apple |
| Real-time E2EE voice, HD video, PTT & screen sharing | Wonek | Low-latency QUIC P2P media pipeline |
| Messaging friends across time zones without waiting both online | Wonek | Ciphertext-only offline queue delivers even if sender boards a flight |
| Sharing large videos, CRDT docs & team/family calendars | Wonek | Full communication & productivity suite |

#### Why iOS Requires Smarter Architecture Than Background Tor Daemons
Briar has never shipped on iPhone largely because iOS suspends persistent background Tor hidden-service daemons to preserve battery life. Wonek works with Apple's architecture instead of fighting it: combining battery-clean wakeups and an opaque ciphertext offline queue with direct QUIC P2P connections the instant a call or transfer begins.

#### Beyond Text: HD Video, Screen Share, PTT & Multi-GB Files
Where Briar is restricted to text and small images, Wonek supports full 1:1 and group HD video, Opus voice, screen sharing, Push-to-Talk, and chunk-resumable P2P file transfers.

#### Multi-Device Freedom Across Your Entire Apple Setup
Link your iPhone, iPad, Mac, and Apple Watch via Noise QR enrollment and keep CRDT documents and shared calendars synced everywhere.

#### Frequently Asked Questions
- **Does Briar work on iPhone?** No—Briar is built for Android (with desktop Linux/Windows/macOS builds) and does not offer an iPhone, iPad, or Apple Watch app. Wonek is designed natively for iPhone, iPad, Mac, and Apple Watch.
- **Do both people have to be online at the same moment to send a text in Wonek?** No. Wonek queues end-to-end encrypted MLS ciphertext when a recipient is offline and delivers it automatically when their device wakes.
- **Does Wonek drain battery in the background like mesh/Tor apps?** No. Wonek avoids continuous background DHT/Tor polling while still establishing direct QUIC P2P connections for live calls and file transfers.

### Wonek vs Jami: Mobile CGNAT Port-Predicted QUIC P2P & Offline Queue vs OpenDHT
URL: https://wonek.com/compare/wonek-vs-jami/

Jami (formerly Ring) is a GNU peer-to-peer communicator built on OpenDHT and SIP/ICE. On mobile networks, however, pure DHT discovery and standard ICE struggle with iOS background suspension, missed offline messages, and symmetric 4G/5G CGNAT. Wonek solves those exact mobile P2P pain points.

**Direct Answer / Verdict:** Choose Jami if you want a GPL serverless OpenDHT desktop softphone on Linux/Windows/Android. Request early access to Wonek (for iPhone, iPad, Mac, and Apple Watch) when you want P2P calling and file transfers that actually thrive on mobile 4G/5G CGNAT via proprietary port prediction over QUIC—backed by reliable offline ciphertext queuing, MLS (RFC 9420) groups, Apple Watch PTT, CRDT docs, and shared calendars.

**Table 1: Reliability & Feature Matrix — Wonek vs Jami**

| Capability | Wonek (Pre-Release) | Jami |
| --- | --- | --- |
| Offline Message Reliability on iPhone | Guaranteed via ciphertext-only offline server queue | Often delayed if sender & receiver aren't awake simultaneously on DHT |
| Mobile 4G/5G CGNAT Call Success | High-rate direct P2P via proprietary port prediction + QUIC | Standard SIP/ICE frequently falls back to TURN relays |
| Group Chat & Key Sync | IETF MLS (RFC 9420) O(log N) multi-device sync | Git-based swarm sync over DHT (can lag across sleeping phones) |
| Large File Transfers | Direct QUIC P2P with chunk-level resumption | P2P file transfer (requires simultaneous online state) |
| Push-to-Talk & Apple Watch | 1:1 & group E2EE PTT + native Apple Watch app | No Apple Watch calling/PTT app |
| Collaborative Docs & Calendar | Built-in Yjs/Yrs CRDT docs + 5-view Shared Calendar | Not included |

**Table 2: Transport, Discovery & Cryptographic Specs**

| Technical Layer | Wonek | Jami |
| --- | --- | --- |
| Wire & Media Transport | Unified QUIC / WebTransport with mandatory TLS 1.3 | OpenDHT + SIP + pjproject ICE / DTLS-SRTP |
| End-to-End Encryption | MLS (RFC 9420) in native Rust core + Noise QR | TLS/DTLS X.509 device certificates + swarm encryption |
| Connection Setup Speed | Fast QUIC 1-RTT setup without 10-second DHT lookups | OpenDHT peer lookup can add noticeable call ring delay |
| Strict Firewall Fallback | Automatic latency-measured encrypted relay | Community or self-hosted TURN server |
| Profile Contexts | Personal & Work profiles under one account | Multiple local SIP/Jami accounts |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended App | Why |
| --- | --- | --- |
| Linux desktop LAN/SIP peer calling without any central server | Jami | Pure GNU OpenDHT architecture with SIP support on Linux |
| Fast call ring times & direct P2P across 4G/5G CGNAT on iPhone | Wonek | Skips slow DHT bootstrap and traverses mobile CGNAT over QUIC |
| Texting someone whose iPhone is currently in Airplane Mode | Wonek | Ciphertext-only offline queue delivers even after you go offline |
| Resuming a 4 GB file transfer interrupted by a subway tunnel | Wonek | Automatic chunk-level resumption over QUIC |
| Team & family planning on Mac, iPad, iPhone & Watch | Wonek | Includes CRDT docs, 5-view calendar, PTT, and Personal/Work profiles |

#### Fixing the Two Biggest Headaches of Mobile P2P Apps
Anyone who has tested pure DHT communicators on iPhones recognizes two frustrations: calls take 8–15 seconds just to locate a peer on the distributed hash table, and messages sent while a friend's phone is asleep sit stuck until both phones happen to open at once.

Wonek uses ultra-fast signaling and a ciphertext-only offline queue for instant wakeups—then establishes direct device-to-device QUIC connections across mobile CGNAT using proprietary port prediction so media flows straight between peers.

#### Modern QUIC + MLS vs Legacy SIP + X.509 Chains
Replacing legacy SIP/ICE/DTLS stacks with unified QUIC / WebTransport (TLS 1.3) and Rust MLS (RFC 9420) eliminates head-of-line blocking and streamlines multi-device sync across iPhone, iPad, Mac, and Apple Watch.

#### Chunk-Resumable Transfers & Built-In Collaboration
Interrupted large file transfers pick up from the exact last verified chunk, while CRDT documents and a 5-view shared calendar turn Wonek into a complete daily driver.

#### Frequently Asked Questions
- **Why do calls ring faster in Wonek than in DHT-based P2P apps?** Wonek avoids slow distributed-hash-table lookups on mobile wake, negotiating direct QUIC P2P paths rapidly with automatic encrypted relay fallback if UDP is blocked.
- **What happens if I send a message in Wonek and then turn off my own phone?** Because Wonek stores opaque MLS-encrypted ciphertext in an offline delivery queue until the recipient wakes, your message still arrives even if your own phone goes offline.
- **Are Wonek's file transfers peer-to-peer like Jami's?** Yes—with the added advantage of chunk-level resumption over QUIC so temporary network drops never restart large transfers at 0%.

### Wonek vs Viber: Clean Ad-Free E2EE Communication & Workspace vs Ad-Heavy Feeds
URL: https://wonek.com/compare/wonek-vs-viber/

Viber is widely used across Central and Eastern Europe, yet its interface has grown crowded with banner ads, sponsored sticker promos, and commercial chatbots—while file uploads cap at 200 MB. Wonek (built in Sofia, Bulgaria by Arte Soft EOOD) offers a calm, ad-free E2EE P2P platform.

**Direct Answer / Verdict:** Keep Viber installed when reaching local businesses, couriers, or Android contacts who rely on it daily. Request early access to Wonek (pre-release for iPhone, iPad, Mac, and Apple Watch) for a 100% ad-free, zero-tracker communication experience featuring direct QUIC P2P calls across 4G/5G CGNAT, MLS (RFC 9420) encryption, chunk-resumable multi-GB file transfers, Apple Watch PTT, CRDT docs, and Personal/Work profiles.

**Table 1: Experience & Feature Matrix — Wonek vs Viber**

| Capability | Wonek (Pre-Release) | Rakuten Viber |
| --- | --- | --- |
| Ads, Promos & Commercial Clutter | Zero ads, zero trackers, calm native UI | In-list banner ads, promo bots & commercial tabs (unless Viber Plus) |
| End-to-End Encryption | IETF MLS (RFC 9420) in native Rust core | Viber pairwise/group E2EE (channels/bots not E2EE) |
| Large File Sharing | Direct P2P over QUIC with chunk-level resumption | 200 MB file-size limit via cloud upload |
| Screen Sharing (iPhone, iPad, Mac) | Native E2EE screen sharing across all three | Desktop-centric screen share |
| Push-to-Talk & Apple Watch | 1:1 & group E2EE PTT + Apple Watch calling/audio | Quick voice/video notes; limited Watch replies |
| Docs, Calendar & Work Profiles | CRDT docs + 5-view Calendar + Personal/Work profiles | My Notes list only; mixes courier spam with work & family |

**Table 2: Network & Cryptographic Architecture**

| Technical Layer | Wonek | Viber |
| --- | --- | --- |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | Legacy TCP/UDP custom transport |
| 4G/5G Mobile CGNAT Calls | Proprietary port-prediction NAT traversal for direct P2P | Standard STUN/ICE with frequent server relay |
| Multi-Device Enrollment | Authenticated Noise-protocol QR handshake | QR desktop activation |
| Rich Technical Formatting | Markdown, inline code, LaTeX math, edits & pins | Basic bold/italic/monospace |
| Advertising SDKs | None | Ad measurement & commercial monetization stack |

**Table 3: Best Fit by Everyday Scenario**

| Scenario | Recommended App | Why |
| --- | --- | --- |
| Receiving utility bills or parcel delivery alerts on iOS/Android | Viber | Existing commercial business-messaging integrations |
| Distraction-free, zero-ad family & team communication | Wonek | Clean native Apple interface with zero ad banners or tracking |
| Separating serious Work projects from Personal chats | Wonek | Dedicated Personal and Work contexts under one account |
| Sending original-quality photo albums & multi-GB videos | Wonek | Direct P2P chunk-resumable transfers bypass Viber's 200 MB cap |
| Crisp mobile-to-mobile calls when switching Wi-Fi to 5G | Wonek | QUIC connection resilience + Opus AEC audio |

#### A Calm Messenger Without Banner Ads Between Your Conversations
Private conversations should not sit next to programmatic banner ads and promotional chatbots. Wonek is engineered by Arte Soft EOOD with zero advertising SDKs and zero commercial feed clutter.

#### Next-Generation QUIC P2P & Multi-Gigabyte Transfers
Instead of hitting a 200 MB error when sending vacation videos or project files, Wonek streams files directly peer-to-peer over QUIC with chunk-level resumption—and establishes low-latency direct P2P calls across mobile CGNAT.

#### Separate Work From Family—Plus Built-In Docs & Calendar
Switch cleanly between Personal and Work profiles, co-edit offline-capable CRDT documents, and plan events across five shared calendar views.

#### Frequently Asked Questions
- **Does Wonek show ads or require a 'Plus' upgrade just to hide banners?** No. Wonek contains zero advertisements and zero ad-tracking SDKs.
- **Who develops Wonek?** Wonek is developed by Arte Soft EOOD (UIC 202787570), an independent software company based in Sofia, Bulgaria.
- **Can I send files larger than 200 MB in Wonek?** Yes. Wonek transfers large files and photo albums directly peer-to-peer with chunk-level resumption.

### Wonek vs Facebook Messenger: Zero Social-Graph Profiling, MLS E2EE & Direct P2P
URL: https://wonek.com/compare/wonek-vs-facebook-messenger/

Facebook Messenger recently rolled out default E2EE for personal 1:1 chats, yet remains deeply tied to Meta's social graph, dropped its standalone Apple Watch app, deprecated native desktop architectures in favor of web wrappers, and caps attachments tightly.

**Direct Answer / Verdict:** Use Facebook Messenger to message Marketplace sellers or old social-network acquaintances. Request early access to Wonek when you want communication completely decoupled from social-media profiling—with native iPhone, iPad, Mac, and Apple Watch apps, MLS (RFC 9420) E2EE for all 1:1 and group rooms, direct QUIC P2P calls, resumable multi-GB file transfers, CRDT docs, and shared calendars.

**Table 1: Privacy & Apple Native Matrix — Wonek vs Facebook Messenger**

| Capability | Wonek (Pre-Release) | Facebook Messenger |
| --- | --- | --- |
| Social Graph & Ad Profiling | Zero social network, zero ad trackers | Tied to Meta Accounts Center & social graph metadata |
| Apple Watch App | Native watchOS calling, audio & Push-to-Talk | Standalone Apple Watch app discontinued by Meta |
| macOS Desktop App | Native macOS app with compiled Rust core | Shifted away from native macOS toward web wrapper |
| Large File Sharing | Direct P2P over QUIC with chunk-level resumption | Small attachment limit (~25–100 MB) |
| Rich Code, Math & CRDT Docs | Inline code, LaTeX math & live Yjs/Yrs CRDT docs | Stickers/GIFs; no technical formatting or collaborative docs |
| Personal & Work Separation | Dedicated Personal + Work profiles in one account | Tied to personal Facebook profile |

**Table 2: Encryption & Network Specs**

| Technical Dimension | Wonek | Facebook Messenger |
| --- | --- | --- |
| E2EE Standard | IETF MLS (RFC 9420) across all 1:1 & group chats/calls | Labyrinth / Signal-based E2EE (community/business threads vary) |
| Key Backup Model | Noise QR device-to-device enrollment (no cloud PIN escrow) | Encourages PIN/cloud-backed Labyrinth key storage |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | MQTT / HTTPS + Meta media relays |
| Mobile CGNAT Call Routing | Proprietary port-prediction NAT traversal for direct P2P | Primarily routed via Meta edge/TURN relays |
| Shared Calendar | Built-in 5-view Calendar (Day, Multi-Day, Month, Year, List) | None |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended App | Why |
| --- | --- | --- |
| Replying to a Facebook Marketplace listing | Facebook Messenger | Directly connected to Facebook listings |
| People who deleted Facebook but want rich family/friend video & chat | Wonek | Zero Facebook account required; zero social-media surveillance |
| Apple Watch voice & Push-to-Talk users | Wonek | Restores true wrist communication that Messenger removed |
| Native Mac screen sharing & multi-gigabyte file transfers | Wonek | Fast native macOS app + chunk-resumable direct P2P |
| Planning family events & work projects in separate profiles | Wonek | Includes 5-view calendar, CRDT docs, and Personal/Work split |

#### Leaving Social Media Without Losing Family & Group Calls
Millions of people keep a dormant Facebook account solely because Messenger holds a family group thread. Wonek provides rich HD group calls, photo album transfers, and a shared family calendar with zero social-network baggage.

#### True Native Mac & Apple Watch Citizens
While Meta retired its Apple Watch app and simplified desktop Messenger into web wrappers, Wonek invests in native macOS, iOS, iPadOS, and watchOS craftsmanship.

#### Direct QUIC P2P Speed & MLS Cryptography
Every chat, group call, screen share, and file transfer in Wonek runs under IETF MLS (RFC 9420) over QUIC TLS 1.3.

#### Frequently Asked Questions
- **Does Wonek require any social media account?** No. Wonek is a standalone private communication platform by Arte Soft EOOD with zero social-network feed or ad tracking.
- **Does Wonek work on Apple Watch?** Yes. Wonek is designed with native Apple Watch calling, audio, and Push-to-Talk support alongside iPhone, iPad, and Mac.
- **Are group calls and screen sharing end-to-end encrypted in Wonek?** Yes—100% of 1:1 and group calls, screen shares, messages, and files are end-to-end encrypted.

### Wonek vs Zello: End-to-End Encrypted Push-to-Talk + HD Video, Files & Apple Watch
URL: https://wonek.com/compare/wonek-vs-zello/

Zello is a classic internet walkie-talkie app, yet consumer Zello channels are not end-to-end encrypted, and Zello lacks HD video calls, screen sharing, large file transfers, and collaborative docs. Wonek brings instant 1:1 and group Push-to-Talk into a complete MLS end-to-end encrypted Apple platform.

**Direct Answer / Verdict:** Use Zello for public open-channel radio dispatch across rugged Android handsets and Windows PCs. Request early access to Wonek when your team, event crew, or family on iPhone, iPad, Mac, and Apple Watch wants end-to-end encrypted 1:1 and group Push-to-Talk combined with HD video calls, screen sharing, rich chat, chunk-resumable P2P files, CRDT docs, and shared calendars.

**Table 1: Push-to-Talk & Full Communication Matrix — Wonek vs Zello**

| Capability | Wonek (Pre-Release) | Zello |
| --- | --- | --- |
| 1:1 & Group Push-to-Talk (PTT) | Yes — instant Opus PTT over QUIC | Yes — core walkie-talkie PTT focus |
| End-to-End Encryption on PTT | Mandatory default MLS (RFC 9420) E2EE | Consumer Zello uses server TLS only (no client E2EE on standard channels) |
| Apple Watch Support | Native watchOS PTT, voice calls & audio | Basic mobile companion focus |
| Native macOS App | Yes — native Mac app (PTT + video + screen share + chat) | Legacy Windows PC focus; no full modern native Mac workspace |
| HD Video Calls & Screen Sharing | Yes — 1:1 & group E2EE video + screen share | None (voice/text/photo alerts only) |
| Large Files, Docs & Calendar | Resumable P2P files + CRDT docs + 5-view Calendar | None |

**Table 2: Audio, Encryption & Transport Architecture**

| Technical Layer | Wonek | Zello |
| --- | --- | --- |
| Audio Codec & Processing | Opus with acoustic echo cancellation (AEC) & noise suppression | Low-bitrate Opus/Speex voice streaming |
| Cryptographic Key Custody | Client-side Rust MLS core; servers never hear audio | Server-mediated audio routing on standard consumer rooms |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | Custom UDP/TCP streaming |
| Network Path | Direct P2P primary across CGNAT + encrypted relay fallback | Centralized Zello server relay |
| Profile Separation | Personal + Work profiles in one app | Separate consumer vs paid Zello Work dispatch accounts |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended App | Why |
| --- | --- | --- |
| Public CB-style open radio channels on Android/Windows | Zello | Designed around public browseable channels and rugged Android PTT buttons |
| Private security, executive, event, or family PTT on iPhone & Watch | Wonek | Every PTT voice burst is strictly end-to-end encrypted via MLS |
| Escalating a quick PTT check-in into an HD video or screen share | Wonek | Switch seamlessly from PTT to E2EE video, screen share, or CRDT doc |
| Mac desk coordinator talking to field teammates on Apple Watch | Wonek | Native macOS + iOS + watchOS parity |
| Keeping shift PTT separate from family chats | Wonek | Clean Personal and Work profile switching |

#### True End-to-End Encrypted Walkie-Talkie Audio
Many teams assume walkie-talkie apps encrypt voice end-to-end, only to discover standard servers can process and archive channel audio. In Wonek, every 1:1 and group Push-to-Talk burst is encrypted client-side via MLS (RFC 9420) on top of QUIC TLS 1.3.

#### When Five Seconds of PTT Turns Into a Screen Share
Field and engineering coordination rarely stops at voice bursts: someone needs to show an iPhone camera view, share a Mac terminal window, drop a 1 GB archive, or update a shared schedule. Wonek handles the entire workflow in one app.

#### Apple Watch + Mac + iPhone Harmony
Answer or transmit from your wrist on Apple Watch while moving, then continue smoothly on your Mac or iPad back at your desk.

#### Frequently Asked Questions
- **Are Wonek Push-to-Talk channels end-to-end encrypted?** Yes. Both 1:1 and group Push-to-Talk in Wonek use client-side MLS (RFC 9420) end-to-end encryption.
- **Does Wonek Push-to-Talk work on Mac as well as iPhone and Apple Watch?** Yes. Wonek supports Mac, iPad, iPhone, and Apple Watch so desk and mobile participants stay connected.
- **How does audio stay clear outdoors?** Wonek combines the Opus codec with acoustic echo cancellation (AEC) and real-time noise suppression over low-latency QUIC.

### Wonek vs Mattermost: Built-In Client E2EE & Direct P2P Without DevOps Overhead
URL: https://wonek.com/compare/wonek-vs-mattermost/

Mattermost gives DevOps teams a self-hosted Slack alternative on PostgreSQL, yet messages sit unencrypted in your server database—meaning any compromised VM, backup snapshot, or root admin can read every room. Wonek provides client-side MLS E2EE and direct P2P calling with zero Linux administration.

**Direct Answer / Verdict:** Choose Mattermost when your company wants an on-premises Linux/PostgreSQL chat server integrated with Jira/GitLab webhooks across Windows, Linux, and Android. Request early access to Wonek when your Apple-based engineering or leadership team wants true client-side MLS (RFC 9420) encryption where NO server database holds plaintext—plus direct QUIC P2P calls, screen sharing, chunk-resumable P2P files, CRDT docs, and shared calendars.

**Table 1: Security & Collaboration Matrix — Wonek vs Mattermost**

| Capability | Wonek (Pre-Release) | Mattermost |
| --- | --- | --- |
| Client-Side End-to-End Encryption | Default MLS (RFC 9420) across all chats, calls & docs | No native E2EE — messages stored as plaintext in PostgreSQL |
| DevOps & Patching Burden | Zero — works immediately with zero servers to maintain | Requires Linux VM, PostgreSQL, TLS, S3 & rtcd TURN maintenance |
| Voice, Video & Screen Share | Direct QUIC P2P primary + encrypted relay fallback | Requires deploying rtcd media daemon + TURN server |
| Rich Code & Math Formatting | Rich text, inline code & mathematical formulas | Markdown, code blocks & LaTeX support |
| Collaborative Docs & Calendar | Offline-capable Yjs/Yrs CRDT docs + 5-view Calendar | Playbooks/boards; no built-in offline CRDT doc editor |
| Apple Watch & Push-to-Talk | Native watchOS calling/audio + 1:1 & group PTT | No standalone watchOS calling or PTT |

**Table 2: Cryptographic & Transport Architecture**

| Technical Dimension | Wonek | Mattermost |
| --- | --- | --- |
| Database Breach Blast Radius | Zero plaintext on server — ciphertext-only transient queue | Full historical chat & file exposure if server DB compromised |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | HTTPS / TCP WebSockets + WebRTC |
| macOS Client | Native macOS app + compiled Rust core | Electron desktop wrapper |
| Large File Transfers | Direct P2P streaming with chunk-level resumption | Uploaded to server disk / S3 bucket |
| Mobile Push Privacy | Opaque wakeup; decryption strictly on device | Requires self-hosted push proxy or cleartext/ID push config |

**Table 3: Best Fit by Team**

| Scenario | Recommended Platform | Why |
| --- | --- | --- |
| Air-gapped Linux enterprise datacenter with Windows/Linux desktops | Mattermost | Runs completely inside your own corporate VLAN across all OSes |
| Security & founder teams wanting zero server plaintext without DevOps | Wonek | Client-side MLS E2EE eliminates PostgreSQL plaintext risk with 0 ops |
| Pair-programming screen share & multi-GB build transfers on Mac | Wonek | Direct P2P QUIC media and chunk-resumable file streaming |
| Teams combining Work channels & Personal life on iPhone/Mac | Wonek | Clean Personal and Work profiles under one account |
| Offline spec writing while traveling | Wonek | Yjs/Yrs CRDT documents merge cleanly after flights |

#### Self-Hosted Plaintext vs Client-Side Zero-Knowledge E2EE
Self-hosting moves trust from a SaaS vendor to your own cloud VPS and sysadmins—but if every message sits unencrypted inside PostgreSQL, a single compromised SSH key or S3 backup leaks years of company secrets. Wonek encrypts everything client-side via MLS (RFC 9420) so no database ever holds readable conversations.

#### Zero `rtcd` and `coturn` Maintenance
Getting crisp voice and screen sharing working across mobile CGNAT on self-hosted servers typically means debugging UDP firewall ranges and TURN credentials. Wonek's QUIC + smart port-prediction P2P works automatically out of the box.

#### Native Apple Craftsmanship Instead of Electron
Run fast native apps across Mac, iPad, iPhone, and Apple Watch with built-in CRDT docs and a 5-view shared calendar.

#### Frequently Asked Questions
- **Are Mattermost messages end-to-end encrypted?** No. Standard Mattermost stores messages in plaintext inside your server's database so server search and webhooks can read them. Wonek encrypts all messages, calls, files, and docs end-to-end on client devices.
- **Does Wonek support inline code and math like technical team tools?** Yes. Wonek supports rich formatting, inline code, and mathematical formulas alongside edits, replies, and pinned messages.
- **Do we have to manage TURN servers for Wonek calls?** No. Wonek prioritizes direct P2P over QUIC and provides automatic encrypted relay fallback with zero setup.

### Wonek vs Rocket.Chat: Default MLS E2EE & Native Apple P2P vs Server-Side Suites
URL: https://wonek.com/compare/wonek-vs-rocket-chat/

Rocket.Chat targets omnichannel helpdesks and self-hosted MongoDB deployments, where end-to-end encryption has historically been an opt-in per-room feature with search and call limitations—and calls rely on external Jitsi/Pexip bridges. Wonek unifies mandatory MLS E2EE across chat, direct QUIC P2P calls, files, and docs.

**Direct Answer / Verdict:** Pick Rocket.Chat if you need omnichannel customer live-chat routing and self-hosted MongoDB servers across Linux/Windows/Android. Request early access to Wonek when you want fast, native iPhone, iPad, Mac, and Apple Watch apps where every chat, voice/video call, screen share, file transfer, and CRDT doc is end-to-end encrypted by default—with zero server or Jitsi bridge maintenance.

**Table 1: Core Security & Media Matrix — Wonek vs Rocket.Chat**

| Capability | Wonek (Pre-Release) | Rocket.Chat |
| --- | --- | --- |
| End-to-End Encryption Scope | 100% default MLS (RFC 9420) for chat, calls, files & docs | Opt-in room E2EE; many server features disabled in E2EE rooms |
| Native Voice, Video & Screen Share | Built-in direct QUIC P2P E2EE calls + screen share | Requires external Jitsi, Pexip, or paid VoIP app integrations |
| Large File Transfers | Direct P2P streaming with chunk-level resumption | Uploaded to GridFS / S3 storage |
| Collaborative Docs & Calendar | Built-in Yjs/Yrs CRDT docs + 5-view Shared Calendar | External integrations required |
| Desktop & Watch Apps | Native Mac, iPad, iPhone & Apple Watch (with PTT) | Electron desktop app; no Apple Watch calling/PTT |
| Personal & Work Profiles | Clean Personal + Work switcher in one account | Multi-server workspace URL list |

**Table 2: Architecture & Operations Comparison**

| Technical Dimension | Wonek | Rocket.Chat |
| --- | --- | --- |
| Cryptographic Engine | Native Rust MLS (RFC 9420) + Noise QR device linking | JavaScript/client room key passphrase model |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | Meteor DDP / HTTPS WebSockets |
| Mobile CGNAT Call Traversal | Proprietary port-prediction NAT traversal for direct P2P | Depends on external Jitsi/WebRTC TURN setup |
| Infrastructure Required | Zero DevOps | Node.js + MongoDB replica set + reverse proxy + Jitsi |
| Audio Pipeline | Opus with AEC & noise suppression | External conferencing provider dependent |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended Platform | Why |
| --- | --- | --- |
| Customer-support omnichannel ticketing (WhatsApp/Webchat inbox) | Rocket.Chat | Designed around external customer support queues |
| Internal private team & founder collaboration on Apple devices | Wonek | Default MLS E2EE + built-in P2P calls without Jitsi plugins |
| Sharing multi-gigabyte deliverables directly device-to-device | Wonek | Chunk-resumable direct QUIC P2P avoids server disk bloat |
| Wrist Push-to-Talk & seamless Wi-Fi-to-5G calls | Wonek | Native watchOS & QUIC connection resilience |
| Co-editing private specs & schedules offline or online | Wonek | Built-in Yjs/Yrs CRDT docs and 5-view calendar |

#### Built-In E2EE Calls Instead of Bolted-On Jitsi Bridges
Rocket.Chat delegates video calling to third-party bridges like Jitsi, creating jarring tab switches and separate security models. Wonek builds 1:1 and group E2EE voice, HD video, Picture-in-Picture, Push-to-Talk, and screen sharing natively into the same QUIC + MLS engine.

#### Mandatory Rust MLS vs Fragile Browser Key Passphrases
Opt-in E2EE toggles often get left turned off. In Wonek, every single conversation uses IETF MLS (RFC 9420) with authenticated Noise QR device enrollment.

#### Zero MongoDB Replica Sets to Babysit
Spend your engineering hours shipping your product rather than upgrading MongoDB and TURN servers—while enjoying native Mac, iPad, iPhone, and Apple Watch performance.

#### Frequently Asked Questions
- **Does Wonek need an external plugin like Jitsi for video calls?** No. E2EE voice calls, HD video, Picture-to-Picture, Push-to-Talk, and screen sharing are built directly into Wonek.
- **Is E2EE optional or automatic in Wonek?** Automatic and mandatory across all 1:1 and group chats, calls, screen shares, file transfers, and CRDT documents.
- **How do I request early access for my team?** Email support@wonek.com to join the pre-release list for Mac, iPhone, iPad, and Apple Watch.

### Wonek vs Nextcloud Talk: High-Rate Mobile CGNAT P2P Without Manual TURN/HPB Admin
URL: https://wonek.com/compare/wonek-vs-nextcloud-talk/

Nextcloud Talk appeals to self-hosters who already run Nextcloud files and calendars, yet anyone who has tried Nextcloud Talk across 4G/5G mobile networks knows calls often fail or freeze without manually tuning `coturn` and a High-Performance Backend—and chat messages sit unencrypted on your PHP/SQL server.

**Direct Answer / Verdict:** Choose Nextcloud Talk if you already administer a Nextcloud Linux server with `coturn` and want browser calls tied to your self-hosted PHP cloud. Request early access to Wonek when you want zero-config, high-success direct P2P calls across 4G/5G CGNAT over QUIC, true client-side MLS (RFC 9420) E2EE for messages, calls, CRDT docs, and calendars, plus chunk-resumable P2P file transfers across iPhone, iPad, Mac, and Apple Watch.

**Table 1: Connectivity, Encryption & Workspace Matrix — Wonek vs Nextcloud Talk**

| Capability | Wonek (Pre-Release) | Nextcloud Talk |
| --- | --- | --- |
| 4G/5G Mobile CGNAT Call Setup | Automatic port-predicted QUIC P2P + encrypted relay fallback | Standard WebRTC mesh fails on CGNAT without manual coturn setup |
| Chat Message End-to-End Encryption | Yes — 100% client-side MLS (RFC 9420) E2EE | No — chat text stored unencrypted in Nextcloud SQL database |
| Group Call Scaling | Built-in E2EE group audio, video & screen sharing | Mesh bogged down > 3–4 peers unless High-Performance Backend deployed |
| Collaborative Docs & Calendar | Offline-capable Yjs/Yrs CRDT docs + 5-view Calendar (E2EE) | Collabora/OnlyOffice + CalDAV (plaintext on your server) |
| Large File Transfers | Direct device-to-device P2P with chunk resumption | Uploads to Nextcloud PHP/WebDAV server disk |
| Apple Watch & Push-to-Talk | Native watchOS calling/audio + 1:1 & group PTT | No standalone Apple Watch calling/PTT |

**Table 2: Network & Server Architecture**

| Technical Dimension | Wonek | Nextcloud Talk |
| --- | --- | --- |
| Wire Transport | Native QUIC / WebTransport (TLS 1.3) | HTTPS PHP/Signaling + WebRTC |
| Cryptographic Core | Native Rust MLS (RFC 9420) + Noise QR linking | TLS to your server; DTLS-SRTP on WebRTC leg |
| macOS Client | Native Mac app (chat + calls + screen share + docs) | Primarily web browser or desktop file-sync client |
| Admin & Firewall Tuning | Zero ports to forward, zero coturn configs | Requires UDP port ranges, TLS certs, coturn & Janus/HPB |
| Offline Document Editing | Native CRDT deterministic local merge | Requires active Collabora/OnlyOffice server connection |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended Platform | Why |
| --- | --- | --- |
| Home-lab Linux admin already hosting TB-scale RAID WebDAV storage | Nextcloud Talk | Integrates directly into an existing self-hosted Nextcloud box |
| Reliable mobile calls across 4G/5G without debugging coturn | Wonek | Proprietary port-prediction P2P + automatic encrypted relay fallback |
| True zero-knowledge E2EE where even server disk holds zero plaintext | Wonek | MLS encrypts chats, docs, calendars, calls, and files on device |
| Editing collaborative notes offline on an iPad or MacBook | Wonek | Client-side Yjs/Yrs CRDTs work without a live LibreOffice container |
| Fast native Mac, iPhone, iPad & Watch daily driver | Wonek | No heavy PHP/Collabora browser latency |

#### Ending `coturn` Nightmares on Cellular Networks
Standard WebRTC inside Nextcloud Talk frequently shows a black screen the first time someone dials in from 5G cellular CGNAT until the admin configures `coturn` and firewall UDP ports. Wonek handles mobile CGNAT traversal natively over QUIC—achieving direct P2P links frequently and falling back to latency-measured encrypted relays automatically.

#### Docs, Calendar & Chat—Actually End-to-End Encrypted
Nextcloud combines chat, docs, and calendar nicely, yet your VPS host or anyone breaching the server sees everything in cleartext. Wonek delivers that exact trio—rich chat, CRDT docs, and a 5-view shared calendar—protected by client-side MLS (RFC 9420) encryption.

#### Offline-Capable CRDTs vs Heavy Server Containers
Instead of streaming remote LibreOffice tiles over Docker, Wonek's Yjs/Yrs CRDT documents render natively at 120 Hz on Apple devices and work offline.

#### Frequently Asked Questions
- **Are Nextcloud Talk text chats end-to-end encrypted?** No. While Nextcloud offers an optional encrypted folder module for certain files, Nextcloud Talk chat history resides in your server's database. Wonek encrypts all chats, calls, files, and docs end-to-end on client devices.
- **Do I need to open ports on my home router to use Wonek P2P?** No. Wonek's NAT traversal works automatically with zero manual port forwarding or UPnP setup.
- **Does Wonek include a multi-view calendar like Nextcloud?** Yes—Day, Multi-Day, Month, Year, and List views are built directly into Wonek.

### Wonek vs Keybase: Actively Built MLS + QUIC E2EE, Calls & P2P Files vs Stagnant Keybase
URL: https://wonek.com/compare/wonek-vs-keybase/

Engineers loved Keybase for bringing end-to-end encrypted team rooms, inline code/LaTeX math, and encrypted file sharing into one app—until Zoom acquired Keybase in 2020 and active feature development effectively froze, still lacking native voice/video calls. Wonek carries that torch forward on modern cryptography.

**Direct Answer / Verdict:** Keep legacy Keybase only if you still rely on an archival `keybase://` Git repo or PGP proof. Request early access to Wonek (for Mac, iPhone, iPad, and Apple Watch) for the modern successor engineers wished Keybase became: active Rust MLS (RFC 9420) E2EE, inline code & math formulas, native QUIC P2P HD voice/video & screen sharing, chunk-resumable multi-GB P2P files, CRDT collaborative docs, and shared calendars.

**Table 1: Engineering & Collaboration Matrix — Wonek vs Keybase**

| Capability | Wonek (Pre-Release · Active) | Keybase (Maintenance Mode) |
| --- | --- | --- |
| Development Momentum | Actively engineered on modern QUIC + Rust MLS | Largely stagnant since 2020 Zoom acquisition |
| E2EE Voice, Video & Screen Share | Yes — 1:1 & group HD calls, PiP, PTT & native screen share | None (relied on pasting external Zoom links) |
| Inline Code & Math Formulas | Yes — rich text, inline code, math formulas, edits & pins | Yes — Markdown, code blocks & LaTeX |
| Large File Sharing | Direct P2P over QUIC with chunk-level resumption | KBFS cloud-backed encrypted filesystem |
| Collaborative Docs & Calendar | Built-in Yjs/Yrs CRDT docs + 5-view Shared Calendar | None |
| Personal & Work Profiles + Watch | Personal/Work contexts + native Apple Watch support | Teams sidebar; no Apple Watch calling/PTT |

**Table 2: Cryptographic & Transport Generation**

| Technical Layer | Wonek | Keybase |
| --- | --- | --- |
| Group E2EE Standard | IETF MLS (RFC 9420) O(log N) TreeKEM in Rust | Per-team shared symmetric key boxes (pre-MLS design) |
| Device Provisioning | Authenticated Noise-protocol QR linking | Paper keys & device-to-device sigchain |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | Framed msgpack RPC over TCP/TLS |
| macOS Footprint | Lean native Apple UI + Rust core (no kbfs Finder kernel/FUSE quirks) | Go daemon + Electron UI + macFUSE mount friction |
| Mobile CGNAT Media | Proprietary port-prediction NAT traversal for direct P2P | No native media engine |

**Table 3: Best Fit for Technical Users**

| Need | Recommended App | Why |
| --- | --- | --- |
| Legacy public social-identity sigchain proofs | Keybase | Original identity-proof directory |
| Modern encrypted startup / R&D team hub on Mac & iPhone | Wonek | Actively developed with native calls, screen share, docs & calendar |
| Pair-programming screen share + code/math chat in one E2EE app | Wonek | Never drop out to an external cloud meeting link |
| Sending multi-GB builds & datasets without macFUSE extensions | Wonek | Clean chunk-resumable direct QUIC P2P transfers |
| Forward secrecy & post-compromise healing in group rooms | Wonek | RFC 9420 MLS ratcheting outclasses static team key epochs |

#### Everything Engineers Loved About Keybase—Plus Live Calls & Screen Sharing
Keybase proved that encrypted group chat with LaTeX math, inline code, disappearing timers, and easy device linking could feel joyful—except every time teammates wanted to talk or share a screen, they had to paste a cloud meeting URL.

Wonek brings native 1:1 and group E2EE voice, HD video, Push-to-Talk, and screen sharing right into the encrypted workspace.

#### Upgrading Team Crypto to IETF MLS (RFC 9420) & QUIC
Built in Rust around standardized MLS (RFC 9420) and QUIC / WebTransport, Wonek provides continuous epoch ratcheting, post-compromise security, and snappy native Apple performance without Electron or macFUSE kext headaches.

#### Live CRDT Specs & Shared Sprint Calendars
Co-author architecture RFCs in offline-capable Yjs/Yrs CRDT documents and track milestones across five shared calendar views.

#### Frequently Asked Questions
- **Why are former Keybase Teams users looking for an alternative?** After Keybase's 2020 acquisition, feature development slowed dramatically and native E2EE voice, video, and screen sharing never shipped. Wonek combines technical E2EE chat (code, math, pins, timers) with direct QUIC P2P calls, screen sharing, CRDT docs, and resumable P2P files.
- **Does Wonek require installing macOS kernel extensions like macFUSE?** No. Wonek runs as a clean, standard native macOS app with zero kernel extensions required.
- **How does device provisioning work in Wonek?** Scan an authenticated QR code from your primary device to link your Mac, iPad, or Apple Watch over a Noise-protocol encrypted channel.

### Wonek vs Marco Polo: True End-to-End Encrypted Voice, Live Video, PTT & Messaging
URL: https://wonek.com/compare/wonek-vs-marco-polo/

Marco Polo popularized asynchronous video check-ins for families across time zones, but Marco Polo videos are stored on cloud servers without end-to-end encryption, lack a native Mac desktop app, and lock core features behind subscription upsells. Wonek protects every family moment with true client-side MLS E2EE.

**Direct Answer / Verdict:** Use Marco Polo if your Android/iOS group specifically wants cloud-stored video-story reels with cartoon voice filters. Request early access to Wonek (for iPhone, iPad, Mac, and Apple Watch) when your family or close circle wants true client-side MLS (RFC 9420) E2EE across async voice messages, live Push-to-Talk, HD P2P video calls, original-quality photo album transfers, and a shared 5-view family calendar.

**Table 1: Family & Group Connection Matrix — Wonek vs Marco Polo**

| Capability | Wonek (Pre-Release) | Marco Polo |
| --- | --- | --- |
| End-to-End Encryption | Yes — 100% MLS (RFC 9420) E2EE for all media, calls & chat | No — videos stored in cloud (transport/at-rest encryption only) |
| Live HD Video & Voice Calls | Yes — low-latency direct QUIC P2P calls + PiP + screen share | Asynchronous video walkie-talkie clips only |
| Push-to-Talk & Async Voice Notes | Both live E2EE PTT (iPhone/Mac/Watch) + async voice messages | Async video/voice Polos |
| Original Photo & Video Albums | Direct P2P chunk-resumable transfers without cloud compression | Compressed cloud video clips |
| Native Mac & Apple Watch Apps | Full native macOS, iPadOS, iOS & watchOS apps | Mobile-focused (no native macOS desktop workspace) |
| Shared Family Calendar & Notes | Built-in 5-view Calendar + CRDT family lists/docs | None |

**Table 2: Privacy, Storage & Network Architecture**

| Technical Dimension | Wonek | Marco Polo |
| --- | --- | --- |
| Who Can View Family Videos | Strictly authenticated conversation members (MLS E2EE) | Stored on vendor cloud infrastructure |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | HTTPS cloud uploads/streams |
| Mobile CGNAT Live Calling | Proprietary port-prediction NAT traversal for direct P2P | N/A (cloud store-and-forward clips) |
| iPhone Storage & Resumption | Chunk-level P2P resumption for large family albums | Cloud history retention tiers |
| Work / Family Separation | Dedicated Personal and Work profiles | Single social list |

**Table 3: Best Fit by Family & Group Need**

| Scenario | Recommended App | Why |
| --- | --- | --- |
| Async cartoon-filter video clips across Android & iOS | Marco Polo | Built purely around async video-message reels |
| Keeping kids' & family videos strictly end-to-end encrypted | Wonek | Zero plaintext family videos sitting in third-party cloud buckets |
| Switching between quick Watch PTT, async voice & live HD calls | Wonek | Supports every communication tempo in one app |
| Sharing full-resolution vacation photo albums & calendars | Wonek | Direct P2P album transfers + built-in 5-view shared calendar |
| Helping parents remotely by viewing their iPhone/Mac screen | Wonek | Includes native E2EE screen sharing |

#### Family Videos Belong to Your Family—Not a Cloud Bucket
Parents sharing videos of their children increasingly check whether an app uses true end-to-end encryption. Unlike cloud video-clip apps where servers hold decryptable copies, Wonek encrypts every voice message, Push-to-Talk burst, live video call, and photo album end-to-end via MLS (RFC 9420).

#### Async When Busy, Live P2P When Together
Send asynchronous voice messages across time zones, tap Push-to-Talk from your Apple Watch while cooking, or jump into a live Picture-in-Picture HD video call and screen share.

#### Shared Family Calendars & Packing Lists Built In
Coordinate school schedules in Wonek's 5-view shared calendar and co-edit grocery or trip checklists in offline-capable CRDT docs.

#### Frequently Asked Questions
- **Is Marco Polo end-to-end encrypted?** Marco Polo encrypts data in transit and at rest on its cloud servers, not with client-side end-to-end encryption. Wonek enforces client-side MLS (RFC 9420) end-to-end encryption on all media and messages.
- **Can I send both asynchronous voice messages and live Push-to-Talk in Wonek?** Yes—Wonek includes asynchronous voice notes, live 1:1/group Push-to-Talk, and full bidirectional HD voice/video calls.
- **Can I send full-resolution vacation videos without cloud compression?** Yes, via Wonek's chunk-resumable direct peer-to-peer file and album transfer.

### Wonek vs Cisco Webex: Agile Direct P2P E2EE Calling & Collaboration vs Legacy Suites
URL: https://wonek.com/compare/wonek-vs-webex/

Cisco Webex serves Fortune 500 PBX telefonies and conference-room hardware, yet its desktop suite is notoriously heavy for agile teams, and Zero-Trust E2EE meetings require explicit scheduling trade-offs. Wonek brings instant native Apple speed with default MLS E2EE and direct QUIC P2P media.

**Direct Answer / Verdict:** Choose Cisco Webex when your enterprise relies on Cisco SIP room hardware, PBX call centers, and cross-OS FedRAMP compliance. Request early access to Wonek when your Mac, iPad, iPhone, and Apple Watch team wants zero-bloat native speed, always-on MLS (RFC 9420) E2EE across chat, calls, screen shares, and files, direct P2P media across 4G/5G CGNAT, CRDT docs, and a built-in 5-view calendar.

**Table 1: Agility, Security & Workspace Matrix — Wonek vs Webex**

| Capability | Wonek (Pre-Release) | Cisco Webex |
| --- | --- | --- |
| Default E2EE Across Everything | Automatic MLS (RFC 9420) for all calls, chats, files & docs | Standard meetings cloud-processed; E2EE requires special session type |
| App Launch & Call Friction | Sub-second native Apple UI; 1-tap call or PTT | Heavy enterprise suite, meeting lobbies & account portals |
| Large File Sharing | Direct P2P over QUIC with chunk-level resumption | Cloud space uploads governed by admin retention |
| Collaborative Docs & Calendar | Built-in Yjs/Yrs CRDT docs + 5-view Shared Calendar | External Microsoft 365 / Google calendar connectors |
| Apple Watch Calling & PTT | Native watchOS audio, calling & 1:1/group PTT | Minimal notification/companion features |
| Personal & Work Contexts | Clean Personal + Work profiles in one lightweight app | Strictly corporate IT tool |

**Table 2: Cryptographic & Transport Comparison**

| Technical Dimension | Wonek | Cisco Webex |
| --- | --- | --- |
| Cryptographic Core | Native Rust IETF MLS (RFC 9420) + Noise QR | Cisco KMS cloud keys + optional MLS Zero-Trust mode |
| Primary Media Routing | Direct device-to-device P2P over QUIC + encrypted relay | Cisco cloud media nodes |
| Wire Transport | QUIC / WebTransport with mandatory TLS 1.3 | HTTPS / SIP / WebRTC / Cisco media UDP |
| Mobile CGNAT Optimization | Proprietary port-prediction NAT traversal for direct P2P | Cloud relay media termination |
| Offline Document Sync | Conflict-free client CRDT merge | Cloud-dependent |

**Table 3: Best Fit by Organization**

| Scenario | Recommended Platform | Why |
| --- | --- | --- |
| 10,000-seat bank with Cisco Desk Pro room hardware & PSTN | Cisco Webex | Deep hardware SIP & enterprise PBX integration |
| Fast-moving founders, legal/security advisors & Apple dev teams | Wonek | Zero enterprise IT bloat; mandatory client-side E2EE everywhere |
| Low-latency P2P code screen shares & multi-GB file drops | Wonek | Direct QUIC P2P keeps text sharp and resumes interrupted chunks |
| Switching between executive calls, Watch PTT & offline docs | Wonek | Unified native Apple workflow |
| Separating advisory client work from personal family life | Wonek | Built-in Personal and Work profiles |

#### Enterprise-Grade MLS Cryptography Without Enterprise Bloat
Cisco itself contributed to the IETF MLS standard because legacy key exchange struggled at scale—yet in Webex, true end-to-end encryption remains gated behind specific Zero-Trust meeting configurations while standard spaces rely on cloud Key Management Servers.

Wonek gives every user pure client-side MLS (RFC 9420) by default in a nimble, native Apple app.

#### Direct QUIC P2P Instead of Mandatory Cloud Hair-Pinning
Two colleagues on the same city fiber or 5G network connect directly peer-to-peer whenever possible via Wonek's smart NAT traversal over QUIC.

#### Integrated CRDT Docs, Shared Calendar & Watch PTT
Co-edit confidential memos offline or live, check five calendar views, and coordinate on Apple Watch without juggling external cloud licenses.

#### Frequently Asked Questions
- **Does Wonek require an IT administrator to turn on End-to-End Encryption?** No. Client-side MLS (RFC 9420) E2EE is always active for every user and every conversation in Wonek.
- **What happens when corporate guest Wi-Fi blocks UDP?** Wonek automatically switches to a latency-measured encrypted relay fallback while keeping all media end-to-end encrypted.
- **Is Wonek native on Apple Silicon Macs?** Yes—engineered natively for macOS, iOS, iPadOS, and watchOS.

### Wonek vs Keet (Holepunch): Mobile CGNAT Resilience, Offline Queue, MLS & Apple Watch
URL: https://wonek.com/compare/wonek-vs-keet-holepunch/

Keet (built on Holepunch/Hyperswarm) is an exciting pure serverless P2P experiment, yet pure swarm apps face a hard physics wall on iPhones: if you send a text and close your laptop before your offline friend wakes up, nobody is online to seed the message—and strict corporate firewalls with zero UDP block pure P2P completely.

**Direct Answer / Verdict:** Explore Keet if you want to experiment with serverless Hyperswarm DHT rooms on desktop. Request early access to Wonek (for iPhone, iPad, Mac, and Apple Watch) when you want direct P2P speed AND everyday mobile reliability: proprietary port-prediction P2P across 4G/5G CGNAT over QUIC, automatic encrypted relay fallback on UDP-blocked Wi-Fi, a ciphertext-only offline message queue so texts never stall when peers sleep, IETF MLS (RFC 9420), Apple Watch PTT, CRDT docs, and shared calendars.

**Table 1: Real-World Mobile & Workspace Matrix — Wonek vs Keet**

| Capability | Wonek (Pre-Release) | Keet (Holepunch) |
| --- | --- | --- |
| Async Delivery When Both Peers Miss Each Other | Guaranteed — ciphertext-only offline queue delivers on wake | Stalls unless at least one online peer/blind-peer stays awake |
| Corporate / Hotel Wi-Fi Blocking All UDP | Connects automatically via latency-measured encrypted relay | Pure UDP swarm connections can fail completely |
| Direct P2P Calls & Multi-GB Files | Yes — QUIC P2P with chunk-level file resumption | Yes — Hyperswarm P2P calls & file drops |
| Apple Watch & Push-to-Talk | Native watchOS calling/audio + 1:1 & group E2EE PTT | No Apple Watch app or dedicated PTT mode |
| Collaborative Docs & Calendar | Built-in Yjs/Yrs CRDT docs + 5-view Shared Calendar | Chat/calls/files only |
| Personal & Work Separation | Dedicated Personal + Work profiles | Room list only |

**Table 2: Networking, Cryptography & iOS Battery Specs**

| Technical Dimension | Wonek | Keet |
| --- | --- | --- |
| Transport Foundation | Standardized QUIC / WebTransport with mandatory TLS 1.3 | Hypercore / Hyperswarm custom UDP/UDX |
| NAT Traversal on 4G/5G CGNAT | Proprietary port-prediction NAT traversal | Hyperswarm hole punching over DHT |
| End-to-End Encryption Standard | Peer-reviewed IETF MLS (RFC 9420) in native Rust core | Noise + Hypercore capability keys |
| iOS Background Battery Profile | Clean push wakeup without background DHT churn | Swarm replication stops when iOS suspends background app |
| Native Apple UI | Native iOS, iPadOS, macOS & watchOS | Pear / cross-platform runtime |

**Table 3: Best Fit by Scenario**

| Scenario | Recommended App | Why |
| --- | --- | --- |
| Testing pure serverless DHT room links on always-on desktops | Keet | Zero server infrastructure experiment |
| Daily iPhone + Mac messenger where offline friends always get texts | Wonek | Ciphertext-only offline queue solves iOS sleep physics cleanly |
| Taking urgent calls from strict hospital, airport, or office Wi-Fi | Wonek | Encrypted relay fallback guarantees the call connects when UDP is blocked |
| Apple Watch PTT, CRDT docs & 5-view shared calendar | Wonek | Complete native Apple productivity & communication suite |
| Auditable IETF-standardized group forward secrecy | Wonek | RFC 9420 MLS epoch ratcheting and post-compromise security |

#### Pragmatic Hybrid P2P Beats Dogmatic 'Zero-Server' Failures on Mobile
Pure P2P purism breaks the moment Alice texts Bob before boarding a flight while Bob's iPhone is in a subway tunnel: with both devices offline at different times, a serverless swarm cannot deliver the message.

Wonek solves this without compromising privacy: live calls and large files route directly peer-to-peer over QUIC whenever possible, while sleeping recipients receive opaque MLS-encrypted ciphertext queued cleanly until wake—and UDP-blocked networks fall back to encrypted relays.

#### IETF MLS (RFC 9420) Forward Secrecy & Native Apple Craft
Wonek implements standardized MLS ratcheting inside a compiled Rust core paired with native Swift/Apple interfaces across iPhone, iPad, Mac, and Apple Watch.

#### Chunk-Resumable Files + CRDT Docs + Shared Calendar
Enjoy direct device-to-device multi-gigabyte file speed alongside offline-capable Yjs/Yrs collaborative documents and five built-in calendar views.

#### Frequently Asked Questions
- **Why do pure P2P apps miss messages on iPhones?** iOS suspends background network sockets to save battery. If sender and receiver aren't awake simultaneously, pure P2P has nowhere to hand the packet. Wonek uses a ciphertext-only offline queue so messages always arrive on wake while servers never hold decryption keys.
- **Does Wonek still send calls and large files directly peer-to-peer?** Yes! Direct device-to-device P2P over QUIC is always Wonek's primary path, enhanced by proprietary port-prediction NAT traversal for mobile CGNAT.
- **What if a firewall completely blocks UDP?** Wonek automatically transitions to a latency-measured encrypted relay so your E2EE call never fails to connect.

### Port-Predicted NAT Traversal vs Standard STUN/TURN WebRTC on 4G/5G Mobile CGNAT
URL: https://wonek.com/compare/port-predicted-p2p-vs-standard-stun-turn-webrtc/

Standard WebRTC ICE was designed in an era of home broadband routers. When two smartphones on modern 4G/5G Carrier-Grade NAT (CGNAT) call each other, naive STUN checks routinely fail and punt the entire media stream onto cloud TURN relays. Smart port-predicted NAT traversal unlocks direct peer-to-peer paths far more often.

**Direct Answer / Verdict:** Standard STUN/TURN WebRTC works fineinside browsers and on simple home Wi-Fi Cone NATs, provided you budget heavily for global TURN relay bandwidth on mobile calls. Wonek's proprietary port-prediction NAT traversal over QUIC / WebTransport achieves a much higher direct P2P connection rate across difficult 4G/5G mobile CGNAT networks—delivering lower call latency and faster direct file transfers, while retaining automatic latency-measured encrypted relay fallback when firewalls block UDP completely.

**Table 1: Connectivity Outcome Matrix Across Real-World NAT Topologies**

| NAT Pair Topology | Standard STUN / ICE WebRTC | Wonek Port-Predicted QUIC P2P |
| --- | --- | --- |
| Home Wi-Fi <-> Home Wi-Fi (Full/Restricted Cone) | Direct P2P succeeds | Direct QUIC P2P succeeds (TLS 1.3 + MLS E2EE) |
| Home Wi-Fi <-> 4G/5G Mobile CGNAT | Mixed — frequently falls back to TURN relay | High-success direct P2P path established |
| 4G/5G Mobile CGNAT <-> 4G/5G Mobile CGNAT | Fails direct ICE most of the time -> cloud TURN relay | Frequently establishes direct device-to-device P2P link |
| Symmetric / Restricted Carrier Gateways | Assumes STUN port stays static; times out to TURN | Proprietary port-prediction algorithm finds direct link |
| Enterprise Firewall Blocking 100% of UDP | Falls back to TURN over TCP/TLS | Automatic latency-measured encrypted relay fallback |
| Wi-Fi-to-5G Mid-Call Roaming | Full ICE restart & media pause | Smooth QUIC path migration & fast re-validation |

**Table 2: Protocol Stack & Media Impact Comparison**

| Architectural Layer | Wonek Stack | Classic WebRTC Stack |
| --- | --- | --- |
| Transport Protocol | Unified QUIC / WebTransport (RFC 9000) | Split RTP/SRTP + SCTP + DTLS + separate WebSocket |
| Wire Security | Mandatory built-in TLS 1.3 from first handshake | Separate DTLS-SRTP media + TLS signaling |
| Application E2EE | Client-side IETF MLS (RFC 9420) in Rust core | Often hop-by-hop to SFU unless Insertable Streams/SFrame added |
| Round-Trip Call Latency on 5G | Shortest physical ISP peering route on direct P2P | Inflated by detour through nearest cloud TURN region |
| Multi-Gigabyte File Throughput | Full direct peer upload-to-download pipe + chunk resume | Throttled by TURN relay bandwidth caps & SCTP quirks |

**Table 3: Real-World User Experience Impact**

| User Scenario | Winning Architecture | Why Users Feel It |
| --- | --- | --- |
| Two people in the same city calling over 5G cellular | Port-Predicted QUIC P2P (Wonek) | Avoids hair-pinning voice packets through a foreign cloud region |
| Sending a 4 GB ProRes video shoot from iPhone on 5G to Mac | Port-Predicted QUIC P2P (Wonek) | Direct peer pipe runs at line rate with chunk-level resumption |
| Zero-install guest call inside a legacy desktop browser | Standard Browser WebRTC | Built into Chromium/WebKit without installing a native app |
| Screen sharing small 12pt code text with instant cursor response | Port-Predicted QUIC P2P (Wonek) | Lower RTT congestion loop keeps high-resolution frames crisp |
| Calling from locked-down hospital guest Wi-Fi | Both (via Encrypted Fallback) | Wonek automatically uses its latency-measured encrypted relay |

#### Why Naive STUN Assumptions Fail on Cellular Networks
A classic STUN check asks one cloud server 'What external IP and port did you see me come from?' and assumes the mobile carrier's NAT gateway will reuse that exact external port when talking to a completely different peer IP. Modern Carrier-Grade NAT gateways frequently allocate fresh ports per destination—rendering the STUN coordinate obsolete before the first packet arrives.

Instead of immediately surrendering to a slow cloud relay, Wonek employs a proprietary port-prediction NAT traversal algorithm engineered for real-world CGNAT behavior, achieving direct encrypted QUIC peer-to-peer sessions at a markedly higher rate.

#### Dual-Layer Security Regardless of Direct or Relay Path
Whether traffic flows directly peer-to-peer across 5G or transitions automatically onto a latency-measured relay behind strict corporate Wi-Fi, every packet is protected twice: mandatory QUIC TLS 1.3 wire security plus client-side MLS (RFC 9420) end-to-end encryption.

#### Direct Bandwidth Unlocks Chunk-Resumable Large Transfers
Eliminating unnecessary cloud relays doesn't just shave voice latency—it lets Wonek stream multi-gigabyte files and photo albums directly between Apple devices with automatic chunk-level resumption.

#### Frequently Asked Questions
- **Does direct P2P work on every single network on earth?** No physical UDP protocol can punch through a firewall that drops 100% of UDP packets—which is why Wonek pairs high-success port-predicted P2P with automatic latency-measured encrypted relay fallback so calls always connect.
- **Is my media still encrypted when flowing directly peer-to-peer?** Yes—doubly so: QUIC enforces TLS 1.3 transport encryption on the wire, and Wonek's Rust MLS (RFC 9420) core encrypts payloads end-to-end between authorized devices.
- **Why does reducing relay fallback improve voice quality?** Direct paths lower round-trip latency and jitter, preventing awkward talk-over collisions while Opus audio and echo cancellation keep voices crisp.

### QUIC & WebTransport Messengers vs Legacy TCP WebSocket Chat Apps
URL: https://wonek.com/compare/quic-webtransport-chat-vs-legacy-tcp-websocket-messengers/

Nearly every mainstream messenger built between 2010 and 2022 relies on a single persistent TCP WebSocket for signaling and chat. On lossy mobile networks, TCP's strict single-byte-stream ordering creates head-of-line blocking that freezes typing, edits, and signaling whenever one packet drops. QUIC and WebTransport change the rules.

**Direct Answer / Verdict:** Legacy TCP WebSockets remain simple to terminate behind decade-old HTTP/1.1 load balancers, which is why older chat apps still run on them. For modern mobile and desktop real-time communication, Wonek's native QUIC / WebTransport stack wins decisively—delivering zero cross-stream head-of-line blocking, faster TLS 1.3 handshakes, unified chat + voice/video + P2P file streaming, and smooth Wi-Fi-to-5G roaming.

**Table 1: Transport Behavior Under Real Mobile Conditions**

| Condition | Legacy TCP WebSocket Messengers | Wonek (QUIC / WebTransport) |
| --- | --- | --- |
| 2% Packet Loss on Train or Café Wi-Fi | Single dropped packet stalls entire WebSocket queue | Only the affected QUIC stream waits; chat & PTT flow freely |
| Uploading 2 GB Video While Texting | Socket contention or separate HTTP upload stack needed | Dedicated parallel QUIC streams with zero chat lag |
| App Wakeup Handshake Latency | TCP SYN/ACK + TLS 1.2/1.3 = 2–3 round trips | Combined QUIC + TLS 1.3 handshake in 1-RTT (0-RTT capable) |
| Stepping Out of Wi-Fi Range Onto 5G | TCP 4-tuple breaks; connection drops & reconnects | QUIC Connection ID migrates session cleanly across IPs |
| Real-Time Voice & Push-to-Talk | Requires bolting on a second WebRTC stack | Unified streams + low-latency datagrams on one protocol |
| Header Metadata Protection | TCP sequence/ACK headers exposed in cleartext | QUIC encrypts transport control frames via TLS 1.3 |

**Table 2: Protocol Engineering Specs**

| Specification | QUIC / WebTransport (Wonek) | TCP + TLS + WebSocket |
| --- | --- | --- |
| IETF Standards | RFC 9000 (QUIC), TLS 1.3 (RFC 8446), WebTransport | RFC 9293 (TCP), RFC 6455 (WebSocket) |
| Multiplexing Model | Native independent bidirectional & unidirectional streams | Single ordered byte stream per TCP socket |
| Unreliable Real-Time Datagrams | Supported natively for low-latency media frames | Impossible over TCP (forced retransmissions add lag) |
| Congestion Control | Modern user-space congestion feedback & pacing | OS-kernel bound TCP congestion state |
| Paired E2EE Layer in Wonek | Client-side MLS (RFC 9420) + CRDT state sync | Varies (often cloud-decrypted JSON) |

**Table 3: Where Users Notice QUIC Most**

| Everyday Moment | TCP WebSocket Result | Wonek QUIC Result |
| --- | --- | --- |
| Opening app in an elevator with 1 bar of 5G | Spinner hangs 'Connecting…' for several seconds | 1-RTT TLS 1.3 handshake delivers queued ciphertext fast |
| Walking out the front door during a live voice call | 5-second robotic silence or dropped call | Connection ID preserves call across Wi-Fi -> 5G switch |
| Co-editing a CRDT doc while transferring a photo album | Keystrokes stutter behind upload buffers | CRDT deltas fly on an independent prioritized stream |
| Quick Apple Watch Push-to-Talk burst outdoors | Slow socket setup eats the first second | Rapid QUIC stream/datagram transmission |
| Resuming a paused 5 GB archive transfer | Restarts HTTP POST from byte zero | Chunk-level resumption picks up immediately |

#### Killing Head-of-Line Blocking Once and For All
In a TCP WebSocket messenger, every message, reaction, read receipt, CRDT keystroke, and thumbnail shares a single ordered pipe. One lost packet stalls everything behind it. QUIC gives Wonek lightweight independent streams inside a single connection so chat, collaborative docs, and multi-gigabyte file chunks never block one another.

#### Seamless Roaming Across Wi-Fi and Cellular
Because QUIC keys connections by Connection IDs rather than fragile IP addresses, stepping out of your office Wi-Fi onto 5G no longer tears down your active call or file transfer.

#### Mandatory TLS 1.3 Plus Client-Side MLS E2EE
QUIC's built-in TLS 1.3 protects wire transport metadata from passive observers, while Wonek's Rust MLS (RFC 9420) core guarantees end-to-end content confidentiality.

#### Frequently Asked Questions
- **What is head-of-line blocking in plain English?** Imagine ten checkout lanes forced to wait because one shopper dropped a coin. TCP forces all data behind one lost packet to wait; QUIC gives different tasks separate lanes so texts and voice keep moving even if a file chunk retransmits.
- **What happens if an older router blocks QUIC/UDP?** Wonek automatically detects strict UDP blocks and routes via its latency-measured encrypted fallback so you stay connected without changing settings.
- **Does QUIC replace MLS end-to-end encryption?** No—Wonek uses both together: QUIC TLS 1.3 secures the wire transport, and MLS (RFC 9420) encrypts content end-to-end between your devices.

### IETF MLS (RFC 9420) vs Pairwise Double Ratchet for Group & Multi-Device E2EE
URL: https://wonek.com/compare/mls-end-to-end-encryption-vs-signal-double-ratchet-for-groups/

The Double Ratchet revolutionized 1:1 mobile encryption in 2013, when most people used a single smartphone. Today, a 30-person team using iPhones, iPads, Macs, and Apple Watches represents over 100 cryptographic endpoints—where pairwise ratchets hit O(N) scaling walls that IETF MLS (RFC 9420) solves in O(log N).

**Direct Answer / Verdict:** Pairwise Double Ratchet remains rock-solid for simple two-phone messaging. For modern multi-device Apple ecosystems (iPhone + iPad + Mac + Apple Watch) and active group collaboration across chat, calls, files, and CRDT docs, IETF MLS (RFC 9420)—implemented in Wonek's native Rust cryptographic core—delivers dramatically cleaner O(log N) key rotation, faster post-compromise healing, and formal IETF standardization.

**Table 1: Cryptographic Scaling & Capability Matrix — MLS (RFC 9420) vs Double Ratchet**

| Property | IETF MLS — RFC 9420 (Wonek) | Pairwise Double Ratchet + Sender Keys |
| --- | --- | --- |
| Adding / Removing Member or Rotating Key | O(log N) via binary TreeKEM ratcheting tree | O(N) — linear pairwise fan-out to every device |
| Post-Compromise Security in Groups | Single Commit heals shared group secret for all | Requires full pairwise re-distribution when members change |
| Forward Secrecy | Continuous epoch & sender-ratchet forward secrecy | Strong per-chain forward secrecy |
| Multi-Device Representation | Native leaf per enrolled iPhone, iPad, Mac & Watch | Simulated as N separate pairwise chats ('sesame') |
| Asynchronous Offline Key Updates | Native KeyPackages allow updating while peers sleep | Prekeys work 1:1; group Sender Keys frequently desync |
| Standardization Status | Published IETF Standard RFC 9420 (2023) | De-facto industry specification (non-IETF RFC) |

**Table 2: How Wonek Pairs MLS With Device & Transport Security**

| Security Layer in Wonek | Technology Used | Security Guarantee |
| --- | --- | --- |
| Group & 1:1 Content Layer | MLS (RFC 9420) in memory-safe Rust core | End-to-end confidentiality, authenticity, FS & PCS |
| Multi-Device Enrollment | Noise-protocol QR authenticated channel | Zero cloud private-key escrow when linking Mac/iPad/Watch |
| Wire Transport Layer | QUIC / WebTransport with mandatory TLS 1.3 | Dual-layer encryption against passive network snooping |
| Collaborative Docs State | Yjs/Yrs CRDT updates inside E2EE boundary | Conflict-free offline merges without server plaintext |
| Offline & Relay Nodes | Ciphertext-only queues & encrypted fallback relays | Servers never possess MLS epoch decryption keys |

**Table 3: Practical Impact for Users & Teams**

| Real-World Situation | Pairwise / Sender Keys Quirk | MLS (RFC 9420) in Wonek |
| --- | --- | --- |
| Opening your MacBook after a week offline | Slow catch-up or 'Waiting for this message' placeholders | Clean epoch tree sync across enrolled leaf devices |
| 25-person team with 4 Apple devices each (~100 leaves) | 100x pairwise key distribution overhead on membership change | ~7 tree steps (log2 100) to refresh group secret |
| Removing a departing contractor from 15 Work channels | Expensive full Sender Key resets across every device | Immediate O(log N) leaf removal & fresh epoch key |
| Rotating call & screen-share media keys | Separate ad-hoc group call key distribution | Derives authenticated epoch secrets cleanly from MLS group |
| Auditing protocol design | App-specific custom extensions for groups | Uniform peer-reviewed IETF RFC 9420 specification |

#### Why TreeKEM Changes the Math of Multi-Device Groups
When Alice, Bob, and 28 teammates each carry an iPhone, an iPad, a Mac, and an Apple Watch, a single group room actually contains roughly 100 client devices. Pairwise protocols treat those 100 devices like 100 separate pipes whenever group keys rotate after a member leaves or recovers from compromise.

MLS (RFC 9420) arranges devices as leaves of a binary cryptographic tree (TreeKEM). Updating any device's secret hashes up only its direct path to the root—requiring roughly seven cryptographic operations instead of a hundred.

#### Ending 'Waiting for This Message' Multi-Device Desyncs
Because MLS was designed from scratch for asynchronous multi-device environments, waking up an iPad or Mac after days in a backpack syncs epochs cleanly without stranded pairwise sessions.

#### Memory-Safe Rust Core + Noise QR Enrollment in Wonek
Wonek runs its MLS engine inside a native Rust library shared across iOS, iPadOS, macOS, and watchOS, pairing it with Noise-protocol QR device linking and QUIC TLS 1.3 transport.

#### Frequently Asked Questions
- **Who standardized MLS (RFC 9420)?** Messaging Layer Security (RFC 9420) was developed over five years by the Internet Engineering Task Force (IETF) with academic cryptographers and major security engineering teams.
- **Does MLS still protect simple 1:1 chats just as strongly as groups?** Yes—a 1:1 chat across your iPhone, Mac, and Apple Watch is already a multi-device group of 4–6 endpoints! MLS provides forward secrecy and post-compromise security for both 1:1 and group conversations.
- **Where can I read more about Wonek's dual-layer security?** Visit https://wonek.com/security/ for a complete breakdown of Wonek's MLS E2EE, Noise QR linking, QUIC TLS 1.3 transport, and ciphertext-only server boundaries.