Bring Your Own Storage
Last updated
Last updated
Bring Your Own Storage is available for Team or Enterprise plans with a yearly plan.
If you have a Team or Enterprise plan, you can Bring Your Own Storage. We'll replace the Drive storage back-end included with PostLab with either...
Bring Your Own LucidLink (BYOL), or...
Bring Your Own S3 (BYOS)
BYOS is useful for companies that already have a 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 functionality, BYOL will be the way to go.
The setup fee for bringing your own storage is $500, and is available for Team and Enterprise plans with a yearly commitment.
BYOS 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 doesn't have any 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 is forfeited.
If you're using subteams, your BYOS/L isn't connected to those too; instead, PostLab's storage back end is used. If you need BYOL for subteams, you can provide the LucidLink details for each subteam. Each requires a setup fee. Subteams with BYOS is not possibility.
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.
We'll send you a username and password through a secure mechanism.
Use those credentials to create a user on your LucidLink Filespace 1.0.
Once you create that user, email us the name of your Filespace. (e.g. name.domain)
We'll email you once we've connected your Drive to your Filespace.
Files and media on your Drive will be lost when we switch to your Filespace. Be sure to have a backup before sending us your Filespace's name.
Send us the following information:
Location
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 a 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.
First, 🙂
BYOS replaces your existing Drive. By default, we do not migrate any data it might contain. If you have data on your Drive, be sure to download it first. If it's too much to download,