The right R2 setup depends on exposure and operating model
NULX defaults to customer Cloudflare R2. Choose domains, Workers, and upload paths based on whether content is public, members-only, or part of a large migration.
Three decisions first
Choose storage, exposure, and processing before comparing price
- Permanent sources and outputs in customer R2
- Public or expiring signed playback
- NULX managed or customer-PC encoding
Direct internet egress from R2 is $0, while Cloudflare bills storage and Class A/B operations directly.
Adoption paths
Three configurations used in real operations
R2 + customer domain
- Best for
- Public VOD & learning
- Storage
- Customer R2
- Playback
- Customer domain
The simplest configuration and a direct use of R2's $0 internet-egress model.
Use a customer domain in production instead of the rate-limited r2.dev development path.
Private R2 + signed Worker
- Best for
- Membership & internal video
- Storage
- Private R2
- Playback
- Expiring signed URL
Check membership before issuing an expiring path and reject denied requests before reading R2.
A signed URL is a bearer token until expiry, so expiration and sharing policies still matter.
R2 + large desktop upload
- Best for
- 4K & large libraries
- Processing
- Customer PC
- Upload
- Direct to R2
Encode on the customer PC and upload completed HLS plus source files to R2 to reduce server-bandwidth pressure.
See the adoption pathR2 adoption path
Start without granting account-wide access
The product guides these four steps. Migration size and acceptable downtime are reviewed separately for Enterprise work.
Create an R2 bucket in the customer Cloudflare account
Issue an R2 API token scoped to that bucket
Run the NULX connection check and upload one video
Verify HLS, captions, and actual playback; add DASH when needed
Moving from S3 or another platform may incur source-provider egress and metadata-migration work.
Questions
Cloudflare configuration FAQ
Is NULX an official Cloudflare partner?
No. NULX is an independent service using the public Cloudflare R2 and Workers APIs. It does not imply Cloudflare certification, sponsorship, or endorsement.
Why do I pay Cloudflare and NULX separately?
Cloudflare bills customer R2 storage and operations. NULX bills the platform and video processing. Keeping responsibility separate makes each provider's markup and usage visible.
Can I switch stacks later?
Standard HLS outputs and sources in customer R2 reduce the need to re-encode. File copy, domains, membership data, and service metadata still require migration work.
What about storage that isn't listed here?
Cloudflare R2 connects directly. Bunny Edge Storage and other backends are available through an enterprise engagement - contact us for a migration and cost review first.
Check R2 and NULX together with your own workload
R2 pricing, security, and public-bucket descriptions use Cloudflare's official public documentation as checked in 2026-08.