Work on music projects online — organise, track, and finish what you start
Work on music projects online with a system that keeps files, versions, tasks, and collaborators organised. TYFRA Vault is the project home for independent artists and producers.
Most music projects do not fail because of a lack of talent or a lack of effort. They stall because of a lack of organisation. The stems are in one folder, the reference tracks are in another, the mix feedback is in a message thread, the latest version might be on the laptop or might be on the backup drive, and the to-do list lives in a note that was last updated three months ago.
Working on music projects online — meaning through a cloud-based system rather than a local file structure — solves a specific version of this problem: files are always accessible, collaborators always have the latest version, and the project record persists regardless of which device you are on or which hard drive you are carrying.
This page covers how to structure a music project properly, what a project management system for music actually needs to do, and how TYFRA Vault handles it. Read next: manage music projects, organise music files, and remote music collaboration.
What a music project actually consists of
Before organising a project, it helps to be precise about what it contains.
Source files. The raw recordings, samples, and stems that the production is built from. These are typically the largest files and the ones where version tracking matters most.
Production files. The DAW session file (.als, .logicx, .ptx etc.), any plugin presets saved with the project, and any sample packs or one-shots used in the session. Note: DAW session files themselves often exceed 150MB when bundled — Vault is the right home for audio exports and stems, not necessarily for full DAW bundles. Be accurate about this when planning what you store.
Exports and mixes. Bounces of the track at different stages — rough mix, revision 2, mix for mastering, master. These are what most people mean when they talk about "the track" in a collaboration context.
Reference material. Reference tracks used during production, brief documents, mood boards, lyric sheets. Contextual material that makes the project intelligible to anyone joining it later.
Communication and decisions. Feedback notes, accepted split proposals, task records. The paper trail of how the project developed.
The problem with local file management for music projects
The conventional approach — a folder on your hard drive organised by artist, project, and date — works until it does not. The points at which it breaks:
When a collaborator needs access. You copy files to a Dropbox folder, which is now a second copy of the project. Changes made in one location do not update the other. Version drift begins immediately.
When you switch devices. The project is on your studio machine. You want to show it to someone on your laptop. It is not there, or an older version is there from the last time you manually copied it.
When you come back to a project after a gap. The file structure made sense when you created it. Six months later, the naming convention is opaque and you cannot remember which mix was the approved one.
When something goes wrong. Hard drives fail, laptops get stolen, studios flood. Local projects without cloud backup are fragile in a way that feels hypothetical until it happens.
How TYFRA Vault organises a music project
Projects and Products — two different containers
Vault uses two distinct organisational structures for a reason.
A Project is for active production work. It is where stems, mixes, revisions, reference tracks, and feedback live while a track is being made. Projects are private workspaces for you and your collaborators.
A Product is for finished releases. It is where a completed track lives once it is ready to be shared with the world — grouped into a Single, EP, or Album with artwork, metadata, and distributor-ready export. Products are the public-facing side of your catalog.
The distinction matters because the needs of a work-in-progress are different from the needs of a finished release. A project needs revision tracking and collaborative feedback. A product needs complete metadata, clean version labelling, and a release-ready structure.
Folder organisation within a project
Color-coded folders inside a project let you group files by type or stage: stems in one folder, mix exports in another, reference tracks in a third. Smart tagging makes individual files findable across a large catalog. For projects with many tracks or many versions, the folder structure provides the organisational layer that a flat list of files lacks.
Version tracking — revisions and variants
Track Revisions track the production iterations of a single mix: v1, v2, v3. Each revision is a snapshot of the track at that point, retained regardless of how many subsequent revisions are added. You can always return to an earlier revision without having to reconstruct it.
Track Versions handle distinct variants: the instrumental, the radio edit, the extended mix, the acapella. These are not iterations of the same mix — they are different versions for different purposes. Labelled and stored separately, immediately distinguishable from production revisions.
Task management
Vault's task management lets you assign specific tasks within a project — "add drum fill at 2:30", "fix the vocal pitch in the bridge", "deliver master by Friday" — with priorities, due dates, and status tracking. Tasks can be templated for common workflows: a standard mastering delivery checklist, a pre-release quality check, an A&R submission package.
For solo artists, tasks are a personal to-do list for each project. For collaborations, tasks can be assigned to specific collaborators, making the work distribution visible to everyone in the project.
Metadata — entered once, travels everywhere
Every track in a Vault project stores its metadata with the file. ISRC, ISWC, BPM, key, genre, moods, instruments, credits, lyrics, recording date, P-line, C-line — all of it entered once and available at every subsequent stage. When the project moves from production to promotion, the BPM and key are already there for Promo campaigns. When it moves to distribution, the ISRC is already registered. Metadata is not re-entered at each stage — it travels.
Finishing projects — the part that is harder than starting them
The hardest part of managing music projects is not organising the files. It is finishing the work. Vault does not make a bad track better, and it does not remove the creative challenges of production. What it does is reduce the administrative friction that causes projects to stall:
The mix that never gets finished because you lost track of which version the client approved. The collaboration that goes cold because neither party can remember where they left off. The track that gets delayed because the metadata is incomplete and the distributor rejected the upload.
Clear version history, task tracking, and a project record that persists regardless of who was last active makes it easier to pick projects back up and move them forward. The work is still the work. The project management is one less thing to fight against.
From project to release
When a track is finished in a Vault Project, it moves to a Product — the release container. Artwork is added, the track listing is ordered, metadata is verified, and the product is ready for distributor export. The same metadata that lived in the project carries over. No re-entry.
From the Product, the track flows into Promo for DJ campaigns (metadata pre-fills), Finance for income tracking once streaming royalties arrive, and Contracts for any collaboration agreements that need formal documentation. The project that started as a stems folder and a feedback thread ends as a properly documented, commercially ready release.
How TYFRA fits
- Projects: active production workspaces (stems, mixes, revisions, references, feedback)
- Products: finished release containers (Singles, EPs, Albums) with distributor-ready export
- Track Revisions (v1/v2/v3): production iteration tracking, each revision retained
- Track Versions: instrumental, radio edit, extended — labelled separately from revisions
- Color-coded folders + smart tagging: file organisation within projects
- Task management: assign tasks with priorities, due dates, status, templates
- Complete metadata: ISRC/ISWC/BPM/key/moods/instruments — entered once, travels everywhere
- Audio analysis: BPM/key auto-detect
- Unlimited collaborators with role permissions
- Flows into Promo, Contracts, Finance at release stage
- £9.99/mo · free tier available
Related on TYFRA
Common questions
Your data flows with you across TYFRA
These aren't separate apps. Your tracks, metadata, splits, contacts, and conversations stay connected—so every tool in the TYFRA suite can work from the same source of truth.