Deploy+: deployments from GitHub, GitLab, Bitbucket or your own Git
Deploy+ is no longer limited to GitHub. You can now connect repositories from GitHub, GitLab, Bitbucket, Gitea, Forgejo or any Git server, including self-hosted ones, and keep the same zero-downtime deployment, automatic webhooks and one-click rollback.
Connect a repository in three steps
The new wizard identifies the provider from the URL, explains which credential it needs and checks access before saving anything. Then you choose the branch and the publish folder, review a command template and decide whether each push should be deployed automatically.
Each provider has its own way of handling authentication and webhooks. Deploy+ sets up the right one for GitHub, GitLab, Bitbucket and Gitea or Forgejo, while a generic Git repository can be deployed manually or through a signed webhook.
A new version, without leaving the site half-done
Each deployment is prepared in a new folder. The system clones the repository, links the shared files, runs the build commands and only publishes the version once every step has finished successfully, so a failed download or build never replaces the site that was already working.
You can define commands such as composer install or npm run build, and keep the .env, upload folders and any other path that must persist between versions. The interface shows progress, the time taken by each step and a practical explanation when it recognises the error.
History and rollback
Every release is recorded in a history with the branch, commit, what triggered the deployment, its duration and the result. If a new version has a problem, you can go back to a previous one without cloning and building again, because the latest releases are kept ready to activate.
Connected repositories are also available in the accounts of multi-account plans, with the deployment running on the server and user that belong to that account.
Separate credentials and webhooks
When you change provider, host or repository, Deploy+ does not reuse the previous credential or secret. URLs containing credentials, private addresses or invalid targets are rejected, and webhooks renew their secret when the repository changes.
Deploy+ is available on all hosting plans at no extra cost, from the service page under "Web and applications / Deploy+". The setup and usage manual explains the full process, scripts, shared paths and rollback.