What MicBridge does
A short list, done properly.
MicBridge is not trying to be a meeting platform. It does one job — getting a broadcast-quality conversation between a presenter and a remote guest, and getting the audio back out — and it refuses to grow features that get in the way of that.
Running an interview
Everything a presenter needs, and nothing else
One-field interview creation
A title is the only thing MicBridge requires. Guest name, note, date and recording preference are there if you want them, and out of the way if you do not.
Microphone check before anyone joins
Both sides pick an input and watch a live level meter before the conversation starts, so nobody discovers a muted microphone on air.
Speaking indicators, not video tiles
The call screen shows who is connected, who is talking and who is muted. There are no empty video rectangles, because there is no video.
Built for a phone first
Controls sit within thumb reach, the layout is designed for a handset rather than shrunk from a desktop, and MicBridge installs as an app where the browser supports it.
- PRPriya RamanHost · speaking
- DODaniel OkaforGuest
The live interview screen.
Guests
No account, no friction, no surprises
Links that are hard to guess and easy to revoke
Each guest link carries 256 bits of randomness, expires on a schedule, and can be revoked instantly. Database identifiers are never used as access credentials.
Consent is a step, not a footnote
Guests are told the conversation will be recorded before they join, and recording cannot start until everyone present has agreed. Each agreement is stored with a timestamp and the version of the notice shown.
Scoped to one conversation
A guest link grants access to exactly one interview. It reaches no other session, no station data, and no recording — not even the one they took part in.
Recording
Audio your editor can work with
Recorded on the server
Recording does not depend on anyone's browser staying open. A guest closing a laptop does not take the audio with them.
Separate tracks per voice
Where the configured provider supports it, each participant is kept as their own file alongside the interview audio — which is what makes a remote interview genuinely editable.
Retention you decide, deletion that is real
Recordings are kept for 30 days by default. Your administrator sets the period, every recording shows its deletion date, and expiry removes the stored audio rather than hiding a row.
Running a station
Administration that answers real questions
Invitation-only accounts
There is no public sign-up. An administrator invites a presenter, and can change their role or disable them — which ends their sessions immediately.
An audit log worth reading
Sign-ins, invitations, role changes, interviews, consent, recording starts and every deletion are recorded, with search, filters and date ranges. Passwords, tokens and conversation content never are.
Authorization in the database
Access rules are enforced by row-level security in PostgreSQL, not by what the interface chooses to show. A request without a valid context reads nothing at all.
Station accounts are created by invitation.
If your station is not set up yet, tell us what you need and we will get back to you.