Case study · Doktorsitesi.com
Doctor Messaging & Network
End-to-end encrypted messaging with simultaneous real-time conversations between doctors, plus a LinkedIn-style network to connect, request, and grow professional relationships on Doktorsitesi — powered by Supabase Realtime and Postgres.
Context & role
At Doktorsitesi.com I owned this product end-to-end as Product & Project Specialist: defining the PRD, shaping the messaging and network backlog, coordinating sprint delivery with the Supabase-backed stack, and overseeing stage and production testing with doctor-facing stakeholders.
The problem
Doctors on the platform had no secure, native way to message peers in real time or manage professional connections in one place — conversations scattered across channels, and networking happened outside Doktorsitesi.
The solution
We shipped Doctor Messaging & Network on Supabase: E2E encrypted payloads persisted in Postgres, Realtime channels for simultaneous p2p delivery across multiple inboxes, and a connection graph so doctors can request, accept, and browse their network without leaving the product.
Doctor message flow
Scroll into view to watch the stack: Doctor A sends an encrypted payload, Supabase Postgres persists it, Realtime fans out to Doctor B, and the connections row links both profiles.
Doctor A · mobile
Dr. Ayşe K.
Cardiology
Supabase backend
Supabase
ds-messaging-prod
Postgres
messages · threads
Realtime
p2p fan-out
RLS
doctor-scoped rows
Postgres writes
Simultaneous p2p
Multiple doctor threads share one Realtime channel map — each inbox subscribes to its thread IDs.
Doctor B · mobile
Dr. Mehmet Y.
Internal med
- 1Doctor A encrypts & sends message
- 2Supabase Postgres stores ciphertext
- 3Realtime broadcasts to peer inbox
- 4connections row links both doctors
Product capabilities
What doctors get in one surface — secure messaging, a professional network, and an inbox built for simultaneous conversations, backed by Supabase.
Messaging
Doctors chat in E2E encrypted threads with Supabase Realtime delivery — built for clinical peers running multiple conversations at once.
Network
A LinkedIn-style connection system: send requests, accept invites, and see affiliated doctors in one professional graph stored in Postgres.
Inbox
An inbox that supports multiple simultaneous p2p threads — each doctor subscribes to their thread IDs over Realtime without blocking other chats.
Outcomes
- Doctors can message peers securely without leaving Doktorsitesi
- Supabase Realtime keeps simultaneous conversations live across devices
- Professional connections stay traceable next to each doctor profile in Postgres
What's next
Want more context on how I ship real-time healthcare product work with Supabase, or to talk about a similar messaging or network problem?