How Netflix Delivers Streaming at Scale: The Open Connect Appliance Explained

When you press play on Netflix, where does the video actually come from? Not from some far-away cloud data center - but from a custom server placed inside your Internet Service Provider's (ISP) own network.

That server is called an Open Connect Appliance (OCA), and it is the heart of Netflix's own content delivery network (CDN), known as Open Connect.

In this blog, we explain how Open Connect works, what an OCA is made of, and the engineering philosophy behind it - in simple, everyday English.

Why Did Netflix Build Its Own CDN?

Streaming video is heavy. A single movie can be several gigabytes, and millions of people watch at the same time. If every request had to travel across the public internet to a central server, streams would buffer constantly and bandwidth costs would explode.

Netflix solved this by building Open Connect: a network of appliances that store content close to the viewers. Today, Netflix partners with over a thousand ISPs worldwide and runs appliances in 60+ global data centers and internet exchange points. Content is served from the nearest, healthiest source - which is why Netflix streams start fast almost everywhere.

What Is an Open Connect Appliance (OCA)?

An OCA is a specially designed server that stores the Netflix catalog and delivers it over HTTP to nearby viewers. Its key traits:

• Free of charge - appliances are given to qualifying ISP partners; they are never sold.
• High availability - redundant system drives, power supplies, and network ports. If a drive fails, it is disabled automatically and the system keeps running.
• Single purpose - each appliance does one job: serve content. Nothing else.
• Continuously monitored - Netflix's Network Operations Center (NOC) watches the health and performance of every appliance around the clock.

The Hardware: Big Storage, Low Cost

OCAs are built from commodity PC parts and assembled in custom cases by suppliers. There are two main types:

Storage Appliances are 2U servers used at large internet exchange points and bigger ISP locations. They deliver around 200 Gbps of throughput with up to 120 TB of NAND storage.

Global Appliances are low-cost 2U servers for smaller ISPs and emerging markets. They provide roughly 80 Gbps of throughput and up to 60 TB of storage, and are engineered for 4-6 years of reliable, no-touch operation.

The lesson: you do not need expensive enterprise hardware. With smart design, automation, and redundancy, ordinary components can run at massive scale.

The Software: Open Source and Minimal

The OCA runs a deliberately small, open-source software stack:

• FreeBSD - the operating system, chosen for its stability and performance.
• NGINX - the web server that delivers audio and video over HTTP.
• BIRD - a BGP routing daemon that shares network topology and helps route clients to the best content source.

Keeping the software minimal means fewer moving parts, fewer failures, and better performance. Netflix also contributes all its improvements back to the open-source community.

Health Checks That Decide Where Traffic Goes

Every OCA continuously reports its health, load, and capacity to Netflix's central control system. This feedback is used automatically in routing decisions. If an appliance slows down or becomes unhealthy, Netflix simply redirects viewers to another healthy appliance - often before users notice anything.

This is reliability as a live feedback loop, not just a monitoring dashboard.

How Resilient Architectures Work

Netflix designs deployments for graceful failure. If an ISP has two embedded OCAs and one goes down, traffic shifts to the second. If both fail, traffic is served from Netflix appliances at the internet exchange point. In every scenario, viewers keep watching - Netflix engineers just steer traffic around the problem.

Replace, Don't Repair

The most interesting DevOps idea in the whole system: an OCA has almost no user-serviceable parts, except power supplies and optics. When enough drives fail, Netflix does not send an engineer to fix the box. It ships a brand-new appliance to the ISP instead.

This is "cattle, not pets" applied to hardware. Servers are disposable. When something breaks, replace it with a clean, known-good machine rather than spending hours repairing it. Netflix also continuously monitors each appliance and automatically manages the content fill and update process.

What Developers and DevOps Teams Can Learn

• Design for replacement, not repair - machines are cheaper than engineers' time.
• Use health signals in routing - let automation react to failures.
• Keep software minimal - fewer components means fewer failures.
• Build in redundancy - single drive or power failures should never matter.
• Make systems self-reporting - a device that reports its own health is easier to operate at scale.

Frequently Asked Questions

Is Netflix's Open Connect Appliance for sale? No. OCAs are provided free of charge to qualifying ISPs that meet Netflix's requirements.

Can I buy or build one myself? No. OCAs are not for sale and are built by Netflix's suppliers for its own CDN.

Does every Netflix video come from an OCA? Most traffic is delivered from OCAs and settlement-free peering connections that are close to the viewer.

What if an appliance breaks? Netflix monitors all appliances and replaces failed hardware, usually by shipping a new appliance to the ISP.

How does Netflix decide which source to stream from? Clients request the best source, and Netflix's control system uses health and load feedback from each appliance to route traffic efficiently.

Summary

The Open Connect Appliance shows how Netflix delivers smooth streaming at global scale using cheap hardware, open-source software, and smart automation. The key takeaways for engineers are simple: build systems that are disposable, self-reporting, and replaceable - then scale them with confidence.

Note: Open Connect is just one piece of Netflix's massive engineering system. Behind it lies a much larger ecosystem of teams, tools, and architectures. We will explore each of these in upcoming posts, one by one.