Why panelX
A modern control plane with disciplined internals.
panelX is not a skin over legacy workflows. It is being shaped as a maintained control plane for live delivery, reseller growth, edge operations, customer continuity, and migration from inherited platforms.
01
Node 24 runtime foundation
The application layer now sits on a modern LTS runtime, so install, update, artifact, and service execution all move on a cleaner long-term base.
02
Orchestrator-led operations
Critical operational flows are being pulled into a visible orchestrator layer, giving operators clearer recovery, update, and runtime attention surfaces.
03
Shared contracts and modular domains
Shared route contracts, schema domains, and storage facades reduce hidden drift between client, server, reseller, and runtime layers.
04
Edge-ready delivery and customer continuity
Main and edge rollout paths, customer portal access, support, and migration onboarding are kept explicit instead of being improvised across disconnected tools.
Operating model
Commercial posture without legacy drift.
panelX is being positioned as maintained infrastructure software: visible roadmap, guided migrations, direct support, a separate customer portal, and licensing and billing layers shaped for controlled commercial rollout.
Product discipline
A rollout model built around continuity, not just first delivery.
The platform is being refined around real operator pressure points: update trust, reseller autonomy, VOD presentation, bug response, migration control, and infrastructure growth from VPS to larger dedicated footprints.
Constant updates
Commercial customers are not left on abandoned builds. Improvements continue after deployment.
Bug resolution
Operational issues are treated as product work, not as tickets that disappear into backlog silence.
Migration support
Legacy structures and inherited databases are handled as transition projects, not as blockers.
Scalable path
Start lean, then move the same architecture toward more serious infrastructure when the business needs it.
The commercial surface is being shaped so plans, add-ons, billing, support, and activation move together instead of living in separate silos.
Early customers can expect real human involvement around deployment, rollout refinement, issue resolution, and roadmap evolution.
Commercial subscriptions
Clear plans for growth, migration, and reseller scale.
The commercial structure is intentionally readable: one main server per plan, a defined load balancer envelope, and a clear path from lean rollout to full enterprise plugin coverage. Annual subscriptions receive a 20% discount.
S
Started
$120/month with 1 main server and 1 load balancer for controlled early-stage deployment.
ST
Standard
$180/month with 1 main server and 5 load balancers for a realistic operational baseline.
P
Professional
$250/month with 1 main server, 30 load balancers, Proxy, and Reseller Panel Proxy included.
E
Enterprise
$400/month with 1 main server, 50 load balancers, and the full current plugin envelope.
Ideal for operators who want to start quickly and shape the deployment in short iterations.
Suited for teams that want steadier forecasting without moving immediately to annual commitment.
For operators who already know the platform direction and want the cleanest long-term billing posture.
The customer starts from a branded billing order flow, not an exposed internal backoffice.
Billing lives in a dedicated portal so approvals, invoices, renewals, and payment visibility stay clean.
Customers move through the customer portal for account access, subscription continuity, and structured support handling.
Main IP authorization and paid add-ons can then flow into the licensing engine with the correct entitlement profile.
Knowledge Base
Documentation that looks like part of the product.
The public panelX knowledge base is now designed as a real navigation layer for onboarding, licensing, reseller operations, billing flow, updates, and VOD guidance. It is meant to support sales conversations, customer self-service, and structured rollout work without exposing internal-only tooling.
Operator-facing articles
Clear guidance around deployment, billing flow, activation, reseller workflows, and maintenance.
Searchable structure
Categories and featured articles are grouped to feel like a maintained knowledge surface, not a notes page.
Public navigation
Support content without exposing the internal desk.
Customers stay on branded panelX pages for knowledge and ticket access, while the internal helpdesk remains reserved to the assistance team.
Admin experience
A real command center for operators.
The admin side is built for teams keeping service moving: orchestrated stream control, Node 24 update management, server visibility, catalog design, watch folders, user operations, customer-facing commerce, and infrastructure oversight.
Executive dashboard
Operations start from a high-signal surface.
The admin dashboard gives fast visibility over platform activity, infrastructure posture, growth signals, and operating priorities.
Live streams
Manage channel operations with clarity.
Stream inventory, operational status, source control, routing choices, and editorial structure live in one workflow.
Server fleet
Keep infrastructure readable.
Server visibility is designed for growth, from main nodes to edge expansion and future dedicated infrastructure upgrades.
Update control
Roll out the platform without guessing.
Version checks, artifact flow, Node 24 runtime alignment, and load balancer synchronization stay visible from the admin surface instead of hiding inside shell history.
External contracts
Expose structured external flows without backoffice leakage.
Business-facing API surfaces can be presented as deliberate product capabilities instead of a pile of hidden internal endpoints and ad-hoc scripts.
Open orchestrator alerts, update readiness, stream monitoring, and server visibility are being converged into a clearer operating model for real production hours.
- Admin alert surfaces
- Runtime and edge attention
- Cleaner recovery signals
Schema domains, route contracts, and storage domains are being split into maintainable seams so the platform can grow without hidden drift between panels and runtime.
- Shared route coverage
- Schema and storage seams
- Lower maintenance drag
The public site, customer portal, knowledge base, support handling, and migration guidance are being shaped as one journey instead of unrelated touchpoints.
- Customer portal continuity
- Guided rollout language
- Migration-first posture
Movies
Catalog pages built to sell confidence.
Movie views are clean, rich, and visual enough to demonstrate a serious VOD operation to a partner, distributor, or prospective reseller.
Series studio
Series workflows stay inside the platform.
Series management remains operationally coherent, reducing manual sprawl and giving teams one place to curate the episodic catalog.
Reseller workspace
Reseller tools that go beyond basic line resale.
panelX includes a reseller environment meant to support real business operations: line creation, package selection, sub-reseller hierarchy, group authority, stream proxy workflows, tickets, and day-to-day management.
Reseller dashboard
Readable by default, even at scale.
The reseller dashboard is designed to be commercial, understandable, and ready for operators who need to delegate without losing control.
Line operations
Create, inspect, and service lines from a reseller surface.
Line workflows are part of the reseller workspace itself instead of being hidden behind an admin-only bottleneck.
Sub-resellers
Growth can be structured hierarchically.
Sub-reseller creation and management keep distribution logic organized for teams expanding in layers.
Resellers can work with package structure and line flows in a way that supports real selling operations, not just raw access toggles.
- Package-oriented selling flow
- Cleaner customer handoff
- Better reseller autonomy
Proxy tooling is positioned as part of a larger commercial and operational model for resellers, not as an isolated technical afterthought.
- Reseller-facing proxy visibility
- Operational grouping logic
- Expansion path for advanced setups
Support requests and day-to-day operational interactions can stay inside the reseller surface, helping teams respond faster and keep context.
- Support desk workflow
- Cleaner escalation paths
- Lower operational friction
Packages
Commercial packaging that feels built for resellers.
Reseller-facing package selection is presented in a way that supports sales workflows rather than looking like a developer-only configuration panel.
Stream proxy workspace
Proxy flows stay readable for delegated teams.
Reseller-facing stream proxy management is presented as a real workspace, with routing groups and delegated control instead of a buried technical screen.
Faroe Islands footprint
A quieter operational setting for partner meetings and rollout work.
panelX commercial and technical coordination can also reference a Faroe Islands footprint for quieter working sessions, partner meetings, and planning away from the usual saturated city setting. We keep the presentation directional, not overly specific.
The idea is not to sell a postcard. It is to show that the panelX project can be presented from credible, quieter locations that fit a serious commercial tone and a long-term infrastructure mindset.
- Private rollout discussions
- Smaller partner meetings
- Operational planning outside the usual city rhythm
The Faroe Islands mention is used to reinforce the idea of a measured, maintained software business with room for focused product work, support coordination, and enterprise-grade planning.
Klaksvik
Street-level setting for quieter regional meetings.
A grounded Faroe Islands backdrop that fits the panelX tone better than a loud metropolitan cliché.
Hov, Suduroy
A calmer route for planning, not just presentation.
Used here to signal a more discreet operational footprint without exposing precise addresses or internal logistics.
Operations, updates, support
The product is meant to keep moving after deployment.
panelX is being developed with a long-term operational mindset: improve the software, resolve bugs quickly, support migrations, protect uptime, and keep the stack ready for larger infrastructure when the business grows.
Release discipline
Frequent improvements are part of the offer.
The platform is being shaped through active iteration. That means bug fixes, UI refinements, operational hardening, licensing improvements, delivery fixes, and reseller evolution are treated as ongoing product work rather than optional extras.
Constant updates
Ongoing releases keep the product aligned with real operator needs.
Bug resolution
Operational issues are tracked and resolved with a product-maintenance mindset.
Dedicated assistance
Support is positioned as part of the service experience, not an afterthought.
Migration projects
Legacy panel and database transitions can be addressed as structured onboarding work.
Technology posture
Built to start lean and scale cleanly.
panelX is suited for VPS deployment today and for dedicated infrastructure tomorrow. The stack is being shaped so components can evolve without forcing a total rebuild when an operator moves into a more enterprise environment.
Operators can shape a real catalog experience and keep the workflow closer to a managed platform than to manual media handling.
The commercial layer and the delivery layer are meant to work together, reducing operational fragmentation.
The architecture can evolve toward more advanced infrastructure, dedicated hardware, and stronger control planes as the business grows.
Existing operator data should not trap the business in the old stack. panelX is positioned for guided migration from legacy panels and inherited databases.
The software is being refined to stay usable during real operating hours, not just in static product screenshots.
This is meant to become a serious operational product, with room for enterprise deployments, stronger infrastructure, and continuous roadmap work.
Legal clarity
Software platform only.
panelX is offered as software and operational tooling only. We do not sell content, channels, movies, series, or third-party media libraries. Commercial discussions cover software deployment, updates, migration work, reseller structure, support, and infrastructure evolution.
Commercial expansion
Structured add-ons are available.
Plan growth can be handled cleanly with named license add-ons, including Proxy, Reseller Proxy, and AutoBlock at $22 each, plus extra load balancer capacity at $18, all aligned with the selected billing cadence.
Customer journey
One clear route for commercial contact, customer portal, support, and self-service knowledge.
panelX now has separate public and operational entry points. This keeps pre-sales, customer portal access, support, and knowledge access organized without exposing licensing internals or sensitive infrastructure controls.
Use the main site for discovery, migration discussions, and structured commercial onboarding before any subscription is activated.
info@panelx.softwareApproved customers can be routed into the customer portal for invoices, subscriptions, renewals, and the financial side of their account.
Customer portalProduct assistance, rollout issues, renewals, and customer follow-up stay tied to the customer portal instead of being scattered across separate public tools.
Client portalPublic-facing guidance can live in a proper panelX knowledge base, helping prospects and customers orient themselves before a ticket is even opened.
Knowledge baseNext step
Plan your rollout, migration, or reseller expansion.
This contact block is ready to be connected to your preferred workflow. It can be routed to email, CRM, ticketing, or the commercial system you choose later.
Engagement model
What the first conversation can cover.
The early phase can focus on migration feasibility, infrastructure sizing, reseller structure, VOD goals, operational pain points, and the right deployment path for where your business is today.
Contact form
Start the conversation.
This form routes commercial requests directly to the panelX team. Pre-sales starts on the main site, while subscriptions and ongoing customer support stay on the private client portal.