Just a suggestion for your marketing strategy and pricing team.
Rackspace provides a solid service including fast phone support and other benefits. While Cloudways (as a reseller) is not providing the same level of service as does Rackspace for their normal level of service and features yet charges and equal sum $2/email address.
This in actuality - as far as I can see at the moment - is a negative benefit for a Cloudways client.
Maybe the benefit of Cloudways Rackspace would be that it is a cost savings - Maybe providing something different - not less than - for example; maybe you could provide numerous email addresses for $2/mo and the current very light service via chat. That could be a value for someone like me who would not need much email support.
I learned of this because cloudways support sent me a link to view rackspace support to understand my possible issues. So at that point I noticed Rackspace's help and chat and phone.
So I called on the phone and got an instant answer of a real person. BUT he was not allowed to serve me since I got my Rackspace email from a secondary provider (Cloudways). Naturally, I was disappointed since I then realized I was receiving something less for the same price.
I think Cloudways is great and looking forward to more great economical and state of the art services.
I do not imagine that Cloudways would wish to appear a bit silly in their value offerings. So because I really like you all quite a bit , I have taken the time to explain that this type of marketing does not make good business sense.
It is quite important to make and demonstrate a clear value message.
The message could be more email for your money and enough support for the not so technically challenged.
Sincerely
Bob

The rackspace "add-on" is very missleading.

1st. It really isn't an add-on. An add-on suggests that it will be fully integrated in my Cloudways control panel and that I'll be able to manage my email configuration. An add-on in Cloudways sounds like an easier and better option than buying directly with rackspace because all the integration issues with Cloudways would be already solved, but that is not the case, in fact is the opposite. The add on is basically a "form" and everything has to be slowly done manually through tickets.

2nd. With the add-on we become second class rackspace accounts. We cannot access rackspace technical support to solve quickly and efficiently any issues with our mail server. They are the ones knowing their system and they are able to fix things directly. Instead we have to go through Cloudways support which usually is good for their own stuff, but are not as knowledgable for rackspace stuff.

3.- Buying directly from rackspace is 2$ per account, with cloudways is 1$ so "just" 1$ difference (in theory cost as I read in another post) but not having proper, efficient, knowledgable and fast support for rackspace issues is utterly not worth the 1$ difference.

4.- It is not possible to "upgrade" an account created through Cloudways to be a proper rackspace account with proper support from them. According to rackspace I would need to create a new account which means reconfiguring everything and migrating the emails (more inconvenience).

5.- When you buy the add-on it doesn't tell you clearly that support will be done only through Cloudways and that we will not have access to a rackspace control panel to manage our rackpace account.

So I recommed that you disable the rackspace "add-on" and instead just recommend customers to open a proper account directly with rackspace...

(The issue I have is that the IP we got assigned was already blacklisted so our emails are being rejected. With rackspace support they will rotate the IPs to a new one that is not blocked, but with Cloudways support it has been a few hours already and still blocked and unable to send emails).

I am currently in the process of moving my sites from cPanel based hosting env. to Vultr, DO, and Linode.

I think everything you guys offer at CW is pretty great, except you folks do not provide us with root access. That's a bummer!

I think you folks should create a new package for DevOps or just for developers who are interested in having the root access. This package will offer everything your platform offers, the custom panel, staging area, security management and stuff but it would also provide root access.

Devs would know what they are doing. You'll be able to contain more folks in this package because you won't be restricting the root access.

Since you do NOT own the hosting stack, that means the only bottleneck here is your team, which is not offering the root access to keep things secure or whatever the reason there is. I understand that, but root access means more transparency to me. It also provides me with added advantages like for example I migrated, sorted, analysed 200GBs of data from my old host to Dropbox within 4 hours at Vultr. Had I not have root access, I would not have been able to do that.

Hi,

I am the developer of WHMCS Digitalocean reseller module and WHMCS Serverpilot reseller module. I am interested in your service and found you are now providing API's to manage your service. So it peaks my interest to develop a module for whmcs similar to my previous modules.

Before that, i have some questions to get answers?

1. Is it possible to set hostname default to clients domain name or something else instead of app-xxxxx.cloudwaysapps.com? So that it makes the module some what white labeled.




2. is it possible to get developer account/server to test my module in live?




3. Do you guys provide support during my development?

you can find my modules @ https://my.dropacloud.com/cart.php
I am waiting for your reply.

Thank you.