Feature Ideas

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.

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.

Exporting static .zip for sites hosted on InstaWP.

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.

Provide option in wordpress plugin to let people make custom name instead of random name for their staging so it's more visual in instawp dashboard.

Context: "View logs" pop-up of each website. Idea: Having two more buttons on the debug.log of each site - CLEAR and DELETE logs. CLEAR button - will only clear the current contents of the logs (visually), so that you can continue testing and therefore, generating new logs, and have an easy way of capturing ONLY each test/scenario's logs generated, while keeping the entire full log in the original /wp-content/debug.log file for later usage. DELETE logs button - this, will of course, simply delete all logs (including the debug.log file) , which of course will then show up again if it's generated and so on (this is what happens now, but I am using manual labor to go into "Code Editor", surf on /wp-content/ and manually remove debug.log each time, which is a bit frustrating.

Many plugins allow license activation in wp-config. This saves time for the developer and is more secure than adding a license to the database, and preferable when possible when working on client sites. It would be useful to allow a code snippet to be auto inserted into wp-config in some way, either as part of a template or in another way in the InstaWP interface, that contains the custom code I use to activate some plugins. I would have this snippet already written and would just need a way to add it, ideally in some automated way.

Enable users to upload and deploy WordPress zip plugins across all managed sites directly from the InstaWP dashboard. Key Features: Centralized plugin upload and deployment. Bulk installation across multiple sites in one action. Ensure consistent plugin versions across all sites. Save time by eliminating the need for individual site logins. Example: I wanted to add new CommandUI plugin to all sites, but had to open all sites individually and upload zip plugin.

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.

Problem: I have 5 sites with a random name that were created a week ago. Now I don't remember why each one was created. Solutoin: A description field below the URL. I could explain the purpose of a site like "Testing Woo shipping options" or "Testing theme update".

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.

Simple brochure sites are primarily static, and don't need dynamic functions. Most of them require only a contact form, which can be taken care of by a third-party service. For these types of sites, an option to completely lock both the database and the file system would minimize maintenance and prevent security issues altogether, bringing complete peace of mind for clients and developers. Rocket.net implemented this feature recently, and it works well.

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.