Building a no-login WebRTC app with Node.js: How we reached 65K organic Google clicks in 28 days (Zero Ads)

Hey everyone,

Over the past month, I experimented with a simple idea:
What happens if you remove all friction from a product?

Most chat platforms require users to:

• create an account
• verify email or phone
• share personal data

For something as simple as starting a conversation, this felt unnecessary.

So instead of following the usual approach (DB + OAuth + verification), I built a completely anonymous, browser-based system:

• no login
• no registration
• no tracking
• instant connection

You open the page and you're immediately in a live session.

Tech stack & architecture

To keep everything fast and lightweight, I used:

• WebRTC for peer-to-peer communication
• Node.js + Socket io for signaling

The server only handles:

• session creation
• SDP exchange
• ICE candidates

Once the WebRTC handshake is complete, everything (text, audio, video) flows directly between peers.

Biggest challenge

Without user accounts, everything becomes stateless and temporary.

That created challenges around:

• socket lifecycle management
• handling unexpected disconnects
• maintaining room states (especially for region-based rooms)

A lot of effort went into making the signaling layer reliable under these constraints.

##Growth: 65K clicks in 28 days

The biggest change wasn’t technical — it was removing friction.

Because users don’t need to sign up:

• entry barrier is zero
• drop-offs are minimal
• sessions start instantly

This led to:

• very low bounce rate
• higher session duration
• strong engagement signals

Combined with targeting long-tail queries like:

• “chat without login”
• “anonymous video chat instant”

the site grew to ~65,000 clicks from Google Search in 28 days, without any paid ads.

##What I built

To test this idea, I created a simple page for random video chat without login:
https://chatzyo.in/

##Key takeaway

Simplicity is not a limitation — it’s a growth strategy.

Instead of adding features, removing steps made a bigger impact on both UX and SEO.

Question

For those building real-time apps:

How are you handling scaling for signaling servers when traffic spikes unpredictably?

Would love to hear how others are solving this.