The September update.
VYVE is live.
Hey everyone, Nikita here. It's been a few months, and the short version is this: VYVE barely resembles the platform I showed you last time. Beta is over. Billing is live. Real venues are using it. And enough changed that a normal little product update wasn't going to cut it.
I'm still a working DJ. A lot of VYVE was built the same way this update was written: between sets, after gigs, and at stupid hours of the night because I kept running into the same problem. Live entertainment is supposed to feel connected, but the technology behind it usually isn't. The TV is doing one thing. The DJ is doing another. Requests live somewhere else. Tournaments become a whiteboard. Trivia becomes another subscription. Half the room is held together by somebody's group chat.
So I built the system I wanted behind the booth. Then people actually started using it. Not in a controlled demo. At 1am on Saturdays, with bad Wi-Fi, packed rooms, drunk guests, real requests, real brackets, real photos, and absolutely no patience for software that needs an explanation. That's where VYVE became what it is now.
What started as one idea is now six connected systems, live subscription billing, a real admin backend, and venues running actual nights on it. If you tested an early build, found something broken, sent me screenshots at 1am, or trusted VYVE before it was polished enough to deserve that trust: thank you. You helped build this too.
The live event operating system.
VYVE exists because live events are still being run across a pile of disconnected tools. One thing controls the screen. Another handles requests. Another runs trivia. Another runs the bracket. Then somebody has to stand in the middle and keep all of it from falling apart.
I don't think the operator should be the integration layer. VYVE is the integration layer. The room, the crowd, the DJ, the games, and the screens should already know they're part of the same night.
VYVE is live
Beta is over. VYVE is officially live, subscriptions are open, and the platform is operating as a real commercial product. If you were part of the beta, I'll be reaching out personally about what comes next for your account.
Core, Pro, and Enterprise are live with self-serve billing behind them. Pick the plan that fits the way you operate, move up when you need more, move down when you don't, or cancel without having to email somebody and hope they answer.
TournamentOS is done. And it runs the whole night.
I've run tournaments with a whiteboard, printer paper, and pure adrenaline while yelling table numbers over a room that couldn't hear me anyway. TournamentOS exists because I never wanted to run another night like that.
Teams join by QR code. Tables assign themselves without double-booking. The bracket advances live. The queue stays visible. And DisplayOS turns the venue TV into a proper Live Board all the way through the champion moment. No taped-up bracket. No guessing who's next. No Sharpie required.
PlayOS is here
Outta Pocket is the first full game to ship under PlayOS. Up to eight people play from their phones, the judge rotates every round, and wins stack across the whole game instead of resetting every few minutes. Somebody can completely eat it in round two and still come back to win the night. That's the point.
TriviaOS is fully live
TriviaOS now runs full-room games in both multiple-choice and buzzer formats, with synced host and player experiences, difficulty levels, tiebreakers, and reusable content packs. Build your own questions from scratch or pull from the shared library and run the night from one place.
CrowdOS got a lot bigger
The photo wall is now part of every VYVE plan. Guests can take a photo, submit it from their phone, and see approved photos hit the venue screen without the venue needing a separate product just to make that happen. Photo Studio (Beauty AI, Face FX, filters, makeup, lighting, and editing tools) stays on Pro and above because that's where the heavier compute actually lives.
CrowdOS also carries reactions, shoutouts, live polls, and Crowd Connect. The goal is simple: give the room something worth interacting with without turning the night into everybody staring at another app.
DisplayOS became a platform of its own
DisplayOS is no longer a handful of hardcoded screen layouts. Scenes are actual HTML, CSS, and JavaScript stored as data, which means a venue can get a completely custom screen experience without waiting on a new VYVE deployment. Scenes can be scheduled, sequenced, and rotated like a playlist, while every major VYVE module gets its own big-screen moment through the same system.
Every venue still starts with polished default scenes, so it looks finished on day one. The difference now is that default no longer means permanent.
VYVE Link went past software
The last time I talked about VYVE Link, standalone Pioneer and AlphaTheta hardware was the wall. Those units handle too much of the mixer state inside the hardware itself for normal software metadata to tell the whole story. So VYVE Link now reads the hardware directly through native MIDI telemetry instead.
Rekordbox and VirtualDJ have full Active Deck Intelligence: faders, crossfader position, and actual audibility, not just whatever track name happens to be loaded. Serato has real-time metadata sync today, with deeper integration still in progress. That's where it stands: the parts that are finished are live, and the part that isn't finished isn't being presented as if it were.
The part nobody sees
A lot of the biggest work this quarter happened in places nobody will ever put in a promo video. The admin side was rebuilt into a proper operating console with organization management, support tools, bulk actions, impersonation, and audit history for sensitive actions.
Subscriptions were wired all the way through the product instead of being treated like a paywall pasted on top. Upgrades unlock what they should. Downgrades actually remove access where they should. Password policy is centralized. Auth emails finally look like VYVE instead of whatever default template happened to ship with the service underneath them.
Nobody buys software because the audit log is beautiful. But this is the stuff that decides whether a platform survives a packed Friday night or becomes another thing somebody has to babysit.
This is infrastructure for the room.
Not another novelty app a venue tries twice and forgets about. The goal is for VYVE to become the layer underneath the night: present when it matters, mostly invisible when it doesn't, and reliable enough that nobody has to think about it.
Live modules
What's next
Final note
I'm not going to pretend VYVE is finished. There are still things I want to build, things I want to make faster, and parts of the platform I know can be better. But that's different from saying it's still becoming real. It is real now.
A few months ago, I was still wondering whether this would ever become more than software running on my own laptop. Today, VYVE has six live systems, paying subscriptions, venues using it, and people interacting with it who have no idea how many late nights it took to make that feel effortless. There were plenty of points where stopping would've been easier. I'm glad I didn't.
To everyone who tested VYVE when it was rougher, reported the weird stuff, showed it to a venue owner, ran it through a real night, or simply gave me enough confidence to keep pushing: thank you. The beta did exactly what it was supposed to do. It made the product better. Now we get to see what happens when everybody else gets it.
VYVE is live. Now we build from here.
Nikita
Founder, VYVE