Lumvara and Fora Soft logos

White-label IPTV for Apple TV, Android TV and Fire TV

Published: Nov 14, 2026
Lumvara TV home screen with a featured title, Continue Watching and trending movies
Lumvara Movies catalog on a TV with genre filters and movie rows
Lumvara series detail page on a TV with episodes and playback options
Fora Soft developed Lumvara's software end to end: the TV design system, three TV clients, the Node.js middleware and the web panels for Palmoc and its resellers. The first app reached an app store three months after the first line of code, all three stores followed two weeks later, and development continues.
Lumvara Movies catalog on a TV with genre filters and movie rows
Palmoc operates Lumvara, a white-label IPTV and video-on-demand platform for independent IPTV resellers in North America. Subscribers watch live channels, a program guide, catch-up TV, movies and series in one app on Apple TV, Android TV / Google TV and Amazon Fire TV.

A shared player for resellers

Each reseller keeps its subscriber accounts and billing. Lumvara reads authentication and subscription status from Xtream Codes and billing updates from WHMCS. The reseller's logo, renewal link and announcements appear inside the shared app.

Lumvara is a player, not a content provider. It doesn't host video, supply channels or movies, or sell subscriptions. Subscribers get content from their reseller's IPTV portal.

Who provides what: the reseller handles subscriber accounts, billing in WHMCS and logins in Xtream Codes; Lumvara provides one app on three TV platforms, reseller logo, renewal link and announcements
Flow from the reseller's IPTV portal (accounts, billing and content) to the Lumvara app (reseller logo, renewal link and announcements) to the subscriber's TV

Three TV clients connected to one middleware

Apple TV, Android TV and Fire TV differ in operating system, remote control, focus navigation and store rules. We built a separate client for each and kept authentication, subscriptions, synchronization and other shared logic in one middleware.

Lumvara series detail screen on a TV with episodes and playback controls

Apple TV

Swift and SwiftUI, with parallax artwork, Siri Remote scrubbing and a Top Shelf extension (content shown on the Apple TV home screen when the app is selected).

Android TV / Google TV

Kotlin and Compose for TV, with D-pad navigation and 10-second skips.

Amazon Fire TV

React Native for Vega OS, plus a build for older Fire OS sticks that reuses the Android TV code.

We tuned the apps on the lowest-spec Fire TV stick Lumvara supports, so remote navigation and guide loading stay responsive while the app works in the background.

The shared Node.js middleware handles:

  • Subscriber authentication and subscription status

  • Playlist and EPG fetching, parsing, and caching

  • Cross-device synchronization and profile settings

  • Reseller branding and application configuration

  • Announcements and subscription notifications

Node.js middleware connected to authentication, synchronization, configuration, favorites and notifications
Architecture: Apple TV, Android TV / Google TV and Amazon Fire TV clients connect to Lumvara middleware, while streams go straight from the reseller's portal to the TVs

Video streams go directly from each reseller's IPTV portal to the subscriber's device.

They never pass through Lumvara's middleware. This separates application services from video delivery, so Palmoc's backend doesn't need to relay or pay bandwidth costs for every stream watched.

Xtream Codes and WHMCS integration without subscriber migration

Lumvara had to work with the systems IPTV resellers already use. Moving subscriber accounts and billing into a new platform would mean a migration for every reseller and a second copy of customer data to keep in sync.

We kept Xtream Codes responsible for subscriber authentication and subscription status. Lumvara polls Xtream Codes for status changes instead of maintaining a second independent subscriber database.

For billing, we developed a custom WHMCS provisioning module that sends subscription state changes to the middleware through webhooks. Renewals and suspensions reach the app faster than through polling alone.

Integration diagram: Xtream Codes polled for subscriber status and WHMCS sending state changes by webhook to Lumvara middleware
Lumvara reseller panel Portal Configuration screen with the source portal address field

The integration architecture evolved during development:

One portal per reseller.

An initial shared portal encountered upstream rate limits. We changed the architecture so each reseller has its own portal configuration, resolved when a subscriber signs in.

Hidden upstream addresses.

The subscriber-facing app never displays the reseller's IPTV portal address, including during errors or other application states.

Simpler authentication.

Working with Palmoc, we removed a second panel from the login process and moved subscriber authentication fully to Xtream Codes.

A reseller can offer Lumvara without rebuilding subscriber management or changing how it takes payments.

Operator and reseller panels for managing the platform

Palmoc runs the service, and each reseller controls its own branding and its messages to subscribers. We built two web panels with separate responsibilities.

Both web panels require two-factor authentication with one-time codes (TOTP).

Lumvara operator panel with the list of resellers and their portal configurations

Operator panel

  • Onboard resellers and view their IPTV portal configurations

  • Suspend and reinstate reseller accounts

  • Reset passwords

  • Publish global announcements to subscribers across the platform

Lumvara reseller panel logo upload screen

Reseller panel

  • Configure the reseller's IPTV portal URL

  • Upload and update the reseller logo

  • Set the subscription renewal link

  • Send announcements to the reseller's own subscribers

  • Change the account email address with verification

Lumvara Sign In screen shown in several accent colours used across buttons, highlights and focus rings
Branding is applied dynamically. When a reseller changes its logo, subscribers see the new one the next time they open Lumvara. Palmoc doesn't publish a separate TV app or submit a store update for each reseller.

Live TV and a program guide built for large EPG files

IPTV program guide files can reach hundreds of megabytes. Downloading and parsing them on a TV would eat memory and processing power, especially on older sticks.

We moved EPG processing to the middleware. It fetches XMLTV or JSON guide data from IPTV portals, parses and caches it, and serves the relevant information to TV clients page by page.

The EPG pipeline was load-tested using a 500 MB guide file.

The TV interface provides:

Full-screen program grid
Live channel preview
Playback without restarting
Catch-up TV
Background guide loading
Non-blocking playlist updates

The platform also supports cloud recording of live and upcoming programs.

Processing guides on the backend cuts the data each TV has to handle, and one EPG pipeline serves all three clients.

Lumvara live TV screen with a channel preview and the program guide grid

Profiles, content discovery, and synchronization across TVs

Each account has up to five profiles, each with its own watch history, recommendations and settings.

Profiles can be configured for adults or children. Kids profiles use MPAA age ratings and category restrictions, with PIN protection for sensitive actions.

A child can open a kids profile without entering a PIN, but changing protected settings, unlocking categories, or requesting adult content requires authorization. Three incorrect PIN attempts lock the request.

Lumvara Who's watching profile selection screen

Content discovery

The home screen has Continue Watching and six recommendation rows, and title pages show trailers and cast.

Lumvara TV sign-in screen with a pair code option

TV pairing without a password

A new TV signs in with a one-time pairing code from a TV that is already signed in, not with a password typed on a remote.

Synced across every TV on the account: playback position, audio tracks and subtitles, watch history, My List and profile preferences

Cross-device synchronization

We built synchronization across TVs connected to the same account, covering:

Subscribers start watching on one TV and continue on another without searching for their position or reapplying settings.

Subscription expiry and reseller communications

Subscriptions stay with the reseller, but subscribers see their access status inside the TV app.

The subscription screen shows the reseller's own renewal link, so payment goes through the reseller's existing billing.

In-app announcements work at two levels: Palmoc publishes messages for the whole platform, each reseller writes to its own subscribers.

Lumvara subscription screens: expires in 3 days and has expired, with the reseller's renewal link
Protection matrix for the Android TV / Google TV, Apple TV and Amazon Fire TV clients

Anti-piracy protection tailored to each TV platform

A streaming app runs on devices the operator doesn't control. Its code can be inspected, modified or run in unauthorized environments.

We implemented protections for each platform rather than one approach for all three clients.

Each TV client passed a penetration test before release.

These controls make tampering and unauthorized clients harder; license validation in the middleware adds a check the operator controls server-side.

Backend infrastructure tested for load and failover

If the shared middleware goes down, sign-in, subscription checks, the guide and synchronization stop for every subscriber at once.

We deployed the backend on DigitalOcean with Cloudflare CDN in front of the infrastructure.

Application infrastructure: Cloudflare CDN, load balancer and several Node.js instances

Application infrastructure

  • Multiple Node.js middleware instances behind a load balancer

  • Autoscaling to handle changes in demand

  • Blue/green deployments for controlled releases

  • Infrastructure defined and managed through Terraform

Database layer: Node.js middleware, PgBouncer and highly available PostgreSQL

Database and recovery

  • Highly available PostgreSQL

  • PgBouncer for database connection management

  • Documented failover runbooks

  • Chaos drills, including stopping the primary database to test recovery behavior

Performance testing

We ran backend load tests at three levels: 1,000, 10,000, and 100,000 users, and tuned the system after each run.

We fixed the constraints found at each level before launch.

Deployment and monitoring

GitHub Actions manages CI/CD, while Sentry and uptime checks support error monitoring and availability tracking.

Lumvara live channel playback screen with catch-up programs

Available in three app stores

Lumvara is available in the Apple App Store, Google Play and the Amazon Appstore.

App Store icon
App Store
Google Play icon
Google Play
Amazon Appstore icon
Amazon Appstore

Updates continue to ship across all three platforms.

Technical implementation

🖥 Platforms
Apple TV (tvOS), Android TV / Google TV, Amazon Fire TV (Vega OS and Fire OS), web panels
🔮 TV applications
Swift, SwiftUI, Kotlin, Compose for TV, React Native
📱 Mobile applications (in development)
React Native for iOS and Android
⚙️ Backend
Node.js, TypeScript, PostgreSQL, PgBouncer
☁️ Infrastructure
DigitalOcean, Cloudflare CDN, Terraform
📈 CI/CD and monitoring
GitHub Actions, Sentry, uptime checks
🔗 Integrations
Xtream Codes API, WHMCS with a custom provisioning module, Recombee, TMDB, FCM, APNs
🗃️ QA and project management
Qase, Playwright, Jira

Delivery and outcome

Development ran through six demos, each a working build for Palmoc and its resellers to review.

Their feedback went into the requirements in nine rounds, up to version 1.9 of the product requirements document.

QA covered more than 800 tickets, with automated tests in Playwright.

The first TV app reached an app store three months after the first line of code. Within another two weeks, Lumvara had launched across Apple TV, Android TV / Google TV, and Amazon Fire TV.

Lumvara delivery sequence: API contracts, middleware and authentication, profiles and VOD catalog, live TV and player, search and synchronization, store submission
The project combined native TV development on three platforms, a shared middleware, billing integrations and load-tested infrastructure. We build the same kind of software for other IPTV and OTT platforms.
Lumvara logo with Apple TV, Android TV and Fire TV labels