It’s one of the most horrible things I’ve ever been forced to touch. I avoid it even more than I avoid Windows and other Microsoft products, which is saying a lot.
Did you read a different article?
--
Edit: turns out they did read a different article, which is here[0] and does strongly imply it's not intended to be a public offering.
[0] https://netflixtechblog.com/empowering-the-visual-effects-co...
From the Netflix blogpost, it seems you are correct. The author of The Register article seems to have misinterpreted and is definitely discussing a prospective public offering.
--
The 2nd sentence you quoted implies that people working on Netflix titles will use it, but does not imply exclusivity.
The 1st sentence I don't really understand what you're reading from it... sounds like a public offering to me.
In addition to those sentences, The Register article is chock full of direct references to it being a public offering, not an internal vendor offering.
Perhaps dang or another mod can change to the source article which is less misleading: https://netflixtechblog.com/empowering-the-visual-effects-co...
Edit: in the original blog post linked to from The Register article it seems this is not public. This would lead me to assume that it is in fact running on AWS like most of the rest of Netflix's infrastructure, and that Netflix are providing a useful distribution/configuration/potentially free layer on top. Not to down-play the importance of this, I can see this being really useful for creators.