GodwinOTT is a live TV service that carries your name and your colours. Viewers open your address on a phone, tablet or laptop and get every channel live, a guide of what is on now and next, favourites and your shows on demand, while your team runs the whole thing from admin screens in a browser.
Both films show the real product, running on demo data. The overview has a voice over and runs well under a minute. The promo film has sound effects and no voice.
"Viewers keep asking where they can watch us on their phone."
People still want your channels. They just want them on the screen in their hand, and if they cannot find you there they find somebody else's stream.
"Our clips do well on the big platforms, and then the audience stays there."
The views count for the platform. So does the viewer's account, the list of who watches, and most of the advertising money.
"We priced an app from a big vendor. It was a fee for every viewer and months of waiting."
A bill that grows with your audience punishes you for doing well, and a long project means another season without a service.
GodwinOTT answers those three in one place. Your channels play at your own address. The viewer accounts, the viewing numbers and any subscription income are yours. You pay for your own servers and bandwidth, and there is no charge per viewer.
Every picture here is the real product with demo channels. Click any of them to see it full size.
Viewers see your whole lineup with a recent picture on each card, numbered the way they know it from the broadcast (2.1, 4.1, 13.10), and sorted in that order. Rows for live now, favourites and each category make a long lineup easy to read.
Twelve hours ahead, moving with the clock. It fills itself from your guide feed every half hour, or your team uploads a file. The player shows what is on now and what comes next over the picture.
Your library becomes an on demand section with its own featured slides, latest episodes and a page for every show. The player remembers where a viewer stopped and counts down to the next episode.
Short vertical clips play full height, one after another, the way people already watch on their phones. Radio programmes and podcasts get an audio player with 15 second skips and controls on the phone's lock screen.
Turn shows you already own into a 24 hour channel: a loop, with fixed slots such as morning prayer at 06:00 on weekdays. It plans seven days ahead, writes its own guide, and appears in the lineup like any live channel.
Your team picks the big slides at the top of the home page and the on demand page, drags them into order, and can give a slide a start and end time, so the Sunday service leads on Sunday morning and steps aside after.
Leave it open to everyone, ask viewers for a free account, or put a PIN on the whole site while you prepare. Any channel or show can be for members or subscribers only. Signed in viewers keep up to 200 favourite channels.
Who is watching now, which channels and shows do best, at what hours, on which devices, and how well playback went. The numbers are counted on your own system, with no outside tracker on the site, and export to a spreadsheet.
If you charge, monthly or yearly plans run through your own Stripe or Razorpay account, with trial days and three days of grace when a card fails. Viewers pay on the provider's own checkout page. We take no share of it.
Viewers see your name, your logo, your colours and your web address, never ours. Your team can change the branding from a screen with a live preview, and it applies straight away.
Each one follows a real person's use of the service from start to finish, on demo channels.
Ada gets home and opens the station's address. She picks a live channel from the home page, flips between channels without leaving the player, looks an hour ahead in the guide and saves a favourite. Then she finds last night's episode of a show on demand.
What your viewers get, in the order they get it.
Sam runs the station's service. In one sitting he renames a channel, changes what leads the home page, adds a new episode to the library and checks the channel he built from the archive. Nothing here needs an engineer or a restart.
The everyday work, done from a browser.
What the person who owns the service looks at: how many people watched this week, which channels and at what hours, how well the picture started and kept playing, and how plans and billing connect to your own payment account.
The numbers and the money, both kept on your side.
Shorter takes with no sound, made while the product was being tested.
Home, a live channel, switching from the player, a favourite and the guide.
Renaming a channel, reordering the home page slides and reading the analytics.
Uploading a video, which is prepared for streaming and plays on the on demand page.
Ada is a viewer. Sam runs the service for the station. Both are made up; the screens are real. Click a picture to enlarge it, then use the arrow keys to move through the tour.
What a viewer sees when she opens your address in a browser.
Ada opens the station's address after work. Tonight the big slide is the Friday Night Movie, live on channel 9.1, and her three favourite channels sit right under it.
Further down, each card shows a recent picture from the channel, its number, what is on and how long is left. The Briefing on News 24 has 37 minutes to go.
She picks Movies on 9.1. The player shows what is on now, how much of it is left and what follows at noon. The heart at the top adds the channel to her favourites.
She opens the channel row inside the player and moves along it with the up and down keys. Full screen stays on while she changes.
The guide starts at the current time, marked by a blue line. Ada scrolls ahead, sees Matchday Live at 10:30 on Sports One and knows when to come back.
She types "sport" and gets both sports channels, live, and the highlights video from the on demand library.
Morning Devotion has its own page. Play all runs the four episodes in order; Play latest starts with today's.
Audio episodes play in their own player with 15 second skips. On her phone the same controls sit on the lock screen, so the programme keeps going in her pocket.
The same service at phone size. There is nothing to download; it can be added to the home screen like an app.
The same service on Ada's phone, with the menu at the bottom where her thumb is. Nothing to install; she added the address to her home screen.
The picture sits at the top, now and next under it, and the channel list below, so switching is one tap.
The guide works at phone width too, with the channel column kept on the left as she scrolls.
Short vertical clips fill the screen. She swipes up for the next one.
The admin screens your team uses every day.
Sam runs the service for the station. Each row has an on and off switch, the number and name viewers see, a category and who can watch. Switching one off takes it out of the lineup within about ten seconds, with Undo.
Sam decides what leads the home page. The slides run in the order shown; dragging Sunday Service to the top for Sunday morning takes a second, and Preview shows the result full screen.
New episodes are dropped onto this page or arrive on their own from a shared Google Drive folder. Each one is prepared for streaming and shows Ready once viewers can play it.
On Demand 24 is a channel Sam built from five library items in a loop, with fixed slots for set times. Its guide is written from this plan.
To Ada it is channel 30.1, live like the others. Ocean Worlds: The Reef is on now and a community choir concert follows.
When Ada writes in, Sam opens her account: what she watched in the last 30 days, her favourites, and buttons to sign her out everywhere or block the account.
One switch decides whether viewers need an account. Another puts a PIN on the whole site before launch. The log on the right shows each change and who made it.
Minutes watched by weekday and hour. On this demo data the busiest slot is Saturday around 8 pm. Beside it, how many visits turned into a real play.
Viewing numbers, brand and money. These screens are for a small group you name.
The station manager opens Analytics on minutes played, viewers, starts and new sign ups, each compared with the week before. All of it is counted on your own system.
How often a play failed to start, how long the first picture took, and how much time went on buffering. A bad match day shows up here while it is happening.
Name, tagline, colours, logo and privacy text, with a live preview on the right. Saving changes the site at once.
If you charge, you connect your own Stripe or Razorpay account here and set plans and trial days. Viewers pay on the provider's own checkout page, into your account. Billing stays off until you switch it on.
Find the one closest to you. The use cases document (PDF) covers each in more detail, including what would still have to be built for it.
GodwinOTT runs today for a broadcaster with 51 live channels. Their viewers watch on computers and phones, with a programme guide across the lineup. If you visit their site you see their name and their colours. GodwinOTT does not appear anywhere, and that is how it should be.
A good part of what is in the product came from working with them. Channel numbers that match the broadcast. Plain words in the player when a channel drops, such as "Reconnecting" or "off air right now", where other players spin. New episodes that arrive from a shared folder of daily shows. And the rule that nothing plays until a viewer asks for it, because their connection has a limited amount of upload to share across every channel.
We do not name the client on this page. If you would like to speak to them, ask us and we will ask them.
These durations are our estimates for a typical client whose channels are already streaming. A tidy channel list and a guide feed move faster. Most of the calendar goes on content, decisions and waiting for outside parties; the technical setup itself is about a working day once your accounts are ready.
We go through your channels, rights, guide data, library and who should see what, and agree what you need on day one.
You bring: channel list, rights notes, a sample guide file, the people who will run the admin side.
We set up the service on your machines and your web address, and make the first admin sign in.
You bring: your domain, access to your server, a Google account for sign in. Waiting on outside parties can add time.
Name, colours, logo, privacy text, channel names, numbers and categories. The site stays behind a PIN.
You bring: logos, colours, the wording you want, your privacy text.
The guide filling itself, the library loaded or syncing from Drive, playlist channels if you want them, the first slides.
You bring: guide source, video files or a Drive folder, cover pictures.
Sign in on or off, who can watch what, plans and trials if you charge, tested end to end.
You bring: a Stripe or Razorpay account, prices and plan names, your access rules.
A small group of real viewers. We watch the quality numbers and fix what they show.
You bring: a list of test viewers and a support address someone reads.
PIN off, your announcement, and a close watch on the first week.
You bring: the announcement, and someone on hand to answer viewers.
Two separate things. Our fee for setting it up and looking after it is quoted per deployment after a short call, once we know your channels and what you need on day one. It can be paid in parts at milestones with a monthly fee for ongoing care, or spread into one monthly payment.
Your running costs are paid straight to the providers, in your name. The figures below are public prices, as estimates as of October 2026. Check each provider's current page before you budget.
| Item | Estimate |
|---|---|
| Website hosting | $0, on a free plan |
| Domain name | $10 to $20 a year (.tv names often cost more) |
| A rented public server that carries the video | $5 to $60 a month, depending mostly on how much monthly transfer is included |
| Bandwidth | Each viewer uses about 1.8 Mbps. One viewer hour is roughly 810 MB, so 1 TB covers roughly 1,200 viewer hours. |
| Your own machine for the service | $0 if you use the equipment that already runs your channels; otherwise a rented server at roughly $50 to $150 a month |
| Google sign in | $0 |
| Card payments | Your provider's own fees. We take no share. |
| Video player licence | Only on one of the two player routes (see Honest scope). We confirm the vendor's price with you during discovery. |
There is no per viewer fee and no fee to us that grows with your audience. Doubling your audience doubles your bandwidth bill and nothing else.
The full checklist of what to gather is in What we need from you (PDF).
It puts your live channels, shows, shorts and audio on a website at your own address, under your own name, and gives your team the screens to run it.
Today, a broadcaster with 51 live channels. It is built for anyone with live channels or a library: TV networks, churches, schools, leagues, civic channels.
Our fee is quoted per deployment after a short call. Your running costs are a domain, a rented server and its bandwidth, paid to the providers. There is no per viewer fee.
Our estimate is 6 to 12 weeks from the first meeting, depending mostly on how ready your channels and library are, and whether you take payments.
Play links expire, admins sign in with Google and cannot be added from a screen, card details never reach the platform, and viewer IP addresses are not stored. It all runs on machines in your name.
Yes. Names and numbers come from the broadcast signal, in the form viewers know (8.1, 13.10), and sort correctly. Your team can change any of them on the Channels screen.
Switch it off on the Channels screen. It leaves the lineup, guide and search within about ten seconds and nobody new can start it. A viewer who already had it open can keep watching for up to six hours.
Yes. Share a Google Drive folder and the platform checks it every 30 minutes, picking up new episodes on their own. It never overwrites an edit your team made.
Yes. Every channel, show and video has a "who can watch" setting: everyone, members or subscribers. Signed out viewers either do not see it or see it locked with a button to sign in.
The site stays up and shows the last good lineup with a "Reconnecting" notice. Video comes back when your machine does.
No. It is a web app. TV browsers work and are counted in the analytics, but there is no Roku, Fire TV, Apple TV or Android TV app yet.
There is no reset email yet. We suggest Google sign in for viewers, and your team can help by hand. Building email sending is on the list of possible next work.
Yes. The servers, domain, accounts and data are in your name from the first day. You can run it yourselves or hand it to another engineer.
The full list is in Questions and answers (PDF).
We would rather you read this here than find it after launch. Each item can be scoped and quoted; some are small, and native apps are a project in their own right.
| Missing | What it means for you |
|---|---|
| Phone and TV apps | Viewers use the web app, which they can add to a phone's home screen. There is no app in the App Store, Google Play, Roku, Fire TV or Apple TV. |
| Casting | No Chromecast or AirPlay button in the player. |
| Captions | None yet. Many schools and public bodies need them before launch. |
| Email sending | No sign up confirmation emails and no password reset by email. Google sign in avoids most of this. |
| Ads | No adverts inside streams or between programmes. |
| Pay per view | Plans are monthly or yearly only. No single event tickets, and no coupons. |
| Live rewind | Viewers cannot scroll back in a live channel. |
| Other languages, other sign in | One interface language. Sign in is Google or email and password; no Microsoft or school sign in. |
| Trade off | Why, and your choice |
|---|---|
| The video player | The live and on demand players use a commercially licensed player. You either buy your own licence, or we build a plain player that needs none (a few days of work by our estimate). We settle this in discovery. |
| No previews that play by themselves | Channel cards show a recent picture, so you only pay bandwidth for what people actually watch. |
| Bandwidth grows with viewers | Your bill rises with your audience. You see viewer hours from the soft launch on, so there are no surprises. |
| Copy protection has limits | Stream protection stops a passed on link. It cannot stop someone filming or recording their screen. |
| Switching a channel off | New viewers are stopped within seconds; someone already watching can carry on for up to six hours. |
| Viewing numbers in one time zone | The zone must sit a whole number of hours from UTC all year, which rules out half hour zones such as India's. |
| The privacy page | We give you a draft and a list of what is stored. Your own adviser approves the final text. |
| You own the servers | They are yours, so someone has to look after them. That can be us, under a monthly arrangement, or your own engineer. |
One Next.js codebase built two ways. Static pages sit on Cloudflare's free plan at your watch domain. The app server and Postgres 16 run in Docker on your own Linux machine. An nginx server on a small VPS carries the API and all video, joined to your machine by a WireGuard tunnel your machine dials out on, so it opens no port. Video comes from your own HLS packager through signed URLs and never passes through Cloudflare.
GodwinMix is our live production desk: one person switching cameras, guests and graphics into one programme. That programme can be the feed for a GodwinOTT channel, with its own place in the lineup, the guide, the members lock and the viewing numbers, the same as a channel that comes off air.
Each product has been built and tested on its own. They have not yet been run together end to end, so read this as the design we intend, with a one day joint test as the first step.
Each document is a PDF you can print or forward.