Panel script

Panel script is the off-the-shelf software a panel runs, which is why many panels share the same order form, field names, dashboard layout and API conventions.

The script supplies the whole storefront: user accounts, a deposit page wired to payment processors, a service list with rates and limits, provider connections that forward orders upstream, the order statuses, a ticket system and an API endpoint for resellers. An operator licenses it, points a domain at it, connects at least one provider and starts selling. That is why so many panels feel identical to use, and why an API written against one panel usually works against another with small adjustments.

The shared software explains several things buyers notice. Status names, the mass order format and the refill button behave the same way across unrelated sites because the same code draws them. Service descriptions repeat word for word because they were imported through an API rather than written. A site that looks polished tells you only that the operator paid for a licence and a template.

It also sets the limits of what a panel can do for you. Features the script does not include, such as a particular refund flow or a report you want, are usually unavailable rather than pending. And because the software ships with provider connections built in, the path of least resistance for a new operator is to resell someone else's supply, which is what most of them do.

Software without supply

A script buys a shopfront and no supply. It produces a website that can take payments and forward orders, nothing more. The accounts, the delivery, the speed and the drops all come from whichever provider the operator connects, so two panels running the same software can behave completely differently, and one panel can change its behaviour overnight by changing that connection.