Cloudflare R2 and Music Distribution
How modern content delivery infrastructure solves the problem of distributing a 5TB music catalog — and what this means for independent music education publishers.
The Sound Cells series generates approximately 5 terabytes of audio, scores, and metadata across its 78 volumes. A generation ago, distributing this quantity of material to students worldwide would have required either a physical distribution network (CDs, DVDs, printed books shipped by mail) or a large institutional infrastructure (university server farms, licensing agreements with streaming platforms). Today, it requires a Cloudflare R2 bucket and a URL naming convention.
This is not just a logistical convenience. It represents a fundamental shift in the economics and reach of independent music education — one that is worth understanding in detail, both for what it enables now and for what it points toward in the near future.
What Cloudflare R2 Is
Cloudflare R2 is an object storage service — a system for storing files (objects) and making them accessible via URLs. It is similar in concept to Amazon S3, but with one significant difference: Cloudflare charges no egress fees. Traditional cloud storage charges for every byte of data transferred to a user — a cost that scales directly with the number of students and the size of the files they access. R2 eliminates this cost, making the economics of audio distribution at scale dramatically simpler.
The technical architecture is straightforward:
The URL Naming Convention
Every audio file in the Sound Cells series follows a consistent URL structure that encodes the mathematical organization of the series directly into the file path:
This naming convention means that any URL in the series is self-describing. A reader who encounters the URL for Composure knows immediately that it is volume 64, that the trichord pair is 026-026, and that it is a computer realization — without needing to consult any external catalog. The mathematical organization of the series is embedded in the distribution infrastructure.
Public vs. Private — The Current Approach
The current Sound Cells audio distribution uses public access — anyone with the URL can stream or download the audio. This is the simplest approach and the right one for the current phase of the project, where the priority is accessibility: students and educators worldwide should be able to access the material without friction.
The future architecture (planned for when the native iOS/iPadOS app is built) will use private access with entitlement gating: a Cloudflare Worker (a serverless function running at the edge) will verify that a user has purchased access before issuing a time-limited presigned URL for each audio file. This architecture is more complex but enables proper monetization while maintaining the delivery benefits of the CDN.
No login required
Zero friction for students
No monetization enforcement
Appropriate for ebook-first distribution
60-second presigned URLs
RevenueCat entitlement check
Per-track or per-volume access control
Required for native app distribution
What This Means for Independent Publishers
Cloudflare R2 and the broader ecosystem of modern cloud infrastructure have fundamentally changed the economics of independent music education publishing. A generation ago, distributing 5TB of audio to a global student base required either venture-backed infrastructure investment or a deal with a major publisher who had the distribution network. Today it requires approximately $15/month in storage costs and no egress fees.
This shift has broader implications than cost reduction. It means that the quality of the distribution infrastructure available to an independent publisher is now comparable to that of a major label or a university press. A student in Seoul streaming a Sound Cells audio file gets the same latency and reliability as a student streaming from Spotify or Apple Music — because the underlying technology (Cloudflare’s CDN) is the same.
The remaining differentiation between independent and institutional publishing is not infrastructure but discoverability — being found by students who don’t know to look. This is where the STEAM education website articles you are reading now serve a purpose: not just explaining the music but making it findable by students, educators, and curious people who encounter it through a search engine or a link from a physics or mathematics classroom.
The Naming Convention as a Learning Tool
There is an educational dimension to the URL naming convention that goes beyond organization. A student who learns to read a Sound Cells URL can reconstruct the mathematical structure of any piece in the catalog from its file path alone. Vol-64-026-026 means: volume 64, trichord pair 026-026, Forte number 6-22, whole-tone dominant hexatonic. This is not accidental — it is a design choice that makes the infrastructure itself a teaching tool.
The same principle applies to the folder organization within each volume: transpositions are numbered by semitone, permutations are labeled by inversion type. A student browsing the R2 bucket structure — if they were given access — would see the mathematical organization of the trichord pair system laid out as a directory tree. The infrastructure encodes the pedagogy.
Streaming from R2 — Two Volumes
These audio files are streamed directly from Cloudflare R2 — the same infrastructure described above. The URL of each player encodes the volume number and trichord pair.
Infrastructure and music — the same design principles
Edge computing
Cloudflare’s 300+ global edge nodes cache content close to users — the same principle that makes the 027 trichord “close” to the ear: familiar, low-latency, immediately available without traversing a long harmonic distance.
Self-describing URLs
The URL encodes the mathematical structure of the content — volume, trichord pair, instrumentation. Infrastructure that describes its own content is more navigable, more learnable, and more maintainable. Good naming is a design discipline.
Public/private tradeoff
Public access maximizes reach; private access enables monetization. The current phase (public) optimizes for discoverability. The future phase (private + entitlement) optimizes for sustainability. The tradeoff is the same one every music publisher faces.
Infrastructure economics
R2’s zero-egress pricing removes the cost that previously made large-scale audio distribution prohibitive for independent publishers. The economics of music education have changed as fundamentally as the economics of recorded music changed with streaming.
Distribution as Part of the Work
Composers and music educators have historically focused on the creative work — the compositions, the method books, the teaching — and left distribution to intermediaries: publishers, record labels, universities. Modern cloud infrastructure makes it possible for a single composer-educator to control the full stack: composition, production, publication, and distribution.
This is both an opportunity and a responsibility. The opportunity is direct relationship with students, without the compromises that intermediaries impose. The responsibility is that the infrastructure work — the bucket policies, the URL conventions, the encoding standards — must be done well for the music to reach its audience reliably. The next article looks at the instrument itself: the acoustic engineering of the guitar, and how the physical properties of the instrument shaped the development of the trichord pair approach.
Cloudflare R2 documentation: developers.cloudflare.com/r2. The Sound Cells audio files are hosted at the R2 bucket described in this article, with URLs following the naming convention documented here. Full catalog and course materials at muse-eek.com.