Why Telpun?

Real-time is powerful. But setting it up? Ugh.

WebSocket servers. Pub/sub infra. Authentication layers. Fallbacks. Boilerplate. You just want to send an event and see it show up on the client. Simple as that. That’s why we built Telpun.


πŸš€ What Telpun gives you

  • Zero setup β€” Just send an HTTP request to publish events.
  • Instant delivery β€” Clients subscribe with EventSource. No WebSocket headache.
  • MVP-friendly β€” Build realtime apps without realtime infra.
  • Language agnostic β€” Works with PHP, Go, Python, Laravel, Node, etc.
  • Works anywhere β€” Serverless, VPS, shared hosting.

πŸ› οΈ Built for developers who move fast

Perfect for:

  • Live dashboards
  • Real-time notifications
  • Chat apps or game lobbies
  • IoT/sensor data feeds
  • Realtime presence/status systems

πŸ’¬ How it works

  1. Client subscribes with EventSource.
  2. Your backend sends events to Telpun.
  3. Telpun handles delivery, scaling, and connections.
Send an event (backend):
curl -X POST https://telpun.com/hub?key={publisherkey} \
  -H "Content-Type: application/json" \
  -d '{
    "event": "notification",
    "data": { "text": "Hello, world!" }
  }'
Listen to event (frontend):
const source = new EventSource('https://telpun.com/hub?key={subscriberkey}&events=notification');
source.addEventListener('notification', e => {
  console.log(JSON.parse(e.data))
})

//you can subscribe to multiple event with comma sparated (notification,chat,test)

✨ Focus on building, not plumbing

Telpun handles:

  • Connection management
  • Event delivery
  • Scaling
  • Developer happiness πŸ˜„