Tellyport: build, publish and run TV apps on every platform

Made in Studio

One builder. Every kind of TV app.

Real apps built from Tellyport templates, shown as they run on a TV.

Streaming & live TVRails, genres, details and a full player

Menus & businessPrices from a Google Sheet, specials, sold-out items

Digital signageLooping scenes, tickers, clocks and notices

Quizzes & gamesPlayed with the remote, with leaderboards

Product tour

See Tellyport at work.

Real screens from the Tellyport console, with a demo streaming app on 54 TVs.

Design it like you will watch it

The preview in the middle is the real app at 1080p. Click any block to edit it, and see which platforms support it.

Blocks for heroes, rows, grids, menus, tickers, quizzes and more
Each block shows support for web TV, Roku and Apple TV
Simple mode for teams, Advanced for languages, rules and experiments

Two ways to start

New TV app or one you already have. Tellyport runs both.

No code

Build a new app in Studio

Pick a template, design screens for the remote, connect your content, and get apps for Samsung, LG, Android TV, Fire TV, Roku and Apple TV, ready for each store.

How Studio works

Your code

Connect the apps you already have

Add the SDK for Roku, Android TV, Fire TV, Tizen, webOS, Apple TV, iOS, Android, Flutter or web. Then change backends, flags and config remotely, release with canaries, and watch your device fleet.

What the SDKs unlock

Everything included

39 features, one platform, every plan.

From the first screen design to the millionth device check-in. See every feature.

BuildStudio visual builder · Templates for every kind of app · Native Roku and Apple TV · Live preview on a real TV · …ContentContent library (CMS) · Scheduled publishing · Bring your own feeds PublishStore-ready packages · Store artwork and listing · Submitted for you · Step-by-step store guides ConnectSigned remote config · Servers and automatic failover · API gateway · Mock APIs from OpenAPI · …ReleaseVersions and one-click rollback · Feature flags and targeting · Rollout groups · Canary with automatic rollback · …MonitorDevice fleet · Health checks · Remote diagnostics · Analytics and fleet map · …DevelopersSDKs for every screen · Config as code · GitHub Actions · REST API and OpenAPI Teams and securityRoles and approvals · Single sign-on and 2FA · Tamper-evident audit log · Organizations for agencies

How it works

Build. Publish. Run. All in one place.

Most TV apps need a different team for every platform and a new build for every change. Tellyport replaces both.

01
Build in Studio

Start from a template, design screens with the remote in mind, and preview on a real TV while you work.
Template · Streaming · 6 screens
02
Publish to the stores

Get store-ready packages, icons, screenshots and listing text, then submit to Google Play, Amazon and App Store Connect from Tellyport.
Play · Amazon · Apple · Samsung · LG · Roku
03
Run it without rebuilding

Update content, layout, flags and backend addresses from the console. Signed, canaried, and live on every TV in minutes.
v52 · signed · canary 10% → 100%

Studio

A visual app builder made for the remote, not the mouse.

Every screen is designed for ten feet away and a D-pad: focus states, rails, safe areas and big type are built in, so the app feels native on every TV.

Any kind of TV appStreaming and live TV, digital signage, menus and info screens, quizzes and games, kids apps.
Native where it mattersReal SceneGraph on Roku and SwiftUI on Apple TV, not a web page in a wrapper.
Live preview on your TVSee every change on the device in your living room as you make it.
Bring your own feedsConnect M3U, MRSS, JSON, CSV or iCal sources, or use the built-in content library.

Streaming & live TV

Rails, EPG, live channels, details pages and a full player.

Digital signage

Looping scenes, tickers, clocks and weather for lobbies and stores.

Menus & business

Price lists, schedules and contact screens from a Google Sheet.

Quizzes & games

Quiz, poll, spin wheel and leaderboards, played with the remote.

Kids

Bright, rounded and simple, with storytime and safe navigation.

Templates

Start from a ready app and make it yours in an afternoon.

Content library

Your content, managed in one place. Live on every app.

A built-in CMS for every app you make. Add a film, fix a title or schedule tonight's premiere, and every TV picks it up on its own, on every platform.

Collections and itemsMovies, episodes, channels, products or menu entries, with images and streams.
Scheduled publishingSet a date and time; the item appears on every TV when it is due.
One library, many appsShare a collection across apps and platforms without copying anything.

Publish

From design to store listing, without a platform team.

Tellyport builds the package for each store, makes the icons and screenshots each store asks for, and walks you through every submission. Where a store has an API, Tellyport submits for you.

