Full in-house
Own embedded, app and backend teams; an ODM building to your spec; your own DRM deals and device-management backend; you handle certification. Realistic at Tier-1 scale — a multi-year, multi-team program.
Make-or-buy guide
Build your own STB, or buy the stack? the honest make-or-buy
“Building your own box” sounds like engineering — but no operator makes its own chips, and almost none designs the board. In practice, building means assembling a stack of eight layers, from the silicon to the support desk, and owning every one. Some operators genuinely should. Most who say they built a box actually assembled one. This guide lays out what “build” really takes, so you can tell which side you're on.
We're the buy-and-partner side — so we won't pretend building never makes sense. It does, for some. This is the honest version of the trade-off.
8 layers to own
Build: a multi-year program
Buy: a branded sample in 1–2 weeks
Start here
“Build” rarely means what it sounds like
No one makes their own chips, and realistically no operator designs its own board — that's what silicon vendors and manufacturers are for. So “building your own STB” isn't a hardware project; it's an integration project. You're assembling hardware you source, software you write or license, and an operation to manufacture, update and support it — then owning the result end to end.
That's a real and valid path — but a bigger one than it looks. A working box a subscriber can actually use touches eight distinct competencies, and a gap in any one shows up later as a stalled launch or a field failure. Before you decide to build, it helps to see the whole stack you'd be taking on.
What “build” really is
Assembling & owning a stack
What you buy either way
Silicon · ODM hardware · DRM licences
The stack
Eight layers behind a working box
A set-top box looks like one product; it's really eight competencies stacked together. Here's each layer, and what owning it involves.
- 1
Silicon (SoC)
The chip — Amlogic, Allwinner, Realtek. You choose it, you never make it, and it caps your 4K, codecs, DRM tier and secure boot.
- 2
Hardware & industrial design
Board, ports, enclosure, power supply, remote. Designed and built by an ODM — from a reference design or your spec — not something done in-house.
- 3
Firmware & BSP
Android AOSP or Linux, kernel, drivers, secure boot. The vendor gives you a base; hardening it for production takes embedded engineers.
- 4
Launcher & middleware
The branded home screen, EPG, settings and app launcher — the part subscribers see as “yours”.
- 5
Apps
Your IPTV/VOD app, plus OTT. Note: Netflix, Disney+ and the rest aren't “built” — each needs its own certification and a direct operator deal.
- 6
DRM & content protection
Widevine and Verimatrix, licensed and provisioned. Widevine L1 keys must be burned in at the factory, on a chip with a secure enclave — you can't add L1 later.
- 7
Device management & OTA
Provisioning, staged firmware updates with rollback, remote diagnostics, TR-069. A backend in its own right.
- 8
Manufacturing, logistics & support
Production, worldwide shipping, certification, QA, RMA and a support desk — the unglamorous majority of the work.
How operators actually build
Four ways to “build”, from most to least
Reference design + your software
Start from a SoC reference board or an ODM box; your team builds the firmware, launcher, app and DMS integration. Needs an embedded team, but skips custom hardware.
Retail devices + your app
Skip hardware entirely — publish your app on Chromecast/Google TV, Fire TV or retail Android boxes. You “build” only the app, but give up the owned box: no branding, no fleet management, and the vendor controls the home screen and updates.
ODM hardware + a vendor stack
Source hardware from an ODM and license the firmware, launcher, app and DMS from a specialist. You brand and configure; the hard layers are already done. This is the buy-and-partner path.
The honest cost
A build is a program, not a purchase
A true from-scratch build means standing up several disciplines you may not have — embedded firmware, app development, DRM provisioning, a device-management and OTA backend, manufacturing and logistics, and certification and support — then keeping them staffed for the life of the product. The upfront cost is real, but the ongoing one is bigger: every OS bump, security patch and new app is now yours to carry. Plan for a program measured in quarters and a team measured in headcount, not a one-off purchase.
When to build
Building genuinely wins when…
- You have the scale. A subscriber base large enough to spread an engineering org across changes the math entirely.
- You have a unique requirement. A feature or integration no vendor offers, and that's core to how you differentiate.
- You already have the org. An in-house embedded and app team you're committed to funding for the long run.
- Control is strategic. When owning every layer — not just branding it — is a board-level decision, not a cost line.
If two or more of these describe you, building deserves a serious look. If none do, the math usually favours sourcing the hard layers.
Side by side
Build vs buy, dimension by dimension
| Build in-house | Buy & partner | |
|---|---|---|
| Time to market | Quarters to years | Weeks to a first sample |
| Up-front cost | High — teams and tooling | Per-device plus setup |
| Team you need | Embedded, app, backend, QA | Product and operations |
| Firmware & OS upkeep | Yours, forever | Maintained for you |
| DRM (Widevine L1) | You negotiate and provision | Provisioned at the factory |
| Device management & OTA | Build the backend | Included (DMS + OTA) |
| Certification | You own GMS / Netflix | Handled or partnered |
| Manufacturing & logistics | Your ODM and freight | Included, worldwide |
| Control | Total — every layer | Yours to brand and configure |
| Where the risk sits | On you, end to end | Shared with the vendor |
| Where inext fits | The buy-and-partner column — brand and configure, a working sample in 1–2 weeks | |
Neither column is “right” — it depends on your scale, your team, and how much of the stack you want to own.
Where we fit
We collapse the build into “brand and configure”
We sit in the buy-and-partner column, and we don't hide it — but our job is to take the eight layers off your plate, not to talk you out of building if you genuinely should. You get ODM hardware, an Android AOSP or Linux build, your Operator-Tier launcher, the IPTV app, Widevine L1 and Verimatrix provisioned at the factory, Alcatraz DMS with staged OTA, and worldwide manufacturing and delivery. It ships white-label — your brand on the firmware, and, if you want it, your logo on the hardware and the remote. What would be a multi-quarter program becomes: choose the model, brand it, and get a working sample in one to two weeks.
Not sure which side you're on?
Tell us your scale, whether you have an in-house embedded team, and how fast you need to launch. We'll give you a straight read on build vs buy for your situation — not a sales pitch.
FAQ
Common questions
Talk to us
Get a straight read on build vs buy
Tell us your scale, whether you have an in-house embedded team, and your timeline. We'll give you an honest read for your situation — and if buying fits, a branded, working sample in a week or two.