A few months back we wrote about why we added in-app voice calling to Lami — the "Voice calling on Lami — the safer way to meet your match" post walked through the privacy story. This week we shipped the next step: in-app video calling between matched Gold and Platinum users. As far as we can tell, Lami is the only Nepal-built matrimonial site with this feature. The India-based apps (Jeevansathi, Shaadi, BharatMatrimony) have video calling too — they got there before us — but they got there as part of an Indian product adapted for Nepali users, not a Nepali product designed for Nepali users from day one. That distinction matters more than it sounds, and the rest of this post is about why.
Why video is the next step (not the first one)
We did voice first on purpose. Voice is anonymizing — your tone identifies you to your match, but not to a screenshot, not to a reverse image search, not to a leaked file. The risk profile is closer to a phone call. Video has a different shape of risk: your face on someone else's screen is, in the moment, harmless. But screens get captured. And in a country where family honor still drives a lot of marriage logistics, a captured screenshot can travel through WhatsApp groups in ways that nobody on the original call intended.
We could have skipped video entirely for that reason. We chose not to, because the safer pattern is already understood culturally: families in Nepal expect to see their potential match — and to be seen — before a visit is arranged. The bihey decision is rarely made by just the two people on a call. It is normal for a girl's phupu, mama, or didi to step into the frame, ask a question, then step out. The traditional in-person "girl-seeing" appointment exists for exactly this reason. Video calling, done well, makes that introduction safer and more egalitarian — both sides get a proper look, the diaspora half doesn't have to fly home for it, and the entire interaction stays inside an audited app instead of getting trade-passed onto WhatsApp.
What we shipped, in plain words
The implementation is conventional and that's the point:
- WebRTC peer-to-peer video, mic + camera captured on each device with EC/NS/AGC. The video stream never touches Lami servers — we relay signaling only, never the call itself.
- TURN relay when needed (most cross-network Nepali calls need it because of carrier symmetric NAT). The relay sees encrypted bytes and timestamps; it cannot see the content.
- Gold and Platinum plans only. Silver and free accounts can still take a video call from someone on a paid plan, but cannot initiate one. Audio calls remain Gold-plus too. Free accounts can match and chat.
- Both sides must be verified and mutually matched. You cannot cold-call a profile. The video button doesn't even render on the screen for unmatched pairs.
The safety story — what we ship, what we won't claim
This is the part we want users to read carefully, because marketing tends to overstate it. Here's the truth:
1. The watermark
Every active video call carries a visible bottom-center watermark with your match's display name and the elapsed call time. It updates every second. If anyone screenshots the video, the captured frame identifies both the session and the moment in time. You cannot remove the watermark from inside the app. This is the strongest practical deterrent against screenshot misuse — it doesn't prevent the capture, but it makes the capture trivially attributable.
2. The honest disclosure
On your first video call, Lami shows a consent prompt that explicitly says screenshots are not technically blockable on the web because the operating system owns the screen, no browser can stop it. We say it before you accept the call. This is uncommon — most platforms with video calling avoid the topic — and we think it matters. You should know what you're agreeing to before your camera turns on.
3. Tab-visibility pause
When you switch tabs or minimize the browser, we pause the remote video AND turn off your camera transmission. The peer on the other end sees a frozen frame of you, not a live feed of your hidden tab. When you come back, the camera resumes only if it was on when you left. This means a backgrounded call cannot be screenshot or screen-recorded by anyone — not you, not the other side.
4. One-tap audio downgrade
The call controls include a "Switch to audio only" button. One tap drops the video tracks and continues as a voice call. You don't have to hang up to turn the camera off. The peer is notified, and Safari, Chrome and Firefox all renegotiate the SDP so the remote frame goes truly dark — not a stale frozen frame, an actually-empty video stream.
5. Report from inside the call
If something feels wrong mid-call, hang up and use the report action in the chat thread. Reports feed our moderation signals; blocked users can never call you again, even if you unmatch and rematch later. The Safety Center has the full report flow.
Nepal-built vs. India-with-Nepal-page
Jeevansathi, Shaadi.com, and BharatMatrimony all market video calling to Nepali users. They were also all designed and engineered in India, with a "Nepali matrimony" page slotted on top of an Indian product. There's nothing wrong with that, and frankly those companies have decades of head start on a Nepali product like ours. But it matters for three practical reasons:
- Jurisdiction. Lami's servers, incorporation, and legal exposure are in jurisdictions that take direct action on misuse reports filed by Nepali users. An Indian platform has to triage Nepal incidents through Indian customer service.
- Data localisation. Most of our data sits in Singapore (close to Nepali users for low call latency) rather than Mumbai or Chennai. That has user-visible consequences: call quality is better, and account-data questions are answered by people who understand Nepali context.
- Product design. Things like family-managed profiles, Devanagari subtitles on every page, Manglik / Nadi filters at the top of search, and the Kundli scoring UI are first-class on Lami because we built for that user first. On an Indian product they are usually three taps deep, optional, or absent.
We are not saying don't use the Indian apps — they have real scale. We are saying that if you want a matrimonial product that was built to serve your context, not adapted to serve it after the fact, Lami is the cleaner fit. And on video calling specifically, we are the only Nepal-built platform offering it.
What we deliberately did not ship
Three things were tempting and we decided not to do them:
- Group video calls. Three-way video changes the safety calculus completely — who is the third party, who consents, who appears in the watermark. Until we have a consent model that handles all of this, group calling stays off.
- Recording. Not on our side, not on yours. The Lami app does not let you save or export a call. Recordings would destroy the trust the watermark deterrent relies on.
- Persistent call history that includes faces. The call list in your chat thread shows "video call — 12:34" with no thumbnail. Nothing identifies what the call looked like after it ends.
How to try it
If you're on the Gold or Platinum plan with a verified profile, open any matched chat thread — the camera icon now appears in the header next to the phone icon. First use shows the safety consent prompt; subsequent calls go straight to ringing. If you're on Silver or free, you can still take a call from a Gold+ match (just no initiating), and you can upgrade on the Premium page any time. For the short marketing read instead of this long-form one, the landing at /video-calling-matrimony has the basics.
We're launching this knowing that video calling on the web has real limits, and that the families on both ends of a bihey call deserve to know what those limits are before they agree to a call. The watermark, the consent prompt, the tab-visibility pause, and the audio-only escape hatch are how we keep this honest. If you spot something we've missed, write to us — info@lamimatrimony.com gets read every day.