Interesting, I didn't realize that Ajenti charges for commercial licensing of their web hosting addon.
It's on github separately but without a license: https://github.com/Eugeny/ajenti-v
Can't be sure this could be treated as an official statement, but https://github.com/Eugeny/ajenti-v/blob/efcee75286418fbbd25e... has a mention of LGPLv3.
If that's real terms the software's distributed under and not some mistake, then it's a proper Free Software project and I don't see any reason why one can't or won't use AGPL/LGPL software commercially. Adding any "secret sauce" seems nearly pointless for web hosting solutions, and even if that's truly necessary it probably could be easily hidden beneath "xGPL software merely writes a config file, and doesn't link with the proprietary bits" waiver.
We've recently undergone transition from an invalid combination of LGPL + custom clauses to dual-licensing under AGPL and proprietary. I actually forgot to replace the license mention in this buildscript, thank you!
Looking at examples like http://support.ajenti.org/topic/403351-setting-up-a-python-w... it seems that the panel is very opinionated on how to set up things. There are myriad of ways of setting up Django website, so I guess, it would be a significantly improvement if docs would explain what exactly goes on behind the scenes when the configuration is applied. Or maybe I just looked at the wrong place and missed those details.
And certainly needs proper licensing terms explained. "License not required" is very bad phrasing for everyone conscious about the matter - when taken literally it reads as "the software can't be (legally) used" in many jurisdictions. If I got it right, Ajenti seems¹ to be available under AGPLv3, so that's what the site should proudly tell.
___
¹) https://github.com/Eugeny/ajenti/blob/master/docs/LICENSE