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.

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.

Functions, KV, SQLDB, Object Storage, and Inference on a single account. CloudFS is the shared filesystem layer. No external storage vendor in the path.

Mount CloudFS, query SQLDB, call inference, and send a message through the telecom API in the same request. No SDK per service, no glue code between layers.

Agents that need to call models, store state, and share files across runs. CloudFS gives them a persistent filesystem: clone repos, checkpoint state, no lost work.
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.
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/agentfsUse it
cd /mnt/agentfs
echo "hello cloudfs" > hello.txt
cat hello.txt
git init -q
git add . && git commit -m "first commit"CloudFS is backed by Cloud Storage and mounts on any Edge Compute container. No credentials to manage, no external storage provider in the path.
Get an API key, create a filesystem, and mount it from your first container in minutes.

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

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.
Cloud Storage is S3-compatible object storage. You access it through an API. CloudFS is a filesystem you mount. It gives you POSIX semantics: read, write, mkdir, rename, git init. Underneath, CloudFS stores its data in Cloud Storage, but you interact with it as a directory, not a bucket.
Yes. CloudFS is built for concurrent access. Multiple clients can mount the same filesystem and read or write files concurrently. JuiceFS handles the coordination through its metadata database.
CloudFS uses the open-source JuiceFS Community Edition client (Apache-2.0). You install and run the client yourself. Telnyx provides the managed storage backend and metadata database. No proprietary agent required.
CloudFS is in beta. The API surface and behavior may still change as it moves toward general availability. It is suitable for development and testing workloads today.
Yes. CloudFS can be mounted on any host that supports FUSE, including bare metal servers, VMs, and CI runners. You do not need to run Edge Compute functions to use it. The filesystem is backed by Telnyx Cloud Storage, which is GA.
Nothing. Files persist in Cloud Storage regardless of container lifecycle. When the container restarts and remounts CloudFS, every file is where it was. There is no ephemeral storage and no data loss on eviction.
Yes. For hosts that cannot use FUSE, CloudFS exposes a WebDAV endpoint. You can read and write files over HTTP from any language or platform.