Feature Ideas

Please consider doing a hosting partnership with xCloud. They have some funding from the Fluent team and they provide reasonable pricing for their managed and unmanaged plans. They seem like a much better Cloudways alternative. Thanks. https://xcloud.host/

Allow users to connect their plugin & theme license for 1-click activation on sites they are creating on InstaWP or migrating to a hosting provider.

Provide an option to take automated daily or weekly backups for InstaWP sites, this will help users recover sites if something goes wrong. Also an option to limit the automated backups to last X times.

We are working on a new version of WaaS portal which will allow end-users to manage their websites, view a list of websites they have purchased, buy more etc.

Please explore a partnership with Gridpane. They also have funding from Automattic and are much more established than a platform like ServerAvatar. https://gridpane.com/

At present the template selection page isn't white labelled but is being considered. You can integrate the page using an iFrame. One thing I would be grateful for consideration is the following: Using the root domain for WaaS means that subdomains are no longer accessible by the client. As the nameservers are under the control of InstaWP via AWS would it be possible to add a custom subdomain like 'my.example.com' or 'clients.example.com' using the WaaS domain for the template selection page?

Ability to set a standard/global WordPress admin email address for WordPress installs I have a specific dev email address for staging/maintenance/website development. InstaWP uses the email address linked to my InstaWP account as the standard WP admin email address which is not preferred. Ability to change the WordPress admin email address Now we aren't able to receive the conformation email when changing the WP admin email address (a workaround is using a plugin but it would be nice if we can change the WP admins email without adding plugins).

When you create a staging site from a live site, it is not possible to push the changes in files and/or database back to the live site (unless you use 2 way sync, which works on "content" level). We will create a functionality which will help push files and/or db (similar to WP Migrate) from and to staging sites <> live sites.

If I'm selling a template to my users I would like to be able to update the main template then push these updates to everyone who bought my template without overwriting their content. This is helpful for adding features and content to end users.

I would like to be able to map domains via an API call. I have customers for whom I create staging/live websites and they then map the domain themselves. And I would like to do this via my own app/website via API. I know that Cloudways, for example, offers something like this: https://developers.cloudways.com/docs/#!/AppManagementApi#updateAppAliases It would save me a lot of time if this were also possible via the InstaWP API.

We will auto create a quick staging site of your main website, perform core, themes and plugin updates and compare the two sites. If everything is ok, we will update the live site for you.

If you enter an existing or reserved site name, then the modal closes and gives an error as attached - Installation Failed! All good, but clicking on add new site, then one needs to select any plugins they have already selected before again. So maybe a possibility to check name availability when entered, or open modal again and give error within that?

Monitor uptime of a connected site by pinging the site and making sure its up. Get alerts when the site is down.

Dear Team, I’ve noticed an intermittent issue occurring during the deployment of multiple sites, particularly when creating a large number of sites from new or existing templates. We occasionally encounter a 439 error (i hope I remembered this correctly), which seems to be triggered by anti-spam protection measures on your end. To streamline our workflow and minimize interruptions, I’d like to propose the following: IP Whitelisting: Could you provide a way to whitelist specific IP addresses? This would help bypass the anti-spam triggers for trusted sources like ours. Improved Anti-Spam Logic: Alternatively, adjusting the anti-spam thresholds to account for manual, non-automated processes might alleviate this issue. For example, allowing higher activity rates from the same IP within a short timeframe. Our site deployment process is entirely manual, and there’s no automation involved. Currently, creating more than 5 sites in quick succession often results in the error (can be reproduced in some cases with less), requiring us to clear caches, log out, and log back in to proceed. This adds unnecessary time and effort to the workflow. Anything to better assist with this use case is highly appreciated. Thank you

Hello team! In the same way the site files permissions can be changed via InstaWP editor, I wanted to ask if you can also do the same for Folders. right now, If i hit properties there are no such options for folders/directories. This is a helpful improvement, which will allow us to not require FTP login to do this via other third party. Reference: https://gyazo.com/5ed4cc3afec58a0f441bd6567778ed44