Bring Your Own Storage
If you have a Team or Enterprise plan, you can Bring Your Own Storage (BYOS). With BYOS, we'll replace the Drive storage back-end included with Postlab with one of these:
- Bring Your Own LucidLink (BYOL)
- Bring Your Own S3 (BYOS3)
BYOS3 is useful for companies with an S3 account where adding a few more TBs isn't much of a deal. If your company already uses LucidLink, but the editorial team needs to use Postlab and Drive's Drop Off and Pick Up functionality, BYOL will be the way to go.
BYOS3 is a yearly commitment with a 1 TB minimum. If you're on a monthly plan, it will automatically be converted to a yearly plan once we connect your S3 to Postlab. When your storage use exceeds 1 TB, another TB is added to your plan, with billing prorated accordingly.
BYOL also requires a yearly commitment, but without storage charges - you pay LucidLink for that, not us. Once we connect your LucidLink Filespace to Postlab, the 1 TB or 2 TB included with your Team or Enterprise plan will no longer be accessible.
It's also possible to deploy a Postlab Local server and hook it up with your Team's Drive. Doing so allows:
- On-prem Team Members to work with Postlab Local, and local media.
- Remote Team Members to access projects and libraries on a Postlab Local server through a VPN.
- Everyone to work directly from your media stored in the cloud, on Drive.
- 1.We'll send you a username and password through a secure mechanism.
- 2.Use those credentials to create a user on your LucidLink Filespace 1.0.
- 3.Once you create that user, email us the name of your Filespace. (e.g.
- 4.We'll email you once we've connected your Drive to your Filespace.
Send us the following information:
- Access key
- Secret key
Then, we'll create a dedicated bucket for Drive available from within Postlab.
Some things to keep in mind with S3:
- Drive uses Wasabi as its back-end, but don't be fooled into thinking it will have the same performance. Off-the-shelf Wasabi is not the same as our Wasabi, as we have special tier deal with them for better performance. Depending on which codecs you play back from the cloud, it might make sense to use our Drive back-end for some of your projects. Your Wasabi has a 90-day retention policy; Drive has none.
- You cannot use your Drive bucket for something else. Also, you won't be able to access the files directly through an S3-compatible API. Because Drive is block-based, each object represents a tiny part of each file, and you'll need Drive to recombine those blocks into files - not unlike how a SAN Initiator works.