Self-hosted deployment platform

Deploy Docker apps to your own servers.

worqer.app gives developers one dashboard for Docker Compose and Dockerfile deployments without giving up control of their infrastructure. Connect a remote worker, choose a Git repository, deploy, inspect logs, run commands, and publish the service when it is ready.

Get startedRead the docs
Docker ComposeDockerfileRemote workersPublic URLs
Docker Hub worker image preview

Live product tour

Watch the workspace come online in seconds.

A lightweight animated walkthrough shows the moment a worker is claimed, a repository launches, and the service becomes reachable.

WorkersBring capacity online wherever Docker runs, then assign it to the right people.
JobsDeployments become visible work instead of hidden terminal sessions.
SecretsTeams can collaborate without passing tokens around in chat.

Launch from Git

Move from repository URL to running service with a guided path for branches, build settings, environment values, and target workers.

Use the machines you trust

Keep execution on VPS hosts, office machines, or lab boxes while the panel gives you status, capacity, runtime details, and cleanup controls.

Share without chaos

Give teammates exactly what they need to deploy: the repo, the credential, the worker, or the whole workspace surface.

From idea to live service

A cleaner way to run the deployment loop.

Each action becomes a trackable job with a worker, status, owner, and timestamp, so releases feel coordinated instead of improvised.

01PrepareConnect code, credentials, runtime settings, and the worker that should own the deployment.
02LaunchRun Compose or Dockerfile flows with the same repeatable controls every time.
03OperateManage containers, commands, restarts, logs, and service state from one surface.
04ShareOpen public URLs when you need previews, demos, callbacks, or quick validation.

Platform architecture

A control panel that stays close to your infrastructure.

The dashboard coordinates auth, job state, access rules, repositories, credentials, workers, containers, and public URLs while execution stays on the Docker hosts you already control.

worqer.app architecture for remote Docker deployments

The cockpit view

Everything important stays close to the action.

The interface keeps workers, repositories, credentials, commands, container logs, and public URLs in one place so deployment feels calm and legible.

Workers
Worker token+
Mexica Online - Private - 11s ago

Claim a host once, then use it as trusted deployment capacity for the workspace.

GeneralBuildAccess
VisibilityShared with usersone@example.com, two@example.com

Share the deployment surface without handing over every secret or every machine.

Deployment activityclaim mexica-worker connected - Privatecredential github-main shared with operatorssync cardanfx/api -> branch maindeploy compose web:3000 on mexica-workerlogs container healthy - restart and commands readyurl preview tunnel published

Watch releases move from queued work to running services with the signals operators actually need.

Documentation

A practical guide for the whole deployment path.

Open the documentation hub for the architecture, worker setup, and the repository-to-deployment workflow.

01

Architecture

Understand the control panel, Firebase state, Docker workers, queues, containers, and public URLs.

02

Set up a worker

Run the Docker Hub image, persist the worker identity, copy the claim token, and attach the host.

03

Clone and deploy

Add credentials, register a repository, sync branches, select a worker, and launch the service.

Open documentation

worqer.app

Sign in

Manage repositories, workers, domains, and deployments.