JioHotstar goes global in UK, Canada, Singapore — without sports
JioHotstar's global launch ships 160,000 hours of entertainment and zero live cricket. The pricing gap and the licensing gap are both lessons for anyone building software for more than one country.
JioHotstar's global launch went live today in the UK, Canada and Singapore, and the headline number is not the 160,000+ hours of content. It is the zero hours of live sport. TechCrunch reported that IPL, Indian cricket, the EPL, tennis, kabaddi and hockey are all absent at launch, blocked by existing licensing deals.
I want to look at this as an engineering and pricing story rather than a media one, because both halves are things I keep watching Sri Lankan teams get wrong.
🌐 The product shape was decided by contracts, not code ⚖️
JioHotstar in India is, functionally, a cricket app that also has dramas. It reached 500+ million monthly active users and at one point held roughly 85% of the Indian streaming audience, and live cricket is the reason. The international build ships without it.
| Content type | India | UK / Canada / Singapore |
|---|---|---|
| Indian films & TV originals | ✅ | ✅ |
| Reality shows (Bigg Boss) | ✅ | ✅ |
| Live TV channels (Star Plus, Colors, Asianet, Star Jalsha, Star Vijay, Star Pravah) | ✅ | ✅ |
| IPL / WPL / Indian cricket | ✅ | ❌ |
| EPL, tennis, kabaddi, hockey | ✅ | ❌ |
TechCrunch reports the company has not ruled out adding sports later. That is the tell: this is not a technical limitation and it is not a product decision. Somebody else already sold those territories.
Key takeaway: If your product depends on rights, data, or APIs you license rather than own, your feature list in a new market is written by a lawyer, not by you. Find out what you're allowed to ship before you scope the sprint.
I've seen the local version of this. A team builds a fintech dashboard against a bank feed, then discovers the data-sharing agreement covers one jurisdiction. A learning platform licenses a textbook set for Sri Lanka and finds it cannot serve the same PDFs to a user on a Dubai IP. The code was never the constraint.
💰 The same catalogue costs up to 10× more outside India 📈
Here are the launch prices, with the approximate USD figures TechCrunch quoted. The per-month equivalent column is my own arithmetic on those numbers, so treat it as indicative.
| Market | Quarterly | Annual | Annual ÷ 12 (approx USD) |
|---|---|---|---|
| India | — | ₹2,199 (~$23) | ~$1.92 |
| India (entry tier) | — | ₹79/month (~$0.80) | ~$0.80 |
| Canada | CA$19.99 (~$14) | CA$49.99 (~$36) | ~$3.00 |
| Singapore | SG$29.98 (~$24) | SG$69.98 (~$55) | ~$4.58 |
| UK | £19.99 (~$27) | £69.99 (~$95) | ~$7.92 |
So a UK subscriber pays roughly 4× the top Indian annual tier and close to 10× the entry Indian monthly tier for a catalogue that is, by the company's own description, smaller. No cricket, same money, times four.
That is not greed. It is willingness-to-pay pricing, and it is the single most common thing Sri Lankan freelancers and small SaaS teams leave on the table. Three patterns I'd push back on:
- Converting your LKR rate to USD and quoting that. Your cost base is not your customer's budget. A London client benchmarks you against London.
- Publishing one global price. JioHotstar's Canadian price is less than half the UK price. Same product, same quarter.
- Discounting to win a market you haven't validated. JioHotstar priced Singapore above Canada. Someone did the diaspora density maths first.
If you're sanity-checking what a foreign rate actually leaves in your account after fees, our Freelancer USD-LKR Earnings Calculator does the Wise/Payoneer/Skrill comparison for you.
🛠️ What a territory-gated product costs you in engineering 🔧
The interesting part of a launch like this is the machinery underneath. Once availability varies by country, a pile of things stop being constants:
- Entitlements become a matrix, not a boolean.
user.isSubscribedis dead. You need(user, region, contentId, time) → allowed?. - Geo-detection becomes a support burden. Every VPN user, every traveller, every diaspora member with a home-country payment card files a ticket.
- Localisation scales with the catalogue. JioHotstar is shipping 12 languages including English, Hindi, Gujarati, Malayalam, Kannada and Marathi. Twelve languages is twelve QA passes.
- Migration has to be invisible. Hotstar ceases to exist in those three markets and existing credentials carry over. Silent account migration is one of the least glamorous, highest-risk things you can ship.
In practice the sane pattern is to make availability data, not logic. Something like:
{
"contentId": "ipl-2027-live",
"type": "live_sport",
"availableIn": ["IN"],
"blockedReason": "rights_not_licensed",
"tiers": ["premium", "super"]
}
Keep it in one place, load it at request time, and never let a region rule leak into a React component. If you're turning a config shape like that into typed interfaces, our JSON to TypeScript Converter will generate them in one paste.
The rule I'd hold to: any check that can vary by country belongs in configuration your ops team can edit, not in a deploy.
🚀 The diaspora is a real, addressable market 🌏
The stated target is 4+ million South Asian diaspora members across those three countries. That is the whole thesis: not "compete with Netflix", but "serve people who already want this and currently can't get it legally".
Sri Lanka has the same structural asset. There are large Sri Lankan communities in Toronto, London, Melbourne and the Gulf. I don't have a verified figure for how many, so I'm not going to quote one, but the shape of the opportunity is not in doubt, and almost nobody is building for it.
Products that fit this pattern:
- Remittance and bill-payment tooling for people paying utilities back home
- Document and legal-form services for people dealing with Sri Lankan bureaucracy from abroad
- Sinhala and Tamil content, media and education that global platforms will never prioritise
- Local-market marketplaces where the buyer is overseas and the recipient is here
The advantage is that you understand both ends. That is hard to copy from outside.
💡 What this means for you
- Ask what you're licensed to ship before you scope. JioHotstar's international product is missing its best feature for contractual reasons, and it shipped anyway. Shipping the allowed subset beats waiting for the whole thing.
- Price per market. The gap between $0.80 and $7.92 a month for the same brand is not an accident, and there is no reason your rate card should be flatter than theirs.
- Treat region rules as data. Config you can edit, not conditionals you have to redeploy.
- Look at the diaspora before you look at Silicon Valley. Four million people is a market. So is the Sri Lankan equivalent, and you already speak the language.
The lesson I'd take from this launch is unglamorous: a company with 500 million users still had to ship a stripped-down version of its own product to enter three small markets, and it did it rather than wait. Most of us are not blocked by anything nearly that expensive.