GemFlare is a free 1:1 calling service that runs in your browser and rides Cloudflare's network in 300+ cities — so the picture stays crisp and the conversation stays in sync, even between continents.
Full-HD calls by default, with an opt-in 4K mode. Under a weak connection the picture softens for a moment instead of freezing — then snaps back.
Your call travels Cloudflare's private backbone from the city nearest you to the city nearest them — not the open internet's scenic route.
No email, no password, no OTP to type. Send one prefilled WhatsApp message and you're in — your number is your account.
Calls are encrypted in transit, nothing is ever recorded, and there are no ads and no trackers — your conversations aren't a product.
Wi-Fi dropped for a moment? The call quietly rebuilds its connection and carries on — no redial, no "can you hear me now".
Works in the browser you already have, on your phone or your laptop. An Android app with true ringing is on the way.
Open the app, tap Open WhatsApp, and send the code it prefilled. That message is your signup — about ten seconds, start to finish.
Enter a friend's number. If they're on GemFlare, their devices ring; your recent calls are one tap to redial.
Full-HD picture, natural voice, and a call that heals itself when the network hiccups. Start with voice and switch to video mid-call whenever you like.
Every other app sends a code and waits for you to type it back. GemFlare works the other way around — and reversing it is what makes the whole thing safer.
Ordinary sign-in
A code arrives. You type it back.
GemFlare
You send the code. WhatsApp vouches for you.
The server generates a code like GEMF-7K2QXA, shows it to you, and
stores it for ten minutes. No SMS, no message from us — there's nothing to
misroute. Seeing the code on your screen is worthless to anyone else: it only
verifies when it comes back from the WhatsApp account it's bound to.
One tap opens WhatsApp with the code already typed in. On the fast path, sending it is the whole signup — no separate step after it.
Meta delivers the sender's verified phone number over a signed webhook. GemFlare trusts WhatsApp's word for who sent the message, never a claim made by the browser.
Instead of a phone number, Meta hands over an opaque id like
BD.1068335812312073. From that alone, GemFlare genuinely cannot tell
who sent the message.
Messages a user starts are free for GemFlare to receive. No template fee, no per-message charge — this path costs nothing.
A six-digit one-time code is sent as a paid template message to the number you originally typed — readable only by whoever actually holds that phone. Slower, and the one path with a real cost.
One more lock: the code is bound to the number you typed before it's even minted, so send it from a different WhatsApp account and it cannot sign anyone in. You can only verify a number you actually hold.
GemFlare is completely free while in beta — every feature, no card, no catch. When paid plans arrive, here's what they'll look like:
No surprise charges, ever: when an allowance runs out, quality steps down or calls continue as voice — nothing is billed behind your back.
Yes. The beta is free while we grow, and it is paid for by us rather than by you. No ads, no data resale.
Three deliberate choices: calls default to Full HD with a modern codec (VP9); media rides Cloudflare's backbone instead of the public internet; and under pressure it adapts to what you picked — on Auto the call protects motion and lets the picture soften, while a quality you choose yourself holds that picture size and lets the framerate give instead.
No account, no password. You prove you own your phone number by sending a one-time code from your WhatsApp; the number itself is your identity, like Duo or WhatsApp.
All media is encrypted in transit end-to-edge with standard WebRTC encryption (DTLS-SRTP) and relayed — never stored — by Cloudflare's realtime network. Calls are not recorded, and GemFlare's servers never see your camera or microphone as anything but encrypted packets in flight.
Not the same way, and it's worth being upfront about it. Calls are encrypted end-to-edge and never stored, but chat messages are not end-to-end encrypted — our servers can read them, which is what lets a message reach every device you're signed into and still be there after a reinstall. Call records (who called whom, when, how long — never the call itself) are kept up to 12 months and then purged automatically; messages have no expiry, though deleting one "for everyone" removes its text from our servers immediately.
Any recent browser: Chrome, Edge, Safari or Firefox, on Android, iPhone, Mac, Windows or Linux. A native Android app — with proper ringing while your phone is in your pocket — is in development.
Not today — in the browser, GemFlare only knows what's happening while the page is open, so nothing can wake a closed tab, for a call or a message. If you have more than one tab open, they all ring together and answering one silences the rest. If no tab is open when someone calls, the server holds the ring for 32 seconds in case you reconnect, then it lands in your call history as missed. Reaching you while your phone is in your pocket is exactly what the Android app in development is for.
GemFlare is 1:1 today, by design — the entire experience is tuned for the quality of a call between two people. Small groups are on the roadmap.
Yes. Settings has a "Who can call me" switch — Everyone, Contacts, or No one — enforced on our servers before your device is ever contacted, so a call you've blocked sends no notification and never wakes your phone (the attempt still shows in your call history, so you can see who tried). One honest limit: the setting governs calls only — someone you haven't saved can still message you unless you block them.
Two separate locks, and both have to be you. The code is bound to the phone number you typed before it's even generated, so a code that reaches us from a different WhatsApp account can't sign anyone in. Even a correct arrival only signs in the browser that started the request, because claiming the session needs a random token that only that browser holds. Codes also expire after 10 minutes regardless.
The call shows "Reconnecting…" and gets 4 seconds to heal on its own. If it doesn't, GemFlare quietly rebuilds the connection from scratch while your camera and microphone stay open, so there's no second permission prompt and the other person doesn't have to do anything. If that rebuild fails too, the next attempt forces media through Cloudflare's relay, which works from behind almost any network; only if that also fails does the call end.
No. When they add video you see their picture, and your camera stays off until you press your own camera button. It works the other way too: you can add video to a voice call already in progress without redialling, and you can answer a video call with audio only. Turn your camera off mid-call and the other side sees your avatar, not a frozen frame.
Yes. Your number is your account, so any signed-in user who enters it learns you're here — your display name, @username and whether you're currently online — and that lookup is throttled to 10 tries a minute. Contact matching sends a hash of each number rather than the number itself, which keeps us from holding your address book, but that's data minimisation, not anonymity. There is no "hide me from search" switch: the settings control who may call you and who you block, not who can find you.
A voice call is light — roughly 60 MB an hour. Video scales with quality: about 0.54 GB/hour at data-saver SD, 3.6 at 1080p30, 7.2 at 1080p60, up to about 10.8 at 4K30 and 21.6 at 4K60. Those are ceilings, not flat charges — the encoder spends only what the picture needs and backs off within seconds when the link struggles. New accounts default to "Maximum" quality, though, which aims for the top of that ladder regardless of your data plan; if data matters to you, set Video quality to Auto or SD in Settings before your next call.