Skip to content Got questions? We’ve got answers — fast, clear, and straight to the point.
It automates the initial WordPress setup in one go: cleans up default content, applies common settings (like permalinks and comment preferences), and installs your selected theme and plugins. You save the configuration as a “recipe” so every new site starts consistently.
A recipe is your saved setup: cleanup choices, settings, theme, and plugins. Build it in the admin, click Deploy to apply it, then export it to JSON for reuse on other sites. Importing that JSON on a new site instantly loads the same configuration.
The batch task engine is designed to be reliable, but we recommend using it on a fresh install or after taking a backup. The plugin skips items that are already installed or configured, minimizing disruption while keeping deployments fast.
The free version ships with a curated, stable list of popular developer themes and plugins so you can get moving quickly. You can select from those to bulk install during deployment.
Export creates a small JSON file containing your recipe. Import reads that file and restores the saved selections into the builder. The import is security-checked and size-limited, and only site admins can use it.
It’s optimized for single-site installs for now. Some actions may partially work on sub-sites, but full Multisite support is not guaranteed yet.
Tasks are idempotent where possible: duplicates are skipped and reported in the progress log. You won’t end up with duplicates of the same plugin or setting.
The queue runs task-by-task over admin-ajax, which helps avoid timeouts. On slower hosts or with many installs, it might take longer—your progress log will keep you informed.
Yes. Everything the recipe changed (installed plugins, theme, and WordPress settings) remains in place; the plugin doesn’t auto‑roll back.
Live plugin/theme search, premium ZIP installs (plugins and themes), header/footer scripts insertion, content protection for visitors, and a hardened task engine with better auto-recovery.
Upload your premium ZIPs in the recipe builder. During deployment they’re installed early—before potentially “noisy” operations—so detection and activation are reliable.
Your server’s upload_max_filesize/post_max_size apply to ZIP uploads, and PHP max_execution_time can affect very large installs. The UI surfaces errors; consider doing it separately, if you deploy large archives.
Yes. Add analytics, tag-verification, or other snippets. They’re output in wp_head/wp_footer with default priority 10. Use responsibly, as scripts run site-wide.
It optionally disables right-click, text selection, and certain shortcuts for visitors. Admins with manage_options are not affected, and the logic only runs on the front-end.
The engine guards risky steps and captures unexpected output. The log clearly marks warnings and you can choose to skip and continue. Most deployments complete without intervention.
Yes. Recipes can include both curated installs and premium ZIPs, plus header/footer scripts and content protection. The deployer automatically sequences the tasks for a smooth run.
Only admins with the security nonce (manage_options) can run deployment, import/export, or upload premium ZIPs.
Yes. Unless you use content protection/header-footer scripts. Other than that, everything the recipe changed (installed plugins, theme, and wordPress settings) remains in place.
But your header/footer scripts and content protection stop immediately because the Pro plugin (and its saved recipe) are removed on uninstall.
Optimized by Seraphinite Accelerator