TELNYX EDGE COMPUTE

CloudFS

Mount a POSIX filesystem on any host or container. Backed by Telnyx Cloud Storage, built for AI agents that need persistent, concurrent file access across runs.

CiscoOpenAITalkdeskAmerican Red CrossZillowMicrosoftCosmoIBMState of IowaCiscoOpenAITalkdeskAmerican Red CrossZillowMicrosoftCosmoIBMState of Iowa
WHY TELNYX

Build on one platform, not a stack of vendors.

Compute, storage, database, inference, and telecom on one account, one API, one bill. CloudFS is the shared filesystem layer, connected through bindings, not API calls.

FEATURES

A real filesystem, not a storage API

Mount it with one command. Use it like a local directory. Every file persists in Telnyx Cloud Storage and is available to every client that mounts it.

  • POSIX semantics

    read, write, mkdir, rename, git init. Anything that works on a local directory works on CloudFS. No SDK to learn, no API to call. Your tools and your code already know how to use a filesystem.

  • Concurrent access by design

    Mount the same filesystem from many clients at once. A fleet of agents can read shared configs, write to a shared workspace, and collaborate on the same files. JuiceFS handles the coordination.

  • Mount anywhere

    Runs on any host or container that supports FUSE. Edge functions, bare metal, VMs, CI runners. If it can mount a filesystem, it can mount CloudFS.

  • Durable storage backend

    Every byte lives in Telnyx Cloud Storage. The same S3-compatible object storage that powers your edge functions. Survives container eviction, pod replacement, and infrastructure failure.

  • Open-source client

    CloudFS uses JuiceFS Community Edition (Apache-2.0). You run the client yourself. No proprietary agent, no vendor lock-in at the mount point. Telnyx provides the managed storage backend and the metadata database.

  • WebDAV for hosts without FUSE

    For environments where you cannot mount a filesystem, CloudFS exposes a WebDAV endpoint. Read and write files over HTTP from any language, any platform, any runtime.

HOW IT WORKS

Mount in three steps

Create a filesystem over the API, mount it with the JuiceFS client, and use it like any local directory. The whole path runs end-to-end on Telnyx infrastructure.

Create a filesystem

curl -X POST https://api.telnyx.com/v2/storage/cloudfs \
  -H "Authorization: Bearer $TELNYX_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{"name": "agent-fs", "region": "us-east-1"}'

Mount it

export AWS_ACCESS_KEY_ID="$TELNYX_API_KEY"
export AWS_SECRET_ACCESS_KEY="***"

juicefs mount --no-usage-report --background --log /tmp/juicefs.log \
  "$META_URL" /mnt/agentfs

Use it

cd /mnt/agentfs
echo "hello cloudfs" > hello.txt
cat hello.txt

git init -q
git add . && git commit -m "first commit"
BINDINGS

What CloudFS connects to on the platform.

CloudFS is backed by Cloud Storage and mounts on any Edge Compute container. No credentials to manage, no external storage provider in the path.

Sign up and start building.

Get an API key, create a filesystem, and mount it from your first container in minutes.

FAQ

CloudFS is a POSIX filesystem you mount on any host or container, backed by Telnyx Cloud Storage. It behaves like a local directory but stores every byte durably in object storage. The same filesystem can be mounted by many clients at once, making it a shared persistent layer for AI agents.