trove

How It Works

Trove helps you save snapshots of a music project, sync them to a private cloud space, and work with collaborators without passing huge project folders back and forth.

01

Save a snapshot

When the project reaches a moment worth keeping, save a snapshot from inside your DAW and add a short note.

02

Sync it to Trove

Send the saved project state to a private cloud project so it is backed up and available away from the original machine.

03

Work with collaborators

Invite trusted people, share the project privately, review snapshots, leave comments, and download versions when needed.

04

Restore or start another direction

Bring back an older snapshot safely, or create a separate alternate idea without losing the current project.

Private collaboration

A shared project room for the people making the track.

Trove collaboration is mainly for private studio work: the artists, writers, producers, engineers, and trusted people who need to hear, review, download, or continue the project.

Private by default

Projects can stay private to you and the people you invite. Public sharing is optional.

Real studio collaborators

Add artists, producers, writers, engineers, vocalists, or other people working on the record.

Comments on snapshots

Keep feedback tied to the exact saved moment it belongs to instead of scattered across texts and file names.

Controlled downloads

Let people with access download synced versions when that is part of the workflow.

Snapshots are saved moments

A snapshot is a point in the life of the project. It should answer a simple question later: what did this feel like, and why did I save it?

  • Save before arrangement rewrites, recording sessions, mix experiments, or big sound changes.
  • Use notes like "before new drop," "vocal comp cleaned," or "rough mix before client notes."
  • History gives you a timeline of the project instead of a pile of duplicated folders.

Cloud sync keeps the project available

Syncing sends saved snapshots to the Trove project page. That gives the project a shared home that is not tied to one laptop.

  • Use sync when you want a backup, another machine, or another person to access the project.
  • Trove keeps unchanged project files from being treated like new work every time.
  • Large project folders can still take time, so sync is built around progress and retrying instead of manual re-uploading.

Collaboration stays centered on the project

The goal is not to make a social feed. The goal is to keep the project, saved versions, comments, audio previews, and downloads in one private place.

  • Invite collaborators when they need to hear, review, download, or contribute to the work.
  • Use private share links when someone needs access without making the project public.
  • Upload audio previews so people can hear where a snapshot is headed before opening the full project.

DAW compatibility still matters

Trove saves and syncs project versions, including the project files and referenced audio it can capture. It does not install Ableton Live, FL Studio, third-party plugins, plugin licenses, or proprietary instrument libraries on a collaborator's machine.

  • Collaborators still need a compatible DAW version and the same third-party plugins when the session needs to stay fully editable.
  • If someone may not have the same plugins or instruments, freeze, consolidate, bounce, or render those tracks before saving the snapshot you want to share.
  • Follow the same Ableton Live or FL Studio handoff habits you already trust for plugin-heavy sessions.

Alternate ideas are separate directions

Sometimes you want to try the club mix, radio edit, darker version, or client revision without damaging the main direction.

  • Start an alternate idea from a saved snapshot.
  • Keep working in a separate project folder for that direction.
  • Use alternate ideas when two directions both deserve to live for a while.

Restore is deliberate

Restoring should feel calm, not scary. The safest path is to restore an older snapshot into a separate folder so the current project is still there.

  • Pick the snapshot from history.
  • Choose where to restore it.
  • Open the restored folder when you want to continue from that saved moment.

Public sharing is optional

Public pages, remixing, likes, and stars can be useful, but they are not the core studio workflow. Use them when you actually want the project to be seen or reused more broadly.

  • Keep sensitive work private.
  • Only allow downloads when the project is meant to be downloadable.
  • Treat public projects as intentional releases of project material, not the default setting.