VYNLT

For studios

Every artist, every session, backed up.

A workspace per client, roles per project, the right projects synced to each studio machine, and backups to your own NAS or cloud with verified manifests.

Before

  • /Volumes/SESSIONS_2024_old/Clients
  • a hard drive labelled in marker
  • shared logins on the studio iMac
  • “who sent this to the label?”

With VYNLT

  • A workspace for every client
  • Selective sync per studio machine
  • Backups to your NAS, verified
  • Roles per person, per project
Studio A, Los Angeles, 21:30

Storage

Kept three ways.

VYNLT Cloud, the studio machine and your NAS or cloud. Each checked against the original.

Hayati · Master 03 · StorageChecked just now
  • VYNLT CLOUD Original stored, SHA-256 checked VERIFIED
  • MIX ROOM IMAC Synced to ~/Music/Hayati VERIFIED
  • STUDIO NAS Backed up with manifest.json VERIFIED
  • WORKSPACES

    One per client or artist

    Organization, workspace, project, song. Access is inherited downwards and can be narrowed per project.

  • MACHINES

    Choose what syncs where

    Two-way on the mix room, download-only on the edit suite. Adding projects to a machine needs a fresh confirmation.

  • NAS

    Local and network storage

    Back up to a folder on your NAS or a mounted drive, restricted to paths your administrator allows.

  • TRANSFERS

    Large sessions, resumable

    Chunked uploads that resume after a dropped connection, verified chunk by chunk.

  • ENGINEERS

    Access that ends

    Invite freelancers to one project as Editor and remove them when the session ends.

  • HISTORY

    Who did what

    Uploads, downloads, shares and approvals in an audit history the studio can read.

Access

Everyone gets exactly enough.

Hayati EP · People PROTECTED

Karim can

  • Listen (allowed)
  • Comment at a timestamp (allowed)
  • Add versions and stems (allowed)
  • Download originals (allowed)
  • Edit lyrics, credits, metadata (allowed)
  • Send private, stream-only links (allowed)
  • Send downloadable links (allowed)
  • Approve a version (allowed)
  • Invite people (allowed)
  • Archive and restore (allowed)
  • Move to Trash; delete forever (confirm it’s you) (not allowed)
  • Storage and backup settings (not allowed)
  • Security policy (require 2FA) (not allowed)
  • Transfer ownership (not allowed)
  • Mark the Official Master (allowed)
  • Lock a master, or release a lock (confirm it’s you) (not allowed)
  • Download Official Masters (allowed)
  • Export social clips (allowed)
  • See campaign plans and calendars (allowed)
  • Plan campaigns, releases and shoots (allowed)
  • Add content ideas and upload edits (allowed)
  • Approve content before it posts (allowed)
  • Schedule and post content, record results (allowed)
  • Work with creators and send creator packs (allowed)
  • Track press and media (allowed)
  • Prepare and deliver to DSPs (allowed)
  • See the campaign budget and spend (allowed)

Checked on the server for every request. Without access, a song simply doesn’t exist for you: the answer is “not found”, not “forbidden”.

Questions

Can I keep files on our own storage?

Yes. Every studio machine can hold a synced copy, and backups can go to a local folder or NAS as well as Google Drive, Dropbox, OneDrive or WebDAV.

Does it replace Google Drive or Dropbox?

For songs, it replaces the folders and links. It can also back up into your Drive or Dropbox, so the copy you already pay for stays useful.

What if two engineers change the same file?

Neither change is lost. The second becomes a clearly named conflicted copy and a conflict is raised for someone to resolve.

One home for every song.

Versions. Feedback. Masters. Your studio. Your cloud. Your team.