Google PlaySubmitted by Tellyport

Android TV and Google TV. App bundle uploaded to the track you choose.

Amazon AppstoreSubmitted by Tellyport

Fire TV. APK uploaded and sent for review.

App Store ConnectSubmitted by Tellyport

Apple TV. Listing, screenshots and review details sent for you.

Samsung Seller OfficeStep-by-step guide

Tizen package ready to upload, with every step explained.

LG Seller LoungeStep-by-step guide

webOS package and assets, with the review checklist.

Roku Channel StoreStep-by-step guide

Channel package and artwork, plus how to sign it on your Roku.

Icons, banners and splash screens in every size
Screenshots captured from your app
Listing text sized for each store
Signing keys encrypted, never shown again

Control plane

Run apps you can't easily update.

Store reviews, TV certification queues and viewers who never update. Every Studio app gets the Tellyport control plane built in, and apps you already have can use it through our SDKs.

Change the backend without shipping a build

Move every installed app to a new API host, region, or vendor from the console. Gateway routes keep the same paths while the origin behind them changes.

Mock backend from OpenAPI

Import an OpenAPI spec and get working mock routes in seconds, built from your examples and schemas. Your app ships before the backend exists, then you flip each route to proxy.

Ed25519-signed config

Every published config is signed, and the SDKs verify it before trusting anything. On TVs without Ed25519 support (Roku, older Tizen and webOS), the SDKs only accept config over pinned or validated HTTPS.

Keeps working if we're down

SDKs fall back to the last verified config, then to the defaults bundled in your app. An edge layer serves the last good signed response if the origin is unreachable.

Remote diagnostics

Request logs, app state, and a screenshot from a specific device. It answers on its next heartbeat, so support can see what the customer sees.

Canary releases with automatic rollback

Send a change to 5% of devices first. Tellyport compares canary and stable device telemetry and stops the canary on its own when errors climb, then alerts you in Slack or PagerDuty.

Release risk check

Before you publish, see what changes, which hosts are unreachable, and how many devices a raised minimum version would force to update.

Fleet map & analytics

Active devices, requests, error rate, and p95 latency over time, broken down by country, platform, app version, and config version.

Config as code

Pull the environment into Git, review changes as diffs in pull requests, and push or publish from the CLI or a GitHub Actions workflow with a scoped service token. Approvals and canaries still apply.

Security & governance

Powerful enough for production. Safe enough to hand to a team.

Changing what millions of screens do should be deliberate, reviewed, and traceable. Tellyport is built that way by default.

Roles & approvalsRequire a teammate to approve production publishes. Rollback never waits.
Single sign-on & 2FAOIDC sign-in with verified domains, plus authenticator-app two-factor for everyone.
Signed configurationEd25519 signatures, verified by the SDKs before anything is applied.
Hash-chained audit logEach entry links to the one before it, so history can't be quietly edited.
Scoped service tokensCI gets editor or viewer access to named projects only.

Developers

Ten lines in the app. The rest is in your pipeline.

Every SDK fetches signed config, caches the last good copy, retries with backoff, and reports device health. The CLI and GitHub Actions put config in code review.

SDK guides CLI & GitHub Actions OpenAPI

const mesh = new OriginMeshClient({
  origin: "https://mesh.example.com",
  project: "tv-app", environment: "production",
  clientKey: "om_pk_...", bundledConfig,
});
const config = await mesh.getConfig();
api.setBaseUrl(config.config.api_base_url);
// verified, cached, falls back to last-known-good

let client = try OriginMeshClient(
  origin: URL(string: "https://mesh.example.com")!,
  project: "tv-app", clientKey: "om_pk_...",
  bundledConfig: bundled)
let result = try await client.getConfig()
let api = result.payload.endpoint("api_base_url")
// .remote / .cache / .lastKnownGood / .bundled

val client = OriginMeshClient(
  origin = "https://mesh.example.com",
  project = "tv-app", clientKey = "om_pk_...",
  bundledConfig = bundled, storage = prefsStorage,
)
val result = client.getConfig()
val api = result.payload.endpoint("api_base_url")

# config as code: pull, review, push, publish
node originmesh.mjs pull -p tv-app       # → originmesh.json
node originmesh.mjs diff
node originmesh.mjs push -m "Move API to eu2"
node originmesh.mjs publish --rollout 10 \
  --reason "Move API to the eu2 cluster"

on:
  push: { branches: [main], paths: [originmesh.json] }
