In Review
48Under consideration
Add Integration: Fly.io
As a: DeployHQ user I want: to seamlessly integrate DeployHQ with Fly.io, so that: I can easily deploy and manage my applications on Fly.io directly from DeployHQ.
Allow website backups on DeployHQ dashboard
As a DeployHQ user, I want to be able to easily configure and schedule full directory backups of my server environments, so that I can quickly revert to a previous state if needed, without having to manually manage backups myself.
Add Social Logins (Google, Github, Bitbucket, etc)
As a DeployHQ user, I want to have the option to log in using my existing social accounts (Google, GitHub, Bitbucket, etc.), so that I can quickly and easily access my DeployHQ account without having to create and remember yet another password.
Allow to restore archived projects
As a Project Administrator, I want to be able to restore archived (deleted) projects so that I can recover accidentally deleted projects and their deployment history without having to recreate them from scratch.
Support ASIA Region
As a DeployHQ user in the Asia region,I want to have a DeployHQ server located in the Asia region, so that I can experience faster deployment speeds and reduced latency. Dependency on Katapult support (not available yet).
Support automatic deployments from branches or tags
As a developer using DeployHQ,I want to be able to deploy from specific branches or tags in my Git repository, so that I can easily manage different versions of my application and deploy them to production or staging environments as needed.
New Integration: Noibu
Notify Releases to Noibu, similar as we do with NewRelic
Retry deployments from the last completed step
As a engineer or user, I want to be able to retry a failed deployment from the last successful step, So that I can save time and effort by not having to redeploy all previous steps.
Automatic Tagged Release Deployments
To support better CI development flows, if a tagged release is created in Github (or other VC system) it would be great if this can then auto-deploy. For example I might have the following setup: dev.website.com = dev branch = auto-deploy when pushed staging.website.com = staging branch = auto-deploy when pushed website.com = v1.0.1 = auto-deploy when created
Automated Preview Environments for Pull Requests
As a Developer, I want my Pull Requests to automatically trigger deployments to unique, temporary preview environments (using the code from the associated branch), So that my team and I can thoroughly test and review the exact proposed changes in a live-like setting before merging them into the main codebase.
In Progress
Actively being built
No In Progress issues
Completed
59Recently shipped
ACL User managment , who can acess to config
Hi, we strongly need an options to give access to separate config files for a user In one project can be production and development config files, which we should separate access between of users
Allow deployment of just config files
Sometimes you need to update and redeploy a config file and doing a full deployment seems unnecessary.
Support Global SSH Keys
As a DeployHQ user, I want to manage my SSH keys globally across all my projects, so that I don't have to upload the same key to multiple projects.
Build configuration per server
Make build configuration configurable per server. At the moment it is annoying to deploy an updated version of an app to a staging site, as you need to change the build config for the whole project, which then blocks any deployments to the production site.
Add SSO (Google, Okta, etc)
As a DeployHQ user, I want to be able to log in to DeployHQ using Single Sign-On (SSO) with various identity providers (e.g., Google, Okta, etc.), so that I can simplify my login process and reduce the risk of credential breaches.
Support for global servers
As a DeployHQ user I would like to be able to manage servers in a global context, so they can be used across multiple projects, so that I can easily apply consistent settings for deployment and build processes.
Allow SSH-Only Deployments (without file transfer)
As a user of DeployHQ, I want to be able to execute SSH commands on my servers without transferring files, so that I can perform tasks like running scripts, checking system status, or configuring settings efficiently.
Add integration: AWS ElasticBeanstalk
As a DeployHQ user, I want to integrate DeployHQ with AWS ElasticBeanstalk, so that I can deploy my applications to ElasticBeanstalk environments directly from DeployHQ
Custom Server Environment Variables
It would be handy to securely create and store custom environment variables on a server basis to be used during SSH commands and Config files. We are currently restricted to only what is available: https://www.deployhq.com/support/projects/variables This would then avoid need to create individual config files per server. Instead, we only need one and ensure the environment variables are set. This is a pretty common setup in other CI/CD providers (ie: github, gitlab, bitbucket, etc)
Add Integration: Digital Ocean
As a DeployHQ user, I want to integrate Digital Ocean with DeployHQ, so that I can deploy my applications directly to Digital Ocean droplets from within DeployHQ.