netflix/titus-executor — explained in plain English
Analysis updated 2026-07-19 · repo last pushed 2023-01-10
Study how Netflix ran and managed thousands of containers at scale across AWS.
Learn how container executors integrate with AWS networking, GPU support, and storage.
Reference real-world Go infrastructure code for starting and stopping application containers on servers.
Explore low-level networking filter techniques used for container security and performance.
| netflix/titus-executor | baiyuetribe/glink | sphireinc/foundry | |
|---|---|---|---|
| Stars | 230 | 209 | 183 |
| Language | Go | Go | Go |
| Last pushed | 2023-01-10 | 2021-11-10 | — |
| Maintenance | Dormant | Dormant | — |
| Setup difficulty | hard | moderate | moderate |
| Complexity | 4/5 | 3/5 | 3/5 |
| Audience | ops devops | general | developer |
Figures from each repo's GitHub metadata at analysis time.
Archived and unmaintained, requires AWS infrastructure, Docker, and heavy build dependencies for networking filters to compile and run.
Titus Executor is an archived piece of infrastructure that Netflix built to run and manage containers, packaged applications that run consistently across different environments. Netflix used this internally as part of their Titus platform, which is their system for deploying and scaling the thousands of containerized workloads that power the streaming service. In simple terms, this software is the component that actually starts, stops, and oversees individual application containers on a server. At a high level, the executor works by talking to Docker, the popular tool for creating and running containers. When Netflix needed to launch a container, this software handled the mechanics of getting it running on a specific machine. It also integrated with AWS-specific features like VPC networking, metadata services, GPU support, and EFS storage. The project is written in Go, a programming language commonly used for infrastructure tooling, and it includes specialized networking code that filters traffic at a low level for security and performance. The people who would have used this are infrastructure or platform engineers at Netflix, the teams responsible for making sure thousands of backend services run reliably across the company's computing resources. For example, when an engineer deployed a new microservice to handle user recommendations or billing, this software helped ensure that container launched correctly, had the right network configuration, and could access GPU resources if needed. It is essentially plumbing for large-scale container operations rather than something an individual developer would install on their laptop. It is important to note that this repository is explicitly marked as archived, meaning it is a historical snapshot and is no longer actively maintained. The README is primarily a build and test guide, focused on how to compile the software, run linters, and execute tests locally or inside containers. It also documents some pragmatic technical decisions, like shipping precompiled networking filters to avoid requiring every developer to install heavy build dependencies.
Netflix's internal tool for starting, stopping, and managing application containers on servers at scale. It is archived and no longer maintained, serving as a historical reference for large-scale container infrastructure.
Mainly Go. The stack also includes Go, Docker, AWS VPC.
Dormant — no commits in 2+ years (last push 2023-01-10).
No license information is provided in this archived repository, so it should be treated as all rights reserved by Netflix.
Setup difficulty is rated hard, with roughly 1day+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Don't trust strangers blindly. Verify against the repo.