Team collaboration on DaVinci Resolve projects
Cut, grade, and finish with a distributed Resolve team without a PostgreSQL server.
Resolve collaboration needs a server
DaVinci Resolve Studio has two ways to collaborate, and both have friction. The classic route is a shared PostgreSQL project server on a LAN: every editor, colourist and assistant connects to the same database, with bin and timeline locking. Standing that up for a remote team with a freelance colourist means VPNs, port forwarding and a database nobody on the team wants to administer.
The newer route is Blackmagic Cloud, which hosts the Resolve project in the cloud and bills per project per month. It solves the database, but it only syncs the project, not the media. Every collaborator still has to get the same 4 TB of rushes onto their own machine, by shipping a drive or uploading to yet another service.
Either way, the project database is the easy part. The hard part is that a distributed grade needs everyone looking at the same footage, and neither a PostgreSQL server nor Blackmagic Cloud moves the media for you.
Shared rushes, synced proxies, role-based access
Sanbila handles the part Resolve collaboration leaves out: the media. Every teammate opens the same Virtual Folder of proxies pointing at the same cloud originals, so nobody ships a drive and nobody copies 4 TB to join. Resolve itself runs locally on each machine, so there is no PostgreSQL server to stand up and no LAN to be on.
The handoff is by FCPXML: the editor exports the cut, the colourist imports it on their own machine, and Smart Relink conforms it against the cloud originals, pulling light proxies to work and streaming the full-resolution clips for the grade. Each member picks proxy or stream per clip on their own machine, so the colourist streams the originals while an assistant stays on proxies, with no conflict. In Resolve, each editor links those cloud-generated proxies natively with Link Proxy Media and turns on Prefer Proxies, so the timeline stays light until Smart Relink conforms back to the full-resolution originals for the grade.
Access is role-based, Owner, Editor and Viewer, so a freelance colourist gets exactly the access they need and nothing more. New uploads show up for everyone on the next project reload. Studio covers 3 seats per project and Enterprise 25, enough for editorial, colour, VFX and QC on one project. You can still pair it with a PostgreSQL server or Blackmagic Cloud for the project database; Sanbila is the shared media layer underneath.
Up to 25 seats per project
Enterprise plan supports editorial + colour + VFX + QC on the same project.
FCPXML handoff
Export the XML from one machine, import on another, Smart Relink conforms against cloud originals.
No PostgreSQL required
Resolve runs locally. Sanbila handles the shared storage layer.
Global edge delivery
cloud storage serves all teammates from the closest edge location.
Sanbila by the numbers
Real specs from the live Sanbila product, not marketing claims.
Frequently asked questions
Do I still need a Resolve PostgreSQL database and a LAN?+
No. Resolve runs locally on each machine and Sanbila handles the shared storage layer, so a distributed team cuts and grades without setting up a PostgreSQL project server or a LAN.
How does the colourist get the editor's cut?+
The editor exports an FCPXML, the colourist imports it on their own machine, and Smart Relink conforms it against the cloud originals. The colourist pulls proxies to work and streams the full-resolution clips for the grade.
How many people can be on one Resolve project?+
The Studio plan allows 3 users per project and Enterprise 25, enough for editorial, colour, VFX and QC on the same project, each with an Owner, Editor or Viewer role.
Does everyone need to download the 4 TB of rushes?+
No. Everyone shares the same cloud originals and caches light proxies locally. Each teammate pulls proxies to work, so nobody copies the whole 4 TB of rushes to join the project.
Ship a Resolve post-production in a week
No database setup, no LAN requirement. Invite by email and grade.
Download freeRelated solutions
Premiere Pro proxy workflow without a full SSD
Keep proxies local, originals in the cloud, export at full quality.
SSD full in the middle of a Premiere Pro edit?
Move originals to the cloud, keep lightweight proxies locally, and reclaim space on demand.
Edit 4K offline in Premiere Pro
Proxies run locally on your SSD, no Wi-Fi required during the edit.