Hey hunters! 👋 I’m Anupam Jha, a 17-year-old indie developer from New Delhi, India. I built Incogniq because I wanted to solve a major issue with modern 'private' messaging apps: the compromise of anonymity. Even when apps use End-to-End Encryption, they still force you to provide a phone number, scan your contacts, and log metadata about who you speak to and when. I wanted to build a communication tool that takes zero identity from the user, operating completely client-side in the browser. Incogniq routes audio, video, text, and files directly browser-to-browser via WebRTC. To give power back to self-hosters and developers, I built a 'Bring Your Own Database' option. You can connect your own Turso SQLite database in settings, routing all signaling handshake records through your own database instead of mine. What you can do right now: - Enter the Global Chat to meet people instantly. - Create a Private Room and share the 4-digit PIN for an encrypted voice/video call or file share. - Schedule a secure room with a custom timer countdown and passcode. I would love to get your feedback on the WebRTC performance, the design, and the signaling database integration. Thank you for your support! 🚀

Incogniq

P2P WebRTC chat with zero-identity and custom DB signaling.

P2P WebRTC chat with zero-identity and custom DB signaling.