been testing out this panel for a couple of weeks.. just to see what it's got..

there's some nice features... i like being able to run incremental backups, and especially run them several times a day.
most panels offer at most a full daily backup
moving sites between servers.. this panel provides the easiest method i've seen yet.
easily switch a webserver between apache/nginx/ls/ols. nice. not seen this anywhere else that doesn't require a lot of work.
the interface is modern looking, nice and clean.

some bits that could be improved a little...
the 'your account setup' banner.. can this be permanently disabled, even when all 7 steps are done, and i've marked all as completed, the next time i login, there it is again.. that's ok if there are steps left, but if i've marked them all as completed i never want to see this banner again. it's a very minor issue, but it is annoying.

the dns for service websites..
when setting up a hosting system, i'll have a domain, mydomain.com, most likely i'll have a website on (www.)mydomain.com, and have the service websites on mypanel.mydomain.com, dbadmin.mydomain.com, and webmail.mydomain.com
i'd expect the A records for all these to be in the mydomain.com dns zone, not for each subdomain have it's own dns zone.
In all the years i've used dns, i've never seen it actually done this way.. it's confusing, but the dns spec does allow for this, so ok.. i still think it would be better all in a single zone for the main domain, but i can live with it as it is.
but to also create the imap/pop/smtp cnames pointing to mail.<subdomain>.mydomain.com, that's just wrong to me.. if they're going to exist (personally, i don't think they should exist), but i they do they should point directly to mail.mydomain.com

also, it took a while, as a new user to locate where the dns records are set, under websites - <website> - domains is not obvious.. just does not seem the right place to me.

in my opinion, websites, emails, dns, and domains should be listed and be able to work completely separately.
a customer can own a domain and not bother with website, dns, or email, just leave it parked.
or have a domain and just use the dns service, no website or email, or have the site/mail hosted elsewhere.
or a customer might just want email hosting ..
it shouldn't be required that the system creates a website.
domain ownership, dns, email and website are separate services, they can all be included in one package, but it should also be possible to create a package that only includes any one (or more) of those services.

also, for dns.. if i have a control panel server, two separate dns servers, and multiple webservers (not running dns).
then the dns zones should exist, in their entirety, on the dns servers. if one of the webservers happens to be offline for some reason, it should not be impossible to edit the dns records for a domain whose website is on that webserver from the panel interface. dns record editing should never be reliant on the state of that domains webserver