Skip to content
Crystal Desk

Integrations / Storage Providers

Storage Providers

Storage provider configuration determines exactly one thing: where the physical bytes of media library files live. It has no effect on any other part of the application.

The default: AWS S3

Every tenant starts on AWS S3-backed storage by default, hosted in the ap-south-1 (Mumbai) region. This requires no configuration and is what powers the media library on the standard plan.

Custom setups: bring your own storage

As a custom, sales-assisted setup, a tenant can instead connect their own storage — Box, Dropbox, or OneDrive — so that media files are stored in infrastructure the tenant controls rather than Crystal Desk's shared S3 storage. This is typically chosen for compliance or data-residency reasons specific to a customer's own policies.

What it affects (and what it doesn't)

Storage provider choice affects only where media library files are physically written and read from. It has no effect on:

  • Application data (tickets, workflow templates, user records) — this always lives in Crystal Desk's own database, regardless of media storage provider.
  • How files behave inside the app — playback, viewing, search, and tagging all work identically no matter which provider is configured underneath.

Switching storage providers on an existing tenant with files already in S3 is a migration Crystal Desk's team handles directly — it isn't a self-serve toggle, since it involves moving existing files, not just changing where new ones go.

Next: Deck Analyzer covers the AI-powered brief analysis tool.