In Review

In Progress

Completed

Main Roadmap

As a: DeployHQ user I want: to seamlessly integrate DeployHQ with <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Fly.io">Fly.io</a>, so that: I can easily deploy and manage my applications on <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://Fly.io">Fly.io</a> directly from DeployHQ.

Add Integration: Fly.io

Facundo@DHQ

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.

Allow website backups on DeployHQ dashboard

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.

Add Social Logins (Google, Github, Bitbucket, etc)

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.

Allow to restore archived projects

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 ASIA Region

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.

Support automatic deployments from branches or tags

Notify Releases to Noibu, similar as we do with NewRelic

New Integration: Noibu

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.

Retry deployments from the last completed step

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:<ol><li>dev.website.com = dev branch = auto-deploy when pushed</li><li><a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://staging.website.com">staging.website.com</a> = staging branch = auto-deploy when pushed</li><li><a target="_blank" rel="noopener noreferrer nofollow" class="link" href="http://website.com">website.com</a> = v1.0.1 = auto-deploy when created</li></ol>

Automatic Tagged Release Deployments

Tom Clarke

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.

Automated Preview Environments for Pull Requests

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

ACL User managment , who can acess to config

Admin TFTC

Sometimes you need to update and redeploy a config file and doing a full deployment seems unnecessary.

Allow deployment of just config files

Pete Heaney

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.

Support Global SSH Keys

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.

Build configuration per server

Matty Forth

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.

Add SSO (Google, Okta, etc)

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.

Support for global servers

Robert Venning

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.

Allow SSH-Only Deployments (without file transfer)

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

Add integration: AWS ElasticBeanstalk

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: <a target="_blank" rel="noopener noreferrer nofollow" class="link" href="https://www.deployhq.com/support/projects/variables">https://www.deployhq.com/support/projects/variables</a> 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)

Custom Server Environment Variables

David Burleson

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.