jobs:
  originmesh:
    runs-on: ubuntu-latest
    env:
      ORIGINMESH_TOKEN: ${{ secrets.ORIGINMESH_TOKEN }}
    steps:
      - uses: actions/checkout@v4
      - run: node tools/originmesh.mjs push --file originmesh.json
      - run: node tools/originmesh.mjs publish --reason "$GITHUB_SHA"

Pricing

Start free. Pay as your audience grows.

Every feature on every plan. Plans differ by apps and active devices, never by seats.

Free

For trying Tellyport and side projects.

$0forever

Studio app builder and templates
Publish to every TV store
1 app
500 active devices
Community support

Starter

One TV app going live.

$49per month

Studio app builder and templates
Publish to every TV store
1 app
5,000 active devices
Email support

Growth

Agency

Build and run apps for your clients.

$999per month

Studio app builder and templates
Publish to every TV store
Unlimited apps
250,000 active devices
Shared support channel

Enterprise

Large fleets, SSO and a contract. Custom limits, single sign-on, an approvals policy, a dedicated data plane and an SLA.

Contact sales

Paid plans never block new devices: extra active devices cost $8 per 1,000 a month.

Compare plans and estimate your cost

Compare

Tellyport vs Firebase Remote Config and feature-flag tools

If you only need feature flags in a mobile app, Firebase Remote Config is free and excellent, and dedicated flag platforms are great at experimentation. Tellyport is for teams that also need to control where apps connect, across TV platforms, and to operate the device fleet.

Capability	Tellyport	Firebase Remote Config	Feature-flag tools
Price to start	Free plan, then from $49/mo	Free	Varies by vendor
Mobile & web SDKs	iOS, Android, Flutter, web	iOS, Android, Flutter, web, Unity, C++	Broad SDK coverage
TV platforms	Roku, Android TV, Fire TV, Tizen, webOS, Apple TV	Android TV and tvOS through the mobile SDKs; no Roku SDK	Varies; some offer Roku or TV SDKs
Feature flags & targeting	By platform, version, channel, country	Rich conditions, plus A/B Testing	Advanced targeting & experimentation
Backend endpoint routing & failover	Built in, with gateway routes	Store URLs as parameters yourself	Store URLs as flag values yourself
Mock backend (OpenAPI import)	Built in	Not offered	Not typically offered
Signature verified on device	Ed25519, verified by the SDKs (pinned HTTPS on Roku)	Relies on HTTPS	Varies
Gradual rollout	Canary with automatic rollback from device telemetry	Percentage rollouts, monitored with Crashlytics	Percentage rollouts; some offer guarded releases
Device fleet operations	Device list, remote diagnostics, fleet map	Separate Firebase products	Not the focus

Comparison reflects publicly documented capabilities as we understand them; check each vendor's docs for current details. Product names belong to their owners.

FAQ

Questions, answered

Still unsure? Read the docs or email us.

Do I need developers to build a TV app with Tellyport?

No. Studio builds the app from a template and your content. Developers can still go further with custom blocks, their own feeds, and the SDKs and API.

Which stores can Tellyport publish to?

Tellyport submits to Google Play, the Amazon Appstore and App Store Connect through their APIs. For Samsung, LG and Roku, whose stores have no public upload API, you get the finished package and a step-by-step guide. You need your own developer account on each store.

Do I have to resubmit to the stores for every change?

No. Content, layout, flags and backend addresses change from the console and reach installed apps directly. You only resubmit when the app itself needs new native capabilities.

What happens if Tellyport is unreachable?

Your apps keep running. An edge layer serves the last good signed response if the origin is down, and apps fall back to the last verified config on the device, then to the defaults bundled in the app.

Is the Free plan really free forever?

Yes. One app and up to 500 active devices, with every feature, at no cost and with no card required. Upgrade when you need more apps or devices.

What counts as an active device?

A TV or device that loaded your app's config, registered, or checked in during the last 30 days. Paid plans never block new devices; above the included amount you pay a small fee per 1,000 devices. On the Free plan, new devices stop at the limit.

Can I use Tellyport with an app I already built?

Yes. Add the SDK for Roku, Android TV, Fire TV, Tizen, webOS, Apple TV, iOS, Android, Flutter or web, and control config, flags and backends from the console. See the SDK guides.

Can someone push a change to production on their own?

Only if you allow it. Roles control who can edit and publish, approvals can require a teammate's sign-off, and every action is recorded in a hash-chained audit log.

Build your TV app once. Launch it on every screen.

One design. An app for every TV your viewers own.