Make a record together. From three time zones.
Drop a mix, the artist comments at 1:42, the A&R approves the master, the label sees it sign off. Every conversation pinned to the version it belongs to.
Three time zones, one record
Timestamped comments
Click 1:42 on the waveform, leave a note. The producer opens it and the playhead starts on the exact bar.
Threaded discussion
Replies stay attached to the comment they answer. No more guessing which note "yes" was meant for.
Approval chains
Define who signs off on each version. Track status from rough mix to delivered master in one view.
Role-based access
Artist, producer, A&R, manager, label: each role sees the files and tabs that match the work they do.
Per-project workspace
Files, comments, approvals, and metadata live inside the project. No scattered email threads or shared drives.
Activity feed
See every upload, comment, and approval as it happens. Catch up on a release without asking anyone.
Version-aware feedback
Comments stay pinned to V1 when V2 arrives. Old conversations stay readable, new ones start clean.
Mobile, same project
Approve a master from a phone in transit. Same project, same comments, same playhead position.
The room
One project. The right people. Nothing else in the way.
Open a project and you see the version that matters, the people on it, and what they last said. The artist sees the latest mix. The A&R sees the master pending approval. The manager sees the release status. Same room, different door.
- Each project holds its own files, comments, approvals, and roster.
- Roles decide what each collaborator sees on open, so nobody juggles permissions by hand.
- Activity sidebar shows the last twenty events without leaving the page.
Feedback
The A&R left a note at 1:42. The producer hears it at 1:42.
Click anywhere on the waveform, type a note, post it. Your collaborator opens the project and the comment is pinned to the exact second. Reply in a thread, mark it resolved when the change is in. No more "around the chorus, second one I think".
- Comments anchor to the exact timestamp on the track.
- Replies stay threaded under the comment they answer.
- Resolve a thread when the fix is committed to keep the open list short.
Work moving between people
Feedback & comments
- Timestamped notes pinned to the exact second on the waveform.
- Threaded replies stay under the original comment.
- Resolve a thread when the fix is in to keep the open list short.
- Comments stay pinned to the version they were left on.
Approvals & roles
- Pick a role per collaborator: artist, producer, A&R, manager, label.
- Role-aware tabs hide what is not relevant to the person opening the page.
- Approval state lives on the version, visible to everyone in the project.
- Lock a master version after sign-off so it cannot be silently overwritten.
Activity & status
- Real-time activity feed for every upload, comment, and approval.
- Project status visible at a glance from rough mix to delivered master.
- Mobile and desktop show identical project state.
- Customer audio is never used to train AI models.
Roles
The label sees the master. The artist sees the rough cut.
Set someone as A&R and they get the comment-and-approve view. Set someone as label and they see the release-ready master and the metadata. The artist keeps full project access. Each person opens the page that fits their job.
- Pick a role per collaborator: artist, producer, A&R, manager or label.
- Role-aware tabs show the right files, hide the noise.
- Change a role without re-inviting; access updates on the next refresh.
Approvals
Sign off the master. Lock the version. Move on.
When the mix is final the A&R hits approve, the label countersigns, and the project flips to release-ready. The activity feed stamps it, the metadata page shows it locked. Anyone who joins the project after sees a clean handover instead of a thirty-message thread.
- Approval state lives on the version, not on a Slack message.
- Locked versions stay locked. Collaborators see the seal before they comment.
- Activity feed records who approved, when, and from which device.
Time zones
Berlin sleeps. London approves. LA wakes up to the diff.
A remote release does not run on a single working day. Vandall keeps every comment, upload, and approval on a timeline you can scroll through cold, so the next person on shift sees what changed and answers without a video call.
- Activity feed gives a chronological catch-up across collaborators.
- Notifications batch by project into one digest instead of twenty pings.
- Mobile and desktop show the same project state, second to second.
The same project, wherever you are
Open it on the desktop in the studio, on a tablet at the desk, on a phone in the green room. Same project, same versions, nothing to sync by hand.
Questions people ask first
Do my collaborators have to sign up to leave feedback?
For full project access (approvals, roles, activity feed), collaborators sign up so their actions are attributed. For one-off review of a single track you can also send a share link and the recipient comments without an account.
Does it work on mobile?
Yes. The project view, timestamped comments, and approvals all run on mobile browsers. An A&R can listen and approve a master from a phone on the move.
How do roles and permissions work?
Each collaborator gets a role: artist, producer, A&R, manager, or label. The role decides which tabs and files they see by default. The project owner can change a role at any time and access updates on the next refresh.
What happens to old comments when a new version is uploaded?
Comments stay pinned to the version they were left on. When V2 arrives, V1 comments stay readable on V1. Conversations on V2 start clean, so feedback never bleeds across mixes.
Do you integrate with the tools we already use?
Email digests and calendar reminders for release deadlines are in. The aim is for collaboration to live inside the project rather than scatter across half a dozen apps.
How do you handle collaborators across time zones?
Every comment, upload, and approval is timestamped on a chronological activity feed. The next person on shift opens the project and reads the diff since they last looked, without a sync call.
Guides on working together
- ArticleThreaded and timestamped comments are hereHow feedback stays pinned to the exact second in the exact version, not floating in a chat.
- EssayThe future of music collaboration in EuropeWhy distributed teams keep beating studios that share a single room.
- Use caseVersion control use caseHow V1, V2, and V3 stay distinct without breaking links or losing comments.
- Use caseFile sharing use caseWhen the share link is the start of the workflow, not the whole thing.
- AudienceFor management teamsRun an artist roster across producers, labels, and lawyers without losing the thread.
- AudienceFor labelsSign off masters, lock versions, and keep the release pipeline visible end to end.
- Use caseRoster management use caseThe business side of the same access model: artists on their projects, the team on the roster.
Trusted by creators globally
Creators on every continent use Vandall to share,
collaborate, and close deals, no matter the timezone.
0+
Projects created
50+
Countries