We've recently updated our AI disclosure for AMP 3 development to include the use of Mythos for security testing.
You don't need us to tell you it has been a bloodbath this week with LLMs discovering or producing PoCs for all kinds of exploits, and AMP of course is installed on a large number of fairly powerful systems which makes it a really attractive target. So we're using the same kind of tooling to make sure not just AMP but the game servers running inside it don't become a vector.
We're committed to aggressive proactive testing before builds reach users to help keep you guys safe, rather than reacting to things after they happen.
On container-less systems, AMP 3 still isolates each game server process within its own user. So even if one was compromised, it wouldn't be able to affect anything else on the system. This applies on both Windows and Linux hosts.
We don't use PHP for any products we ship or systems we use. If you're using any legacy panels that still rely on PHP then AMP 3 is about to offer you an excellent upgrade path soon :)
Anything that can create standard Docker contains on your system has the equivalent of root access to your entire system and everything in it. This is part of why AMP uses either rootless Docker or Podman (which is always rootless)
If you're still using a panel that creates normal containers, AMP 3 has the ability to import from a variety of other server panels so you can level up your security.
P.s. It's also a good reason to make sure you're not using something vibe-coded that has de-facto root access to your system whose developer doesn't understand how it works ;)
One of the things we will never do is shoehorn unwanted AI features into our software just for the sake of it or push it onto users who don't want it.
If we ever do find a use for AI that actually adds value in some way to our software, it will be disabled by default, explicitly opt-in, and you will never be pestered or annoyed into turning it on.
If a feature can be implemented *without* using AI to do it, that will remain the preferred approach.
Apologies all, there was a minor issue with the new referrals system that meant some referrals weren't being counted. Anyone you referred can credit you retroactively by going to their account at https://t.co/Npxulfc5vj and giving it your link again so you get credit for it.
We've made a change to how CubeCoders accounts work that you may wish to review. We've introduced a new set of flags to let you control when you want to hear from us via email.
The defaults are as shown here - so transactional emails, security notifications and rewards/bonuses issued to your account. Sales and Offers and Product Notifications are disabled by default. If you'd like to change when you hear from us, you can change this at https://t.co/7Xd2s10C12
Psst: Turn that last one on if you want to be amongst the first hear about AMP 3!
One of the best overall design changes in AMP 3 is removing redundancies and duplications. Need to open a support ticket? You do that in *one* place regardless of whether it's with the system itself or a specific app. Permissions? All in one place, you don't need to go in to each apps own settings. Analytics? Same again - one big shared system that lets you filter by the app rather than requiring that you go to each one individually. Similarly there is *one* SFTP for each machine rather than needing one for each individual app. It addresses one of the biggest sets of issues with AMP 2 that made features harder to find than necessary.
AMP 3 is so well engineered that if you link two or more systems together, you can shut down AMPs core on one of them, and continue managing that systems running servers via the other installation seamlessly despite it being on another machine. There is no hierarchy making one system more important than another which gives it massive operational redundancy and safety. Even the schedule, logging, auditing and authentication are fully distributed. It's designed to keep functioning under extreme stress while still being fast, responsive, intuitive, and respectful of the value of your time.
We would like to make it very clear to our community that we will *never* charge a subscription for private use of AMP on your own systems. Only commercial users will ever pay that. We believe in the one-time payment model, and the idea that future **revenue is earned by providing value** - not by rent keeping for the sake of it when people get locked into a platform.
If we want more money from you, we have to show you something worth paying for rather than just taking advantage of it being work and effort to move to another platform.
We're going to work on bringing forward the AMP 3 release if we can. It's importing system can read in servers from other panels and keep their data, configuration, etc so that users affected by some of the recent news will have a safe, practical and economical migration path.