Feature Ideas

Rename domains for existing websites.

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

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.

Email logs from your WordPress instances

When we create a new site, especially if it is a staging site, it would be very important to auutomatically set it to NOINDEX. Otherwise the SEO of the original website could be affected.

If you are setting up multiple sites generated from a template I need to connect to the site and check the WordPress title to know what it is, so it would be nice if I could leave a note in advance. Or it would be a nice feature to list WordPress site names, etc. from the database.

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

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.

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.

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

Right after creating a new site there is a "Your new WordPress wevsites is ready!" block which in the bottom right corner has a "Copy Link" button, next to the "Magic Link" button. This "Copy Link" button allows you to grab the magic login link for the site. Once this block is gone there is no other way to copy the magic login link for a running site. In the list of active sites on https://app.instawp.io/dashboard each site does have a "Auto Login" button, but you cannot copy the link. Either add a Copy Link or similar button in the list, or add the magic login link to the View Creds window.

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.

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)