👨‍💻 Creator

WaveLite was created by Chandan Maurya in Bengaluru, India, in 2025. Driven by the lack of truly private messaging solutions that don't rely on centralized servers, Chandan set out to build a peer-to-peer communication tool where privacy, simplicity, and user freedom come first.

What began as a personal challenge has grown into a complete application that lets people chat and share media directly with each other — without a central server storing their conversations.

🌐 About WaveLite

WaveLite v3.0.0 is a modern, lightweight, peer-to-peer messaging application built on WebRTC. It connects two browsers directly, so messages, files, and media travel straight from one device to the other — no accounts, no registration, and no central message server.

The only server-side component is a small Cloudflare-based signaling service that helps the two peers find each other by exchanging connection details (SDP offers and answers). Once the handshake is complete, all communication flows directly browser-to-browser.

✨ Features

• Serverless peer-to-peer messaging powered by WebRTC
• Cloudflare-based signaling — SDP exchange only, no message relay
• No accounts or registration — connect with a shared Connection Key
• Ready button workflow with automatic connection establishment
• Share images, videos, audio, and documents
• Capture and share photos with your device camera
• Record voice messages from the browser
• Record video from the browser
• Share your location with an embedded map preview
• Tap-to-view image preview inside the chat
• Secure Mode — encrypts text messages (text only)
• Modern iOS-inspired interface with theme customization
• Developer Options for advanced users — STUN/TURN, chat and homepage customization, and optional AI Chat

⚙️ How WaveLite Works

1. Create a profile with a display Name and a shared Connection Key.
2. You and your peer use the same Connection Key to pair with each other.
3. Press Ready. WaveLite generates a WebRTC offer and sends it to the Cloudflare-based signaling service.
4. When your peer presses Ready too, the signaling service matches the pair and returns an answer.
5. The two browsers connect directly over WebRTC DataChannels. Messages and files now flow browser-to-browser.
6. The signaling service is used only for the initial handshake — it never handles message content.

🛡️ Security & Benefits

• No central message server — nothing is stored
• Messages and files travel only between the two connected browsers
• No accounts or registration — your identity is just a name and a key you choose
• Signaling handles only the SDP handshake, never your content
• Secure Mode encrypts text messages
• Lightweight, fast, and privacy-focused by design