6 weeks from handshake
to first subscriber.
The headend is already running — hosted and operated by OnyxPlay. For production, add an optional BGP-anycast CDN node inside your network, peered directly with your ASN. You keep routing control. We run the software stack.
The actual production path. Click any phase.
Paperwork & access
MoU signed, Partner Portal accounts cut, IP block and ASN exchanged. Most partners finish this before any CDN node hardware arrives.
- Provision Partner Portal accounts
- Sign carriage MoU under the master OnyxPlay licence
- Share the CDN node reference hardware spec + procurement BoM
- Send network-requirements PDF + IP / ASN intake form
- Return signed MoU and partner KYC
- Allocate /29 IPv4 (+ /112 IPv6) per CDN node
- Confirm your ASN, intended peering posture
- Nominate 2 ops contacts and 1 escalation owner
- MoU.pdf
- reference-hw.csv
- ip-asn-allocation.csv
CDN node install
Optional, recommended for production. You procure servers to our reference spec; we install the OnyxPlay CDN software remotely over OOB and validate every node.
- Provide the signed OnyxPlay CDN install image + BMC playbook
- Drive remote install over OOB once each node is racked
- Run post-install burn-in: PSU, NIC, NVMe, RAM, DRM key store
- Sign off each node as ready for BGP peering
- Procure N servers to our reference spec
- Rack each node · dual A+B power · OOB on separate VLAN
- Patch each node into your BGP-speaking switch
- Confirm cooling envelope (35 °C cold-aisle max)
- install.log
- burn-in.log
- node-inventory.csv
BGP-anycast & peering
Each CDN node speaks BGP into your network and announces the anycast prefix. You keep full routing control.
- Bring up our side of the peering (ASN 149231 · PNI or IXP)
- Configure anycast prefix and per-node BGP communities
- Pre-warm cache hierarchy across all nodes
- Validate Widevine + PlayReady license routing per node
- Accept anycast announces from each node on your BGP router
- Set local-pref, MED, communities — steer subscribers as you like
- Bring up upstream peering (PNI preferred · IXP supported)
- Reverse-DNS the node IP blocks under your zone
- bgp.cfg
- anycast-prefixes.txt
- license-test.log
Billing & apps
Webhooks wired to your BSS/CRM. OnyxPlay apps available across the 4 smart-TV platforms.
- Wire webhooks to your billing & CRM
- List OnyxPlay apps on Android TV, Tizen, webOS, Fire TV
- Configure EPG, catalog, and the entitlement state machine
- Open Partner Portal access for ops, support, and finance teams
- Provision API credentials in your billing system
- Map subscriber plans to OnyxPlay entitlement tiers
- Confirm EPG source and lineup defaults
- Approve test entitlements ahead of UAT
- webhooks.yaml
- epg-feed.xml
- entitlement-map.csv
UAT & go-live
Pilot subscribers on real TVs. Soft launch to 100 households, then open the gates.
- Stand up 25 test entitlements across all 4 TV platforms
- Run synthetic load to 1.5× projected peak concurrency
- Pull and re-announce anycast routes to prove node failover
- Sit on the bridge for the first 48 hours after public launch
- Recruit 10–20 pilot households (staff first, then friendlies)
- Run 7-day soft launch with capped enrolment
- Coordinate marketing for public launch day
- Open Tier-1 support queues with scripts we provide
- uat-signoff.pdf
- failover-drill.log
- runbook.md
OnyxPlay CDN node — reference spec.
Nothing to buy for the headend — it is hosted by OnyxPlay. A CDN node inside your network is recommended for production and not needed for a 1–2 user demo. You procure the hardware to this reference spec; OnyxPlay installs and operates the software remotely, BGP-anycast across N nodes.
Reference compute
- CPU
- AMD EPYC 9354P · 32 core · 3.25 GHz (or equivalent)
- Memory
- 256 GB DDR5 ECC · 4800 MT/s
- Boot
- 2× 480 GB NVMe · mirrored
Reference cache
- Tier 1
- 4× 3.84 TB NVMe Gen4 · ~95% hit
- Tier 2
- 6× 7.68 TB SATA SSD · long-tail catalogue
- Total
- ~61 TB raw · ~24 TB usable after parity
Network & BGP
- Data NICs
- 2× 25 GbE SFP28 · LACP bond to your BGP switch
- Routing
- BGP4 speaker on every node · anycast member
- OOB / BMC
- 1× 1 GbE · IPMI 2.0 + Redfish for our installer
Power & env
- PSU
- Dual 800 W 80-Plus Platinum · A / B feed
- Draw
- 380 W typical · 540 W peak (per node)
- Cooling
- Front-to-back · 35 °C cold-aisle max
What you bring to a CDN node install. Six items.
CDN node hardware
Optional, recommended for production · N servers to the OnyxPlay reference spec (1U each) · procured by you from any tier-1 OEM
Rack space
1U slot per node · 19″ rails · 760 mm depth · 35 °C cold-aisle max
Dual power
A + B feeds per node · 16 A IEC-C13 per PSU · UPS or generator-backed
BGP router
Each node patches into a router that accepts BGP4 anycast announces from the node
IP & ASN
/29 IPv4 + /112 IPv6 per node · your ASN for peering · reverse-DNS under your zone
Ops contacts
2× 24×7 NOC contacts · 1× escalation owner · IPMI / serial access for our installer
Two paths. PNI preferred. IXP supported.
Private Network Interconnect
Cross-connect in our cage at any of our six PoPs. Dedicated capacity, no shared-fabric contention, deterministic latency.
- Setup
- 5–8 business days
- Capacity
- 10 / 25 / 100 GbE
- Latency
- ~0.4 ms RTT in-metro
- Best for
- Steady, high-volume traffic · partners > 8 Gbps peak
IXP peering
Bilateral or via route servers — both supported. We peer on DE-CIX, Extreme-IX, and NIXI; three IXPs × two cities = 6 on-ramps.
- Setup
- 10–14 business days
- Capacity
- Shared fabric
- Latency
- 0.6–1.2 ms RTT
- Best for
- Smaller partners · already on the IX
NOC-watched. 24×7. Mumbai.
Eight live metrics, auto-paged on threshold breach. The Partner Portal shows your CDN node dashboard in real time.
Response + resolution times. In writing.
| Tier | Description | Response | Resolve | Credits |
|---|---|---|---|---|
| P1 · Service down | Anycast pool unreachable, > 5% concurrent subs affected. | 15 min | 2 h | 5% of monthly fee per 30 min over SLA |
| P2 · Degraded | Single node down with anycast holding, channel failing. | 1 h | 8 h | Case-by-case |
| P3 · Functional | EPG mismatch, billing webhook lag, single-subscriber issue. | 4 h | 2 business days | None |
| P4 · Cosmetic | Portal label, app screenshot refresh, dashboard tweak. | 1 biz day | Next release | None |
Questions before the deployment call.
Answered by our deployment team on every intake call.
Request the deployment checklistReady to plan your launch?
Let's schedule the kickoff.
We'll send you the CDN node reference spec, the IP/ASN intake form, and the deployment playbook the same day.