Skip to content

Ask AI

Ask anything about Destesi — setup, products, APIs.

Powered by Claude. Answers may be wrong — always verify against the docs.

Drive

Drive is the one library where everything the suite produces lives. Every artifact any product creates — a rendered video, a voice clip, a generated image, a file you uploaded — is registered in Drive at drive.destesi.io. One place to find everything, across every product, in your workspace.

Without a shared library, each product would keep its own silo of outputs and you would be hunting through five different products to find one file. Destesi avoids that by making Drive the canonical sink: when a product finishes producing something user-facing, it registers that artifact in Drive.

In practice that means:

  • The video Studio renders, the narration Text-to-Speech synthesizes, and the images Image generation creates all show up in the same Drive.
  • You browse, organize, and download them from one interface, regardless of which product made them.
  • Files are workspace-scoped — your Drive shows your workspace’s artifacts, shared with your teammates in that workspace.
  • Files and folders. Organize artifacts into folders, rename them, and move them around.
  • Artifacts from across the suite. Each registered file records which product produced it, so you can tell at a glance where a video, audio clip, or image came from.
  • Your own uploads. You can upload files directly into Drive as well, not just consume what products generate.

You can browse and download files through the Drive web app, and manage folders and files there. Drive also serves the content links that products embed — when another product shows you a video or image it produced, that media is being served from Drive.

Drive accepts the same account-wide bearer token every product does — see CLI & API auth for how bearer-token authentication works across the suite. This lets you list, fetch, and manage your workspace’s artifacts from scripts and services.