1) Backups of server is a payed service. Totally fair, but it is not noted anywhere inside the platform portal. You have to dig like 3 articles deep to find out the actual costs for backup storage. It would be nice if in the server settings this was more transparent communicated.

2) Once you have multiple servers it is nearly impossible to find out what is actually charged per month for backup storage costs and what is droplet cost. Some reporting on this would be helpfull.

3) And last but not least, I think backup should be optional. I can easily create a custom script and cron job to create backups of applications myself to possibly a cheaper backup storage service. However, I must use the CloudWays backup service and I am forced to pay for this.

Please add geo detection capabilities into Varnish, this will accelerate use case scenarios where geo detection is essential.

For e.g. in WooCommerce, their current method to provide multi-currency that's compatible with cache is using Woocommerce based geo detection, which tends redirects the visitor 4 times to the correct URL of the page with the correct currency/tax displayed.

Other multi-currency plugins attempt improve this but their loading speeds are too slow, drastically affecting woocommerce store loading times, and making caching useless.

By having geo detection capabilities right in the server stack (Nginx or Varnish, which ever is hit first by visitors) we have opportunities to use this capability to serve the pre-cached store with the correct currencies.

For reference, this is one example of a Varnish configuration to link with a multi-currency plugin.

https://guides.wp-bullet.com/cache-woocommerce-currency-geoip-varnish-4-vmod/

Another with NGINX and various other caching plugins.
https://aelia.freshdesk.com/support/solutions/articles/3000042591-how-to-add-dynamic-caching-to-your-site?fref=gc&dti=962543703760049

The issue of multi-currency woocommerce store with caching issue is discussed here.
https://aelia.co/woocommerce-currency-switcher-cache-new-solutions/

Allow a way for a SINGLE person (and their email) to be associated as a TEAM MEMBER on more than one account.

At the moment, a person would need to create several different emails to be be a TEAM MEMBER on more than one account.

There should be a GENERAL ACCOUNT console (that doesn't require a hosting/server plan.... however it CAN support a purchased plan if desired) that is separate from any TEAM MEMBER access associations.
On the console you should be able to see all of the accounts you are associated as a TEAM MEMBER on... and access them from your own MAIN ACCOUNT.

The current option to add mailboxes from Rackspace is extremely limited.
The only way to order them, is via a small window and is very limited information.
I have no details at all about current mailboxes, quota usage etc...
Also, the only way to order mailboxes is by TYPING in the details in the window including the desired password for the mailbox???
Afterwards, I get a confirmation back from support with the password in the email.
It's completely unsafe to communicate about passwords this way.

And lastly, there is no control at all about the mailboxes.
I can't create extra alias, I can't activate forwarding, etc...
for each and every change we have to request via support and wait for them to fix it, while some things I can do very easy myself instantly.
I don't understand why there isn't a control panel to manage the mailboxes?

My suggestion is that all WordPress apps use the Woocommerce Varnish by default.

This way there's no risk of a user installing a normal WordPress app and later installing Woocommerce on it, only to find out that their cart is broken because of Varnish.

Here is why:

I found out that the WordPress app uses a unique Varnish and the Woocommerce app uses it's own unique Varnish.

I ran into a problem with a WordPress app that I later decided to install Woocommerce on. Once I did, the normal wp Varnish did not support Woocommerce and it broke my cart functionality. I had to make a new Woocommerce app and migrate my site over there so it could use the Woocommerce Varnish.

The support team told me that Woocommerce Varnish would also work for a plain WordPress app without Woocommerce.