Missing a control panel option, a server location, a payment method or an application you rely on? Tell us. Customer requests decide most of what we ship, and every one is read by the people who build it.
No black hole, no automated reply that goes nowhere.
Requests land with the engineers who run the platform, not in a marketing inbox. We read every one, including the short ones.
A request from one customer is a data point. The same request from twenty is a priority. Grouping tells us which is which.
Some things are a setting we can switch on the same week. Others need a new server, a licence, or a change from our upstream provider.
If we build it, you hear first. If we decide not to, you still get an answer explaining why rather than silence.
No. If something is broken, open a support ticket instead so it reaches an engineer straight away. This form is for things that are missing rather than things that are failing.
Yes. We reply to the email address you give, whether the answer is that we shipped it, that it is on the list, or that we decided against it. You will not be left guessing.
It depends entirely on what it is. Enabling a PHP module or a control panel option can happen within days. A new server location or a new payment gateway takes months, because it involves contracts, hardware and testing.
No. Requests from people who are not customers yet are just as welcome, and often tell us why someone chose another host.
Yes, and this is one of the most useful requests we get. Tell us the application name and roughly what you would use it for, so we can check licensing and whether it runs on our platform.
If a service is down or misbehaving, do not use this form. Open a ticket and an engineer will pick it up straight away, 24/7.
