I really appreciate Cubbit’s zero‑knowledge peer‑to‑peer storage architecture and isolated encrypted buckets, which provide rock‑solid data privacy for our high‑risk broadcast assets here at Chicago Broadcast Collective, our 120‑person multi‑site media company. The peace of mind from knowing the platform cannot decrypt or view our media materials is irreplaceable, especially for broadcast compliance work. Before we moved over from Box, we had a very scary incident early this year. A junior production assistant created an over‑permissive public share link on Box for a folder with unaired interview clips and unsigned talent release forms. That link got mistakenly posted in our internal studio chat. We had to pause pre‑production, pull in our legal team, go through pages of access logs and revoke dozens of links just to contain the exposure. We were inches away from talent complaints and regulatory penalties. That stressful near‑miss made privacy our top priority. I like that I can create separate encrypted Cubbit buckets for specific use cases, limiting access to only those who need it. I split assets into buckets for talent paperwork, pre‑air raw footage, and live‑on‑air emergency scripts. Staff from our downtown studio and suburban satellite location only get permissions for their relevant buckets. Additionally, its built‑in file versioning has been a lifesaver. Back in May, one of our studio producers accidentally overwrote our live severe‑weather contingency script right ahead of a forecasted storm cut‑in. Instead of rushing to rebuild that whole critical document under tight deadline pressure, I rolled back to an earlier saved version inside Cubbit and recovered everything in minutes. These features have made Cubbit indispensable for securely managing our sensitive broadcast content across our distributed studio teams. Review collected by and hosted on G2.com.
First of all, there is no native integration with OneScreen. Our studio staff need to manually download files from Cubbit and then re‑upload them into OneScreen digital signage panels for talent briefings and studio shift announcements. This manual workflow can lead to errors. Back in June ahead of our high‑profile local live awards broadcast, a production technician grabbed an old locally‑saved briefing file instead of pulling the latest asset out of Cubbit. He uploaded that outdated document to OneScreen, and wrong talent arrival times displayed on all studio screens for roughly 40 minutes before we went live. I had to rush to refresh every display unit, creating unnecessary last‑minute stress. Second, its file‑search performance slows noticeably when working inside large buckets full of raw broadcast footage and high‑resolution media files. Last month our legal team needed to find one specific talent release form buried among thousands of assets for a compliance audit. The search operation dragged on for multiple minutes and held up our review timeline. Additionally, there is no automated sync with Pinnaca Record & Stream or Seafile. After one live news cut‑in in July, a production coordinator forgot to manually upload our risk‑assessment debrief recording from Pinnaca Record & Stream into Cubbit. The recording sat only on a local server for two weeks, and legal could not locate it during our quarterly audit check. Finally, the initial setup was a bit burdensome, especially user provisioning, as I had to manually input nearly 70 email addresses one‑by‑one, taking up almost a whole workday. Review collected by and hosted on G2.com.
