Resources
What shipped.
A public record of every release. New features, fixes, and improvements, as they land. Written by the people who built them, in plain language, with nothing buried.
Why we keep a public changelog.
Because a platform that asks for your community should be able to say, precisely, what it changed and when.
Vronify.chat is hand-written, from zero to over 125.000 lines of code, by a small team in the Netherlands. There is no template underneath and no white-label product we rebrand. That means every entry on this page describes work we actually did, on software we actually understand, running on hardware we own and tune ourselves. When we say something shipped, we mean we wrote it, tested it, and put it in front of you.
We publish the log for three reasons. First, trust: you should never have to guess whether the platform under your community is moving. Second, accountability: fixes appear here too, which means admitting what was broken. Third, planning: server owners run real communities on top of this platform, and a change to roles, moderation, or messaging is something you deserve to read about, not discover.
How versions are numbered
We are pre-1.0, so versions look like v0.9.4. The middle number marks a new wave of work; the last number counts the releases inside that wave. A bump in the middle number usually means a headline capability arrived. A bump in the last number means a focused release: a feature or two, some sharpening, some fixes. Neither kind is allowed to break your server without an entry here explaining what changed and why.
How updates reach you
Vronify.chat is browser-first, with nothing to install, and that shapes how releases work. There is no updater to run and no app-store review to wait out. When we ship, the next page load you make is the new version. Everyone is on the latest release, always, which also means a fix reaches every user at the same moment it reaches the first one. The mobile apps for iOS and Android and the desktop apps for Windows, macOS, and Linux are coming soon; when they arrive, their releases will be recorded on this same page.
If something looks wrong right after a release, check the status page first, then tell us. We would rather hear about a problem twice than not at all.
The release log.
Newest first. Every release since the platform opened, with what it added and what it fixed.
Faster loads, tighter sessions
- Long channels now load in pages as you scroll up, so even the busiest server opens instantly
- Sign out of all sessions everywhere with one password-confirmed action
- Fixed: pinned messages could briefly lose their in-channel badge after an edit
Roles, sharper
- Gradient role colors, rendered live everywhere names appear
- A tabbed role editor: display, permissions, and members in one place
- Bookmarks now show a Go to link only while the source message still exists
- Pinned messages get an in-channel badge
Built for scale
- A single server now comfortably supports 50k+ members
- Message delivery tuned to under 40ms median in Europe
- Channel history and switching are noticeably faster on large servers
- Groundwork for the upcoming bot engine, which has its own page
Easier ways in
- Sign-up, shortened: from first click to first message in under a minute
- Redesigned account emails that actually reach inboxes
- A two-step first-run wizard: pick your look, then find your people
- Pretty invite links: vronify.chat/invite/CODE
Threads, polls, and bookmarks
- Threads keep side conversations attached to the message that started them
- Polls with live results, posted right inside the channel
- Bookmarks: save any message to a private list and jump back to it later
Discovery, opened up
- The Explore page: browse and join public communities without an invite
- Server tags, so communities can say what they are about
- A featured communities showcase for servers worth discovering
Tools for moderators
- The audit log: administrative actions, recorded and reviewable
- Slow mode, set per channel, to calm conversations that move too fast
- Automated filters that catch problems before a human has to
- Pinned messages, so the important things stay findable
Voice channels
- Voice channels: drop in, talk, drop out, with no call to schedule
- See who is in a voice channel before you join it
- Runs in the browser like everything else, nothing to install
DMs, private
- Direct messages are private: only the people in the conversation see them, and we don't read them
- Community channels stay readable to moderators, so public spaces stay safe
- No ads, no trackers, no data brokers: unchanged, and now easier to verify
Your account, actually yours
- Export your data any time, no request forms, no waiting
- Delete your account any time, which anonymizes it: your name and profile are removed, and your messages remain attributed to a deleted user
- A ban only stops participation: your account and your message history stay yours
Make it yours
- Custom profiles, so you look like yourself everywhere
- Per-server nicknames: be someone slightly different in every community
- Themes, appearance, and accessibility settings
- Custom emoji, uploaded and managed per server
The foundation
- Real-time messaging with edits, replies, reactions, and read receipts
- Roles and permissions, so responsibility scales with your community
- Channel categories to keep growing servers organized
- One-link invites: share a single link, and that is the whole onboarding
How a release happens.
The same four steps every time, on hardware we own, with no third party in the path.
Build and test
We write the change, then run it the way you will: in the browser, against real servers, on the same class of hardware production uses. Because the whole codebase is ours, there is no vendor to wait on and no black box to work around.
Ship it
The release goes to production infrastructure we own and tune ourselves. Browser-first means the rollout is immediate: the next page load anyone makes is the new version, with no updater, no download, and no app-store queue.
Watch it
We watch our own numbers after every release: message delivery times, error rates, uptime. Those are the same figures behind the performance page, and if a release moves them the wrong way, we act before most people notice.
Write it down
The entry lands on this page in plain language: what is new, what changed, what was fixed. No marketing gloss, no vague version notes that say only bug fixes and improvements. If we changed it, we say so.
How to read an entry.
Every bullet in the log falls into one of a few kinds. Knowing which is which tells you whether a release matters to you.
Features
Something the platform could not do before, like threads, polls, or voice channels. Features are the headline of most entries and always come with the settings to control them, so server owners decide what their community actually uses.
Improvements
Existing things made better: faster loading, clearer editors, smarter defaults. Improvements rarely need anything from you, but we list them anyway, because a platform that only announces new features is hiding most of its work.
Fixes
Things that were broken and are not anymore. We name them plainly. Admitting a bug existed is the price of a changelog you can trust, and we think it is a fair one.
Security notes
Changes that harden the platform, like the sign-out-everywhere action in v0.9.4. We describe what improved without publishing a how-to for attackers. Researchers should start at our vulnerability disclosure page.
Coming soon
Sometimes we point at what is next, like the upcoming bot engine and the mobile and desktop apps. Anything labeled upcoming is not live yet. When it ships, it gets a real entry with a version number.
Removals
When we take something away, we say so, and we say why. Quietly deleting features is how platforms lose trust. If a removal could affect how you run your server, the entry will tell you what to use instead.
What all those releases add up to.
The log above is the history. These are the standing numbers it has to keep meeting, release after release.
What makes the log, and what stays out.
A useful changelog is edited. Here is the rule we apply to every release before we write it up.
Always gets an entry
- Every new feature, from headline capabilities to small quality-of-life additions
- Any change to behavior your members would notice, even subtle ones
- Fixes for bugs that affected real users, named plainly
- Anything that changes what server owners or moderators can do
- Removals, with the reason and the alternative
Kept out, on purpose
- Internal refactors that change code but not behavior: real work, but not news you can use
- Routine infrastructure maintenance, which belongs on the status page instead
- Experiments we tried internally and never shipped
- Wording tweaks to this website: the log tracks the product, not the brochure
- Vague filler like bug fixes and improvements with nothing behind it
Questions about releases.
How often does Vronify.chat ship?
Steadily, but on no fixed schedule. We ship when a release is ready, not when a calendar says so, which is why the gaps between entries above vary. If you want to know the moment something lands, this page is the source of truth: every release appears here, and the newest entry is always at the top.
Do I need to update anything when a release ships?
No. Vronify.chat runs in the browser with nothing to install, so the next time you load the app you are on the latest version automatically. If the app is already open when a release lands, a refresh picks it up. There is nothing to download, approve, or configure. When the mobile and desktop apps arrive, their releases will be listed here too.
What do the version numbers actually mean?
We are pre-1.0. The middle number marks a wave of related work, and the last number counts the releases inside that wave. So v0.9.0 through v0.9.4 are one arc: threads and polls opened it, and sharper roles and faster loading followed, so far. The numbers are a reading aid, not a contract; what matters is the entry text, which always says exactly what changed.
A release broke something for me. Where do I report it?
First, check the status page to rule out a wider issue. If the problem looks specific to a release, go to support and mention the version number from this page; that context helps us reproduce it fast. If what you found is a security issue, do not post it publicly: use the vulnerability disclosure process instead, and we will take it from there.
Where is the bot engine in this log?
It is not in the log yet, because it has not shipped. The bot engine, with welcome cards, reaction roles, leveling, custom commands, and tickets, is on the way and is described on its own page as upcoming. When it launches, it will get its own entry here with a version number, so watching this page is the reliable way to catch it.
Can a release ever take away my data or my account?
No. Account ownership is a standing commitment, not a feature flag: you can export your data any time, you can delete your account whenever you want, which anonymizes it, and even a ban only stops participation while your account and history remain yours. Releases add capabilities on top of those guarantees; they never subtract from them. If a release ever changed how your data is handled, the entry here would say so explicitly.
Will new features start costing money?
Core features are free forever. Later there may be optional extras for power users, and if those ever appear, they will be announced here like everything else, clearly marked. What you will never find in a release is a surprise paywall in front of something you already relied on.
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.