LAN Backbone appliance¶
Last updated: 2026-10-27
The WyreDeck LAN Backbone is an optional, self-operated data appliance for a trusted home network. It centralizes provider catalog imports, XMLTV guide refreshes, organization, and search for compatible clients on the same local area network (LAN).
You run it on hardware you control. It is not a hosted WyreDeck catalog, a provider subscription, or a media transcoder. Clients resolve playable sources through the appliance and play them from the provider, subject to client and provider capabilities.
What the appliance does¶
A Backbone can:
- import Xtream movie, series, episode, and live-channel catalogs;
- import live M3U playlists with optional XMLTV guide data;
- retain a local catalog and guide, then serve browsing, search, and direct playback-resolution APIs to authorized clients;
- coordinate explicit provider syncs and report their status;
- issue and revoke appliance-specific local device credentials; and
- keep provider credentials and appliance data on your own persistent storage.
The appliance supplies no channels, movies, series, streams, playlists, or provider accounts. Bring only lawful sources that you have the right to use. WyreDeck does not include content, a content subscription, or a hosted catalog.
Local Install or LAN Backbone¶
| Setup | How it works | Useful when |
|---|---|---|
| Local Install | Each supported client connects to its configured provider and keeps its own local catalog and viewing data. | You use one client or want independent setups with no extra hardware. |
| LAN Backbone | One appliance imports and organizes provider data for authorized clients on the LAN. | You want a shared appliance-managed catalog without repeating the full import on every client. |
A Backbone does not make every client feature shared. Device-local profiles, favorites, progress behavior, metadata support, and playback capabilities still depend on the client, source edition, and account tier. A shared protocol is not a promise of universal client or media-format support.
Local ownership and account pairing¶
Provider credentials, playlist URLs, imported catalogs, and Backbone-held viewing state stay on your appliance rather than in the WyreDeck account service. Provider and guide sources still receive the requests needed to refresh the data you configured.
An account is optional for local Free use. Local LAN trust and WyreDeck account pairing are different actions:
- LAN trust authorizes one client to use one appliance. An operator approves the client's request from the appliance command line.
- Account pairing enrolls a device with the anonymous WyreDeck account service for account, tier, and device-management functions.
The appliance is not an entitlement authority. It cannot invent account capabilities or turn source code into a paid grant. Planned Premium capabilities on Full require the applicable account grant, and Premium is not currently active or available for purchase.
Under the initial five-device service configuration, an enrolled appliance counts as 1 of the 5 device slots on a Premium account, and consumes one ordinary slot on Free as well. This is an example of the initial configuration, not a fixed limit or a promise of a larger Premium allowance. The account service reports the current limit.
Standard and Full are source editions¶
Standard and Full describe which Backbone implementation is installed. Free and Premium describe account tiers; they are not alternate names for those editions.
- Standard is the planned free public distribution with Premium execution physically omitted. Its public release location, source license, and final supported-client details have not been finalized.
- Full contains the shared foundation plus private Premium implementation. Its distribution method is not finalized, and installing it would not by itself activate Premium features.
Private implementation and internal testing are not commercial availability. See the current WyreDeck Help center for general account guidance.
Honest connection failures¶
A discovered appliance is not automatically trusted, and an unreachable appliance is not replaced with an invisible second provider setup. When a client is using a Backbone-managed provider, it does not silently fall back to a local provider copy.
If the appliance is off, unreachable, or has revoked that client's trust, the client should report the connection problem. Reconnect or repair local trust explicitly; choose a separate Local Install only if that is the setup you want.
Read the Privacy policy for the canonical account-service privacy boundary.