Band Internal Workspace
A private workspace for a band: song ideas, demo versions, rehearsal logistics, gigs and release planning.
- 4 categories
- 17 channels
- 5 roles
- Small
Choose a server, review what will be created or reused, then confirm. Merge keeps what you have; replace rebuilds the server. Vetox takes a safety backup first either way.
Server structure
Channels
WRITING
- song-ideas
Fragments. A riff, a line, a title. Nothing has to come of it.
- songs-in-progress
One thread per song. Keep its whole history here.
- demos
Put a version number on every upload. Every time.
- lyrics
Words, kept separate from audio.
REHEARSAL
- band-chat
Everything else.
- rehearsal-dates
When and where.
- setlist
What we are working on and the running order.
- gear-and-repairs
What is broken and who is fixing it.
- Practice Room
GIGS
- gig-offers
Anything incoming. Post it here first.
- confirmed-shows
Dates that are actually booked.
- logistics
Load-in, travel, accommodation.
- settlements
What each show paid, in and out. The band's money record.
RELEASES
- release-schedule
What comes out and when.
- artwork-and-assets
Covers, photos, files.
- promo-plan
Who we are telling and how.
- press-and-contacts
Names, outlets, replies.
Roles
- BandAdministrator
- ManagerModerator
- Crew
- Muted
Overview
This is the band's back room, not a fan server. Nobody outside the band and its crew is in it. Writing is where songs start: #song-ideas takes fragments, a riff or a lyric line with no expectation that anything comes of it, while #songs-in-progress has one thread per song so a track being worked on for three months keeps its history in one place. #demos is where recordings go, and the channel topic asks for a version number on every upload, because the commonest argument in a band is which mix everyone was talking about. #lyrics keeps words separate from audio. Rehearsal covers the logistics that eat a band's time: #rehearsal-dates, #setlist for what is being worked on, and #gear-and-repairs. Gigs is the business half: #gig-offers where anything incoming is posted, #confirmed-shows, #logistics for load-in times and travel, and #settlements for what each show actually paid, which is the record that prevents most band arguments about money. Release Planning holds #release-schedule, #artwork-and-assets, #promo-plan and #press-and-contacts. Crew is a separate role for a sound engineer or manager who needs Gigs and Rehearsal but not Writing, because the demo channel is where a band is most exposed and least ready to be heard.
When to use it
Bands run on group chats where the demo, the gig offer and the argument about the setlist are the same scroll, so nobody can find which mix was version three and no one remembers what the last show paid. This layout gives songs threads, requires version numbers on demos, keeps a settlement record per show, and lets a manager or engineer into the logistics without seeing the unfinished writing.
What makes it different
- One thread per song, so three months of work on a track stays in one place.
- Demos require a version number, which ends the argument about which mix.
- A settlements channel records what each show paid, before it becomes a dispute.
- Crew see gigs and rehearsal but not the writing, where a band is least ready to be heard.
Recommended Vetox setup
Reminders
Set Reminders in #rehearsal-dates and #logistics so load-in times reach the whole band without one person chasing.
Logs
Enable Logs so edits and deletions in #settlements are recorded, since that channel is the band's money record.
Suggestions
Run Suggestions on #setlist so the running order is decided by a vote rather than by whoever asks last.
Questions
Why not just use a group chat?
Because a band produces three kinds of thing that a linear chat destroys: versioned files, per-song history and a money record. A demo posted in a chat is unfindable in a fortnight, a song discussed across four months has no thread to read back, and a settlement mentioned in passing is not a record. Everything else a band does is fine in a chat, which is why this server is small.
Should the whole band see #settlements?
Yes. Money opacity is what ends bands, and the channel costs nothing to keep honest. One post per show with what came in, what went out and what each member received turns a recurring source of suspicion into a boring record. If someone handles the accounts, they post; everyone reads.
Common mistakes
- Uploading demos without version numbers, after which nobody knows which mix is being discussed.
- Keeping no record of what each show paid, which is how a band ends up arguing about money a year later.
- Giving crew access to the writing channels, where half-finished work is not meant to be heard yet.
Consider instead
- Artist Fan Community You want a public server for listeners rather than a private workspace for the band.
- Musicians Collab Network Members are looking for people to play with rather than already being a band.
More in Music
View allArtist Fan Community
FeaturedAn official fan server for one artist: release and tour feeds, song threads, listening parties and an inner circle.
Electronic Music Fans
FeaturedSubgenre rooms, a curated release radar, a mixes forum and festival meetups for electronic music fans.
Independent Label Server
FeaturedA label server: read-only release feed, roster-only backstage, staff-read demo submissions and a supporters tier.
Producer Feedback Community
FeaturedA producer community built around a tagged feedback forum, a collab board and a listening-party stage.
0.0k
Servers
0+
Commands
0
Users
0
Languages
