Target audience: Workspace administrators
Overview
TeamCache is an add-on that places a shared, location-based cache server between your team and your LucidLink filespace. When many users in the same office access the same files, TeamCache serves those files from a local cache instead of fetching them from the cloud each time, reducing latency, cutting bandwidth consumption, and delivering a more consistent experience for high-volume workflows.
Frequently Asked Questions
Who is TeamCache designed for? TeamCache delivers the most value to enterprise teams with read-heavy, high-volume workloads, for example a media production team where many people are working from the same library of large video, image, or project files from a shared location.
Is TeamCache included in my subscription? No. TeamCache is a paid add-on that has to be enabled for your workspace before you can deploy it.
Does TeamCache replace my filespace? No. TeamCache sits in front of your existing filespace. Your filespace remains the source of truth for all your data; TeamCache accelerates access to the files your team reads most often.
Does TeamCache support write operations? No. TeamCache accelerates read access only. Files you write or modify go directly to your filespace as they normally would.
Тhe data blocks of the files we cache are immutable by design, so if a file is changed partially the parts that are not modified are served from the cache (cached blocks) and the others (which aren’t in the cache yet) are served directly.
Is TeamCache hosted by LucidLink? No. You provision and operate the TeamCache server yourself on your own infrastructure. LucidLink does not manage the server on your behalf.
How TeamCache works
TeamCache runs on a Linux server in your office or data center. Once installed, it acts as a local delivery point for your filespace:
When a team member requests a file that TeamCache has already cached, it is served from the local server with no round-trip to the cloud. When a file has not yet been cached, TeamCache fetches it from the filespace, serves it to the requesting client, and stores it locally so subsequent requests are served from cache.
TeamCache can be configured per client using the local TeamCache.Location setting. This gives teams flexibility to connect clients to the most appropriate local cache for their location or workflow. In most cases, a TeamCache server is deployed close to the users it supports, helping reduce cloud round-trips and improve file access performance.
Requirements
Before deploying TeamCache, make sure you have:
A dedicated Linux server on your own infrastructure. Ubuntu, Debian, RHEL, Rocky Linux and AlmaLinux are supported. See Install and Set Up TeamCache for the tested versions and architectures.
An existing LucidLink filespace on S3 storage, in a workspace whose subscription includes TeamCache.
IT staff with Linux server administration experience.
License and all required steps for it will be provided by your LucidLink team.