Hedge
Search…
Licensing
Bring Your Own Storage
Instead of using Drive's storage back-end, we also offer teams on a
Team or Enterprise plan to bring their own. We have two flavors available:- Bring Your Own LucidLink
- Bring Your Own S3
The latter is mainly useful for companies that already have an S3 account, and where adding a few more TBs isn't much of a deal. The former is useful if your company already uses LucidLink but the editorial team needs to use Postlab and Drive, to make use of Drop Off and Pick Up functionality.
Pricing
BYOS3 is a yearly commitment with a 1TB minimum, which evidently also requires a yearly Postlab plan. If you're on a monthly plan, it will be automatically moved to a yearly plan when we connect your S3. When the 1TB mark is exceeded, another TB is added to the plan and billed. This is of course prorated, so no surprises there.
BYOL is free of charge. It however does replace your Drive, so you won't have access to the 1TB or 2TB that comes with your Postlab plan.
Postlab Local
It's possible to deploy a Postlab Local server, and hook it up with a Drive. This allows you to work on-prem of a local server, and lets remote employees access your projects through a VPN but the media directly from the cloud.
Setup
First, reach out to us 🙂
Bring Your Own LucidLink
- We'll send you a username and password through a secure mechanism
- Use those credentials to create a user on your LucidLink Filespace.
- When done, email us the name of your Filespace.
- We'll then email you when Drive is replaced with your Filespace.
Bring Your Own S3
Send us the following information:
- Location
- Access key
- Secret key
Then, a dedicated bucket for Drive is created by us, and 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 the Drive bucket for something else, and you also cannot access the files directly through an S3-compatible API. Because Drive's 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.
BYOS replaces your existing Drive. We do not by default 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, ask us for a quote to migrate your data.
​
Last modified 10d ago
Copy link