The customer should own the video library
NULX keeps permanent sources and streaming outputs in the customer's own Cloudflare R2 storage while operating upload, transcoding, and protected playback.
The problem we solve
Managed convenience should not require surrendering data control
We make security, ownership, and cost visible in the buying decision, not only in engineering documentation.
Keep sources and HLS outputs in customer storage, adding DASH only when requested.
Separate bucket access, managed processing, signed playback, and external AI transfers.
Separate direct Cloudflare costs from NULX billing and add no NULX markup to playback.
Core values
How product and pricing decisions are made
Review storage location, processing boundaries, and cost terms before rollout.
Customer control
Keep storage location, access, domains, and the Cloudflare contract under customer control.
Transparency
Explain what moves during processing and who bills each cost before purchase.
Reliability
Verify manifests, renditions, segments, and the real playback path instead of trusting a completed process alone.
Verified scope
Separate features verified in live workflows from features that need additional setup.
Team
A team focused on stable video operations
NULX is built by an engineering-led team that cares about predictable delivery, launch readiness, and operator experience.
Focused architecture
Keep the product understandable and composable instead of layering unnecessary complexity.
Hands-on support
Help customers move from evaluation to rollout with practical guidance.
Continuous improvement
Use customer feedback and operational evidence to keep improving the platform.
Architecture review
Where is your video stored, and who pays for delivery today?
Share your Cloudflare setup and monthly upload and playback volume. We will map the operating model first.
Review my architecture