A Perfect Panel Alternative With No Monthly Fee

Perfect Panel is a serious engine in this market - plenty of panels run on it and it does the job. Its problem is not technical, it is the billing model. The subscription starts at roughly $50 a month and is unrelated to how many orders the panel processed. The invoice is identical in a month when everything went well and in a month when your customers were on holiday.

For a young panel that hurts most. The first months go on advertising, filling the catalogue and finding an audience, which means order counts are low by definition. A flat subscription during that period behaves like a tax on trying: you have earned nothing yet and already owe.

We built the tariff from the opposite end. What counts is orders created during the month, per panel, and only those routed to third-party providers. Up to 100 such orders a month costs nothing, always. Above that the plan is selected by volume automatically - and steps back down just as automatically when order counts fall, all the way to free. Orders the panel fulfils through our own provider, Heroverin SMM, are not billed at all: buy services from us and the panel stays free at any volume.

This is worth knowing in two situations: when you are sizing up someone else's panel and want to know what it is built on, and when a contractor offers you "our own development" while actually reselling an off-the-shelf engine. The signals are public - nothing needs to be hacked, you only look at what the site serves.

Assets from their CDN. The most reliable tell. Styles and scripts load from one of two hosts: cdnfiles.perfectpanel.com or storage.perfectcdn.com. It is the same engine behind both - the path structure is identical, with /global/ and /libs/ directories plus a six-character folder belonging to that specific panel, such as 2105na. That folder is what distinguishes one panel from another.

The /example.txt file. A generated sample of their API wrapper: a PHP class with the API address already filled in for the panel's own domain, served straight to the browser. This one catches panels that serve assets from their own domain and therefore leave no CDN trace.

Yii traces. Weaker, and proof of nothing on their own, but they reinforce the first two: a _csrf cookie in PHP-serialised form, a guest_user_first_visit cookie, and a non-standard X-Query-Count response header.

One thing that is not a signal: nameservers on cloudns.net. The same ClouDNS sits in front of panels with no connection to Perfect Panel, so it will not carry a conclusion by itself.