Product
Voice rooms that are one click away.
Drop into low latency voice with a click. No separate app, no setup wizard, no second account to manage: just your people talking, in the same browser tab as the rest of your community.
Voice that feels close.
Everything you need to talk, nothing you need to configure first.
Low latency audio
Voice runs on the same infrastructure we tune for chat, so conversations feel like sitting in the same room, not like a conference call.
Straight from the browser
Click a voice channel and you are in. No download, no install, no update prompt when everyone is already waiting.
Simple controls
Mute, deafen, and volume per person. The controls you actually use, without a mixing desk of settings you do not.
Moderated like everything else
Voice channels respect roles and permissions. Decide who can join, who can speak, and who can move people.
Voice messages too
Not every thought needs a live call. Record a voice message in any channel or DM and let people listen when they are ready.
Built for groups
Lounges for hanging out, focused rooms for planning. Create as many voice channels as your community needs.
From channel list to conversation.
Four steps, and the first two only happen once.
Add a voice channel
Voice channels sit in your channel list next to your text channels, grouped into the same categories. Name them for what happens inside: a lounge for hanging out, a planning room for projects, a quiet room for co-working. Creating one takes seconds and needs no configuration beyond a name.
Click to join
Click the channel and you are in it. The first time, your browser asks for microphone access; that prompt comes from the browser itself, and once you allow it you will not be asked again on that device. There is no meeting link to share, no lobby, and no ringing.
Talk
Everyone in the channel hears everyone else, live. You can see who else is in the room before you join, mute yourself when the dog starts barking, deafen when you need to focus, and turn any one person up or down without touching anyone else's volume.
Leave when you want
One click and you are out. The channel stays where it was, empty or not, ready for the next conversation. Nobody has to end the meeting, and there is no host whose departure kicks everyone else out.
Why voice lives in the browser.
The best voice app is the one nobody has to install.
On most platforms, group voice means a second piece of software: a client to download, an account to create, updates to sit through while your friends wait, and an overlay that wants to run at startup. The voice tool and the chat tool end up as two different worlds with two different identities, and half the work of organizing a call is getting everyone into the right one.
Vronify.chat takes a different position. Voice is part of the same browser tab as your chat. The people in a voice channel are the same members you see in the channel list, with the same per-server nicknames, the same roles, and the same profiles. There is nothing to install, so "can you hop in voice?" is a one-click request instead of a fifteen-minute onboarding.
Under the surface, voice rides the same infrastructure as everything else here: hardware we own and tune ourselves, the same network that delivers messages in under 40ms median across Europe. We built the whole platform by hand, from zero to over 125.000 lines of code, and voice is not an acquisition or a plugin. It is a part of the product, which is why it behaves like one. You can read more about how we keep the platform fast on the performance page.
The trade-offs, honestly
Browser-first has real advantages: everyone is always on the current version, nothing needs admin rights to install, and it works the same on a school laptop as on a gaming rig. It also has honest limits. Your browser is in charge of microphone permissions, so if you ever deny the prompt you will need to re-allow it in your browser's site settings before voice can hear you. And because the tab is the client, closing the tab means leaving the call. A dedicated mobile app for iOS and Android and a desktop app for Windows, macOS, and Linux are coming soon for people who want voice to live outside the tab; until then, the browser version is the way in, and it is a good one.
One identity everywhere
Because voice uses your normal account, everything you have set up already applies. The nickname you use in a server is the name people see in its voice channels. The roles that decide what you can do in text decide what you can do in voice. And your account stays yours the same way it does everywhere else on the platform: your data is exportable at any time, and you can delete your account whenever you want, which anonymizes it. Read how that works on the account ownership page.
Who controls what.
Members control their own ears and voice. Moderators control the room.
What every member controls
- Mute your own microphone whenever you want, instantly
- Deafen to step away without leaving the room
- Set a separate volume for each person in the channel
- Leave any channel at any time, no host approval needed
- Send a voice message instead when live is not the right fit
What moderators control
- Which roles can see and join each voice channel
- Who can speak, so events can have speakers and listeners
- Who can move people between channels when things drift
- Creating, renaming, reordering, and removing channels
- Permission changes take effect immediately, mid-conversation
There is no separate permission system to learn for voice. The same role grid that governs your text channels governs your voice channels, so a setup you already understand keeps working. Channel and permission changes are recorded in your server's audit log, the same as any other administrative action, so a team of moderators can always see who changed what. If you are building out a permission structure for the first time, the roles and permissions page and the moderation guide walk through it.
The boring numbers behind good calls.
Voice is only as good as the platform underneath it. Ours is one we built and run ourselves.
Bolt-on voice versus built-in voice.
The common pattern is a chat platform plus a separate voice client. Here is what that costs, side by side.
"The usual setup" describes the common pattern of pairing a chat platform with a separate voice client, not any single product. For a broader feature-by-feature look at how we stack up, see the compare page.
Setting up voice for your community.
Patterns that work, drawn from how real servers use their rooms.
Start with one lounge
New servers often create five voice channels on day one and watch all five sit empty, because members spread out and never find each other. Start with a single lounge. One room concentrates whoever is around into the same conversation, and an occupied channel invites people in far better than an empty grid of them. Add more rooms when the lounge is regularly crowded, not before.
Name rooms for activities, not audiences
"Lounge", "Study Room", "Match Planning", and "Recording, do not disturb" tell a member what is happening inside and whether they are welcome to interrupt. Names like "Voice 1" and "Voice 2" tell them nothing, so they hover in text asking which one to join. Since voice channels live inside the same categories as text channels, you can also keep each room next to the text channel it pairs with: the planning room under the planning category, the event stage under events.
Use speaking permissions for events
Because moderators decide who can speak in a channel, you can run structured events without extra tooling. Give a speaker role permission to talk in your event channel and let everyone else join as listeners: you get a stage for AMAs, community meetings, reading groups, or tournament commentary. When the formal part ends, relax the permission and the stage becomes a room again.
Give staff a room of their own
A voice channel visible only to your moderator roles gives your team a place to confer mid-incident without leaving the server. Pair it with your private staff text channels and the audit log, and your moderation workflow stays in one place. The owner handbook covers this and other structures in more depth.
Know the edges
A few practical things worth knowing before your first big call. Echo almost always comes from someone playing sound through speakers while their microphone is open; headphones fix it, on any platform, and it is worth saying so in your rules channel. If someone's microphone will not work, the usual cause is a denied browser permission, fixed in the browser's site settings rather than anywhere in Vronify.chat. And because the browser tab is the client today, closing the tab leaves the call; keep the tab open while you talk. If something still is not working, support can help, and the status page will tell you if the problem is on our side.
Voice messages: talking without the call.
Live rooms are for being together. Voice messages are for being heard later.
Not every thought needs a live call, and not every community is awake at the same time. A voice message is recorded straight from the message box in any channel or DM, sent like any other message, and played back whenever the listener is ready. No scheduling, no "is now a good time?", no transcribing your own thoughts into three paragraphs when thirty seconds of talking says it better.
They shine in the gaps live voice cannot cover. A community spread across time zones can keep a spoken conversation going for days, each reply landing while the other person sleeps. A tutor can talk through feedback in an education server instead of typing it. A creator can leave a spoken update for the whole community without staging an event. And because a voice message sits in the channel history, it can be replied to, reacted to, and revisited like anything else you post.
They are messages, and they behave like messages
A voice message belongs to the conversation you sent it in, and to you. Delete it and it is gone. If you ever decide to delete your account, which anonymizes it, your voice messages are covered by the same account ownership promise as the rest of your data. Voice messages sent in a DM live inside that conversation, and DMs here are private.
When to use which
A simple rule serves most communities well: if the conversation needs back-and-forth right now, open a voice channel; if it needs to be said out loud but not answered this minute, send a voice message. The two share a purpose, which is why they live side by side here: some things are simply better spoken than typed, and your community should not have to leave the platform to say them.
Questions about voice.
Do I need to install anything to use voice?
No. Voice channels run in the browser, in the same tab as the rest of Vronify.chat. The only setup is a one-time microphone permission prompt from your browser. A mobile app for iOS and Android and a desktop app for Windows, macOS, and Linux are coming soon; the browser version is available now and is the full experience, not a preview.
Does voice cost anything?
Voice channels and voice messages are core features, and core features are free forever. We may offer optional extras for power users later, but there are no surprise paywalls, and we will never move a feature your community relies on behind one.
Who can join a voice channel?
That is up to your server. Voice channels respect the same roles and permissions as your text channels: moderators decide which roles can see a channel, join it, speak in it, and move people between rooms. An open lounge, a staff-only room, and an event stage with designated speakers are all the same feature with different permissions.
What is the difference between mute and deafen?
Mute silences your microphone: you can still hear the room, but the room cannot hear you. Deafen goes further and silences the room for you as well, which is the polite way to step away for a moment without leaving the channel. Both are your own controls, one click each, and take effect instantly.
Why is my browser asking for microphone access?
Because browsers require every site to ask before touching a microphone, which is exactly how it should be. The prompt appears the first time you join a voice channel or record a voice message on a device. If you denied it by accident, re-enable it in your browser's site settings for vronify.chat; there is no switch inside the app that can override your browser's decision, by design.
How is a voice message different from a voice channel?
A voice channel is a live room: everyone in it hears everyone else in real time, and nothing is posted to the channel history. A voice message is a recording you send into a channel or DM like any other message, to be played back whenever the listener is ready. Live for conversations, recorded for time zones.
Will the bot engine do anything with voice?
The bot engine is coming soon, and its launch features live on the text side of your server: welcome cards, custom commands, reaction roles, leveling, tickets, and more. It is built so we can keep adding features over time, so if there is something you want automation to do around voice, tell us and it goes on the roadmap.
How many voice channels can my server have?
As many as your community needs. Servers here scale past 50k members, and the healthiest large communities use plenty of rooms to keep each conversation at a human size: a couple of general lounges, focused rooms per topic, and an event space. Start small and add rooms as they earn their place; the owner handbook has patterns that work.
Your community. Your rules. Your data.
Create a server, invite your people, and see what chat feels like when your account actually belongs to you.
Free to start. Live in under a minute. No install required.