root@vyve:~$ modules --list
Every module reads
from one live event.
One connected runtime for the DJ booth, the crowd, and every screen in the building. Requests, reactions, photo walls, and tournament queues — all reading from the same live event.
# system boot sequence
djos[ONLINE]
crowdos[ONLINE]
displayos[ONLINE]
tournamentos[BETA]
triviaos[PENDING]
# runtime_architecture
one live event → every system reads from it
01dj_booth—requests, tracks, energy↓ sync
02djos—show control↓ sync
03crowdos—guest interaction↓ sync
04displayos—venue screens↓ sync
05the_room—everyone in sync
# interactive_demos --live
See how the live runtime works.
djos --queue
room_energy84%
Snooze
SZA · from Maddie
Pending
No Hands
Waka Flocka · from Jason
Approved
Pepas
Farruko · from Table 6
Pending
# status --all
What's live now.
vyve-runtime — status
djos
[ONLINE]
active beta
Song requests, live QR codes, now playing, room energy.
crowdos
[ONLINE]
active beta
Reactions, polls, shoutouts, photo wall with Beauty AI & Face FX.
displayos
[ONLINE]
active beta
Venue TVs controlled by events, schedules, and custom scenes.
tournamentos
[BETA]
live testing
Teams, tables, queues, match results, live TV displays.
triviaos
[PENDING]
in development
Phone answers, team scoring, leaderboards, live rounds.
# built_for_venues
The TV is not an afterthought. It's the system.
VYVE makes venue screens useful during every part of the night: requests, promos, tournaments, QR codes, crowd moments, and custom displays.
›venue owns the TV system
›events connect to TVs when needed
›DJOS and CrowdOS push live scenes
›QR codes update by event
›track and crowd data update live
›tournament queues sync to screens