We have done some testing and feel quite confident that the encoding and delivery stack will work. This is a summary of what is currently blocking us from taking a decision.
Price - this is a showstopper. We can not invest more in research and development without any indication.
I saw a comment that you consider consumptioned based prices based on played minutes in a comment. Since bandwidth currently are on a flat fee, at least on your self-service plans, this would encourage us to select another service for encoding and storage but still deliver content through Cloudflare. A more predictable approach, at least for us, is a consumption model based on storage and encoding minutes. (I’m happy to provide you with our video stats and costs to have a private price discussion).
End-user upload - All our video files are uploaded by editors or our users through their web browser. We need a simple and safe way to enable upload in a browser with a one-time code client side generated server side.
Just like you have a browser api for the player I would like to see an upload api in the browser. I would like to call an api endpoint server side using my secret key to get a video-id/upload-id and a code snippet back that I can send to the browser to enable a user to upload one video.
I do not want to build a hack with workers to hide my secret key and build my own authentication in workers as suggested as a workaround. I would prefer not to reference tus.js directly and keep track of compatibility and updates - you should embed it in your browser api. I also prefer if you configure the tus client for me.
Origin file - Users own their data. We need to be able to provide download of the origin upload. It does not make sense that we should handle this separately.
Access Tokens - We need to be able to generate time limited playback links/tags. You should not be able to craft your own playback link and share with others since most of our content is private.
White label - we prefer if upload and playback is from our domain and not cloudflaresteams.com. Our customers trust us and our domain and we do not want them to see who is handling their data if possible.