On Premises

Taskforce.sh is also available On-Premises, so you can run the dashboard in your own infrastructure instead of using the hosted version at taskforce.sh. This is useful if your company policies do not allow your Redis instances, or the data in your queues, to be accessed from an external service, or if your Redis instances live in networks that cannot reach the internet at all.

The On-Premises version provides the same functionality as the hosted version, and the deployment supports unlimited connections and teams.

Choosing a deployment

Currently, there are two ways to run Taskforce.sh On-Premises:

• AWS Marketplace. If you are on AWS, you can launch Taskforce.sh as an AMI from the AWS Marketplace. The instance is configured through AWS Systems Manager, and upgrading is just a matter of deploying the latest AMI. Follow the AWS guide for all the steps.
• Docker image. The dashboard is also available as a Docker image that can run in any container platform, such as Kubernetes, ECS or a plain Docker host. The image is downloaded from our private registry, which requires an On-Premises license that you can get from your subscriptions page. See the Docker guide for details.

If you would like to try the On-Premises version before buying a license, please contact support.

What you need

Both deployments rely on some external services that you need to provide:

• A PostgreSQL instance for storing all the persisted data, such as users, connections and monitors.
• An Auth0 application for user authentication. The free plan is enough for most installations.
• A Mailgun account for sending team notifications and alert emails. The free plan is often enough.
• A domain with HTTPS, since Auth0 will not work over plain HTTP.

The Docker image also needs a Redis 7.0+ instance that the dashboard uses internally for monitoring. This is not the same as the Redis instances holding your queues, although you can use any Redis you like for it.

Connecting your queues

Once your instance is running, you add connections in the same way as in the hosted version, either as direct connections or with the Taskforce connector. When using the connector you need to point it to your own instance instead of taskforce.sh, as explained in Using the taskforce connector.