Skip to main content

​
Telnyx Storage: CloudFS (Beta) — Documentation Index

CloudFS (Beta) documentation within the Storage section of the Telnyx developer docs (https://developers.telnyx.com). Root index: https://developers.telnyx.com/llms.txt · Storage index: https://developers.telnyx.com/development/llms/storage-llms-txt.md · Full content for this subsection: https://developers.telnyx.com/development/llms/storage-cloudfs-beta-llms-full-txt.md

​
Get Started

  • CloudFS: CloudFS is a POSIX filesystem you mount on any host or container, backed by Telnyx Cloud Storage — a shared, persistent filesystem for AI agents that you mount once.
  • Quick Start: Create a CloudFS filesystem over the API, mount it with the JuiceFS client inside a Linux container, and read and write files over POSIX.

​
Concepts

  • Filesystems From First Principles: What a filesystem actually is — files, inodes, and directories — and how a local one is implemented: a metadata index (inodes and bitmaps) over a region of data blocks.
  • Network Filesystems: Why the classic network filesystems — Sun’s NFS and the Andrew File System — don’t fit a fleet of ephemeral agents over the WAN, and how GFS, HDFS, and MooseFS reframed storage: an authoritative meta…
  • How CloudFS Works: How CloudFS works: JuiceFS’s synthesis of the metadata/data split — a transactional metadata database plus object storage, served by a rich client with no server in the data path — and the two-lane a…

​
Guides

  • Mounting a Filesystem: Mount a CloudFS filesystem through FUSE with the JuiceFS Community Edition client — on Linux, in Docker, or on macOS — using the metadata URL and your Telnyx API key.
  • Serving Without FUSE: Serve a CloudFS filesystem over WebDAV with juicefs webdav — no FUSE, no kernel extension — and mount the endpoint natively in Finder on macOS.
  • Concurrent Access: Mount the same CloudFS filesystem from many clients at once and read and write it concurrently — with cross-client visibility (close-to-open) and file locks for coordinating writers.

​
API Reference (CloudFS (Beta))

​
cloudfs filesystems

  • List CloudFS filesystems: Lists the CloudFS filesystems for the authenticated user’s organization. Results use cursor-based pagination: fetch the next page by passing `meta.cursors.afte…
  • Create a CloudFS filesystem: Creates a CloudFS filesystem. Provisioning is synchronous — typically a few seconds, up to a few minutes — and the filesystem is returned with status ready,…
  • Get a CloudFS filesystem: Retrieves a CloudFS filesystem by its ID. The returned meta_url omits the credential — the metadata token is only ever returned by create and rotate-meta-tok…
  • Update a CloudFS filesystem: Updates a CloudFS filesystem. Only name can be changed; other fields are immutable and unknown fields are rejected with a 400. Renaming to a name that alre…
  • Delete a CloudFS filesystem: Permanently deletes a CloudFS filesystem, removing its S3 bucket and its metadata database. Deletion is synchronous: the response returns the filesystem’s fina…
  • Rotate the metadata token: Issues a new metadata access token for the filesystem and returns the full filesystem, including the new meta_token and credential-bearing meta_url. The pr…