Use this space before a ticket is opened, before a migration starts, or while reviewing plans, add-ons, billing cadence, licensing activation, reseller growth, and update discipline.
Start from the operational basics.
The first release of the public knowledge base focuses on the questions prospects and customers actually need answered before rollout: how access works, how plans map to licensing, and how support and reseller workflows are meant to operate.
Registration creates the billing-side customer flow first, then payment unlocks the next guided steps for activation and licensing.
Read articleThe client portal is where approved customers access invoices, subscriptions, and the commercial side of their relationship with panelX.
Read articleThe main IP is collected after payment because it belongs to the activation phase, not the pre-sales phase.
Read articlePlans, plugin add-ons, and extra load balancer quantity are carried from billing into licensing so the activation data remains commercially coherent.
Read articleThe reseller workspace covers line operations, package selection, sub-reseller structure, proxy workflows, tickets, and customer-facing activity.
Read articlepanelX is shaped to support hierarchical growth without turning the reseller layer into a confusing admin mirror.
Read articleThe VOD workflow is built around catalog quality as much as ingestion speed, so metadata, movies, series, and watch folders stay coordinated.
Read articleThe platform can mark content editorially so the player-facing runtime can expose parental-control-compatible signals where supported.
Read articlepanelX is positioned as maintained software, so updates, bug resolution, and product refinement remain part of the customer relationship.
Read articleCustomers stay on branded panelX surfaces for guidance while the client portal centralizes billing continuity and structured support handling.
Read articleMigration is treated as a guided commercial and technical phase, not as a side note to the software sale.
Read articleProxy tooling can be extended into the reseller layer so a reseller can manage proxy behavior for their lines and child resellers where entitled.
Read articleHow commercial registration works
panelX registration is intentionally guided. The first step creates the commercial account and invoice flow so billing, support, and activation stay aligned from the start.
- Registration creates the customer record and commercial document first.
- Payment confirmation is the point where activation starts to matter.
- Main IP authorization belongs to licensing, so it is requested after payment.
What the client portal is for
The client portal is the customer area for invoices, billing rhythm, account-level visibility, and structured support continuity. It is not the licensing backoffice.
When the main server IP is requested
The main IP is requested once the commercial side is confirmed because it belongs to the activation sequence. This keeps pre-sales, payment, and licensing cleanly separated.
How plans and add-ons stay aligned
Named plugin add-ons and extra load balancer quantity remain attached to the base license, not sold as free-floating products. This keeps billing and licensing coherent.
What resellers can do inside panelX
The reseller surface is designed for line operations, packages, sub-reseller structure, ticket flow, and customer-facing work without forcing everything back through the admin layer.
Sub-reseller structure and growth
Hierarchical reseller growth is part of the operating model. The goal is cleaner commercial delegation, not a chaotic copy of the full admin panel.
VOD, TMDB, and watch folders
Movies, series, metadata, and watch folder ingestion are meant to stay in one managed workflow so catalog quality is visible and repeatable.
Adult flag and parental control posture
The adult marker is editorial and platform-controlled. It is designed to help player-side parental control where the downstream client supports those signals.
Why updates are part of the offer
panelX is positioned as maintained software, so updates, bug resolution, and product refinement stay part of the service relationship rather than stopping after the initial sale.
How support fits the client journey
Customers use panelX-branded pages for guidance and move into the client portal for structured support and subscription continuity. That keeps the public experience clean without exposing internal operations.
Migration from an existing panel or database
Migration is treated as a real transition project. Existing data, reseller structure, and inherited operational habits are taken into account instead of being ignored in favor of a clean-room fantasy.
Proxy workflows for reseller operations
Where licensed, reseller proxy workflows can support grouped line ownership, child reseller coverage, and more structured traffic handling inside the reseller layer.