A partial Netflix technology profile using its own disclosures. Separate the 2016 cloud migration, Open Connect video delivery and October 2026 source review.
Dated evidence review ·
A partial documentary history of cloud computing and video delivery, not an exhaustive current stack. Next editorial review due . This edition records what was checked on the review date; it does not promise current contract status. If the review is overdue, use the linked primary sources to recheck before acting.
Two layers, two kinds of evidence
Company disclosures reviewed October 15, 2026. Publication, review and event dates are separate.
Technology / scope
What Netflix disclosed
Publication / observation
Confirmed event timing
Amazon Web ServicesApplication compute and storage
Netflix reported completion of its streaming-service cloud migration. The account covers computing and storage for application functions; it separates video delivery through Open Connect.Netflix primary source ↗
Published: 2016-02-12Observed: 2026-10-15
Early January 2016 (company-reported completion; exact day not stated)
Netflix Open ConnectVideo delivery network
Netflix documents ISP partnerships, embedded Open Connect Appliances and peering. This is Netflix’s delivery system, not a separately purchased AWS service.Netflix primary source ↗
Published: Not statedObserved: 2026-10-15
Not established
A reported migration, not a new 2026 adoption
Netflix’s February 2016 account dates completion to early January 2016. Our October 2026 review only confirms that this historical account remains available. Open Connect’s undated documentation describes the delivery architecture without providing a new migration date.
This profile follows two infrastructure layers that Netflix describes directly: application compute and storage, and video delivery. It does not inventory every language, database, analytics system, SaaS contract or business unit. An omitted technology is unknown, not absent.
Read the dates before inferring a change
The migration is a company-reported historical event. The publication date is when Netflix described it; the observation date is when VendorCensus reviewed the source. An undated architecture page cannot establish when a component was first introduced or whether a recent replacement occurred.
How this history will be maintained
Review Netflix’s migration account and Open Connect documentation quarterly, and investigate important new company disclosures. Preserve the historic event even if the live page moves. Add a change only when the same service scope and its timing are supported. If a review is missed, this remains a dated documentary profile rather than a current stack inventory.
A public job board supports an ATS observation. A subprocessor disclosure identifies a provider that may process data for particular services. A vendor customer story describes a published relationship. These sources have different scopes and are labeled separately.
Counts cover the records on these pages, not the whole market. No observation in our covered sources does not mean a company does not use a vendor. Source recency and unresolved conflicts affect confidence; observations do not establish spend, renewal timing, or customer churn.