Feature Ideas

Rename domains for existing websites.

Provide 1-click hosting integration to connect WP sites with InstaWP. In first phase we will release integration with Runcloud, then followed by Gridpane, WPBolt, WPEngine & Cloudways.

Put a paywall infront of your templates and start making money. You will be able put a one-time or an ongoing fee to a template, if anyone buys your template, they get an InstaWP site!

Provide a Zapier app with actions. Actions Create Site Create Site from Template

Providing the ability to use xdebug would enable advanced debugging capabilities when trying to track down gnarly problems that customers are experiencing that are not reproducible in local dev environments.

A WordPress plugin for your Production sites in order to create 1-click staging sites on InstaWP

Email logs from your WordPress instances

I would love have the ability to set a custom 301 redirect target for expired sites (also for expired magic-login-links).

We use Active Campaign as our CRM. It would be useful to be able to add users, as well as tagging new & existing users or triggering events.

Sometimes when we move a client from InstaWP to our production service we aren't quite ready to nuke everything on InstaWP. I'd like to be able to suspend the site (or redirect it from the dashboard) without deleting it while we wait for it to expire.

If the templates had their own set of permissions they could be managed by other team members who are not admins. On a team where multiple people need to manage the same templates, it would be helpful and avoid the need to give everyone admin rights.

It would be great if the website owner could disable all installed plugins. If any unexpected errors occur, this setting will assist users in recovering the website.

There is an issue in InstaWP right now: When creating an instance using the API but there's no PR associated to it, and then I destroy it via INSTAWP_ACTION: destroy-site, it destroys all the instances from that template, instantly killing all the other tests I'm running at that moment. Maybe passing the instance URL when doing INSTAWP_ACTION: destroy-site can solve the issue.

I see this has been implemented: "- Added: Change Template PHP Version" However, I'd like to have a single Template with all of my configurations, and ask my potential customers what's their PHP version. Then I can create a testing site for them using their PHP version, which I select upon clicking on "Create Site from Template". This way, a single template is good for all customers, for all PHP versions. Otherwise, I need to clone a template just to change the PHP version, that's not ideal. Same for testing: if I want to run integration tests against PHP versions 7.1 ... 8.2, I'd need 6 templates, that is certainly not ideal. I'd rather have a single Template, and pass variable PHP_VERSION to the InstaWP API (when using InstaWP/wordpress-testing-automation)

I happen to manually go into a lot of instances and enable FTP/SSH to be able to access them. In my case, when using Deployments: https://docs.instawp.com/docs/deployments/add-deployment I’d love that if a deployment is generated from a PR, have SSH enabled on it by default, and in the automated message have a command that I can quickly copy to connect to the new instance via SSH, e.g: ssh hiniyonile5453@m-enforcer-wuka.instawp.xyz