Within the Kronos Backend, 2 primary node types are supported, with additional subtypes (Products applied to them).
The primary node types define what software is supposed to be used on the node, these are;
A node with primary type "Plex Appbox" is used to deploy plex appboxes in Docker containers and can accept the following types of products
A primary node of "Plex Appbox" with a product of "Plex Invite" means you will deploy 1 or more containers on the node, that will accept plex invites, via the plex Friends system.
A node with primary type "Emby" will support a docker installation of Emby, for sending out invites to your customers(Similar to the plex Friends system)
An "Emby appbox" system is not currently supported, due to insufficient methods of controlling system load with Emby.
Primary types are set-in-stone supported types by Kronos, products can be defined by you(via WHMCS) to allow for a refined ruleset when deploying customers.
For example, for the primary "Plex Appbox" nodes, you may want 2 different Appbox products;
When a node is installed in Kronos, and the "Plex Appbox" type is picked, and the "4k" product is applied to it, then when accepting orders of the "4k" type via WHMCS, insures that these customers are only deployed to a node with available room, accepting "4k" customers.
When Kronos is linked to a WHMCS installation, Kronos will automatically fetch available products configured in WHMCS under the "Setup -> Products/Services" tab.
These products can then be viewed, and rules defined via the Kronos settings panel located at
Here you can select a product, define the amount of allowed transcodes(For Emby and Plex invites and/or appboxes) the product type(Primary types), whether to deploy automatically when accepting the order
Upon configuring the products for each product within the settings panel above, simply create a node in Kronos and apply the "Service type"(Primary type) as well as the "Node type"(The product type), if "Plex appboxes" and "4k" is defined for a node here, that means when an order on WHMCS is accepted, for it to be deployed to this node, the order must be;
Create a tar of the Emby finished library similar to Plex. Simply install Emby on your node first, scan the library, and tar it just like with Plex.
Optionally, you can manually install Emby and scan the library on your node.
We strongly recommend still using the 'Plex Appbox' instructions to create an image so you can easily deploy new Plex invite nodes for scaling, however as a Plex invite node will typically only have 1 or 2 containers running plex (on which customers are then invited) you can also just do a "quick deploy" via Kronos, which will simply install plex - Then manually scan your library and begin inviting your customers