Source: https://worq3r.com/en

Built for developers · test and production

# Deploy to Cloudflare or your own Linux servers. 

Deploy from Git to Cloudflare, Docker Compose, Dockerfiles or native systemd services on Linux. Each worker brings its own platform applications: install PostgreSQL, Redis and more, follow deployments and share access with your team from one dashboard.

[Get started free](https://worq3r.com/en/login) [Read the docs](https://worq3r.com/en/docs) 

Dashboard Deploy, share and watch every project worqer-cli The same power from your terminal worqer-runner Connect your own Linux or Docker workers 

Public URLs depend on the deployment target. Use Cloudflare URLs, configured domains or ngrok tunnels for local previews.

worqer-cli 

Platform architecture

## One panel for Cloudflare, Linux and Docker.

Connect your own workers, deploy containers or native Linux services, and publish applications to Cloudflare. The panel coordinates authentication, jobs, team permissions, projects and runtime status. Hosting and cloud provider charges depend on the infrastructure you choose.

Built on tools you already trust

Next.js   React   TypeScript   Go   Firebase   Docker Hub   npm   SQLite   GitHub   Git   ngrok   Node.js   Cloudflare  

Self-hosted execution

## Keep deployment execution on machines you control.

worqer runs on machines you own. Configure your build and deployment commands on your worker. There are no platform build minutes to buy; source hosting, external APIs and cloud availability still depend on their providers.

[Deploy your first worker](https://worq3r.com/en/login) 

### Your machines, your queue

A VPS, an office box, a laptop. The worker takes the job the moment you press deploy, because nobody else is in front of you.

### A forge with CI, in one click

Gitea and Forgejo are in the catalog. Both speak the Actions workflow syntax, so the pipelines you already wrote have somewhere to run that you control.

### Pipelines beyond a push

Apache Airflow is in the catalog too, with its database wired up. For the work that runs on a schedule, retries, and has to explain itself later.

### Leave whenever you want

Plain Docker Compose and Dockerfiles on hosts you already administer. Nothing here holds your deployments hostage, including us.

Deployment destinations

## Choose the runtime. Keep one control panel.

Run applications at the edge or on your Linux machines, and keep platform services alongside them.

### Cloudflare

Publish applications to Cloudflare from a registered project. Configure the build command and worker name, and track the published URL.

### Linux with systemd

Build and run native Linux services on workers with systemd enabled. Track their status, restart them or remove a service from its host.

### Docker Compose and Dockerfile

Build container images and run individual services or Compose stacks on your VPS, office machines or local workers.

### Platform applications per worker

Install PostgreSQL, Redis, Listmonk and OSRM on your worker. The catalog also includes MySQL, MariaDB, MongoDB, Grafana, n8n and more.

Assign workers to teams and choose whether members can view their projects and deployments. Keep read access separate from administration.

## 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.

## One deploy, every machine

Share a worker and a teammate deploys to it without touching your server. Mix a laptop, an office box and a production VPS in the same workspace — then ship to one of them, or to all of them at once, in seconds.

## Reachable the moment it runs

Publish supported applications with Cloudflare URLs or configured domains. Use ngrok tunnels to share local environments where tunneling is configured.

## Databases on your workers

Deploy PostgreSQL, MySQL, Redis, MongoDB, Supabase and more on your own worker. Configure access and choose where the data lives; hosting costs remain with your provider.

What people run on it

## Your applications and platform services, together.

Deploy from the application catalog or bring your own Dockerfile or Compose stack. Choose Linux systemd for native services, or Cloudflare for supported web applications.

PG SQL 

### PostgreSQL

Configure and deploy from the catalog.

SB Backend 

### Supabase Postgres

Configure and deploy from the catalog.

MY SQL 

### MySQL

Configure and deploy from the catalog.

MA SQL 

### MariaDB

Configure and deploy from the catalog.

RE Key/value 

### Redis

Configure and deploy from the catalog.

MO Document 

### MongoDB

Configure and deploy from the catalog.

CO Document 

### CouchDB

Configure and deploy from the catalog.

CH Analytics 

### ClickHouse

Configure and deploy from the catalog.

N4 Graph 

### Neo4j

Configure and deploy from the catalog.

IN Time series 

### InfluxDB

Configure and deploy from the catalog.

ES Search 

### Elasticsearch

Configure and deploy from the catalog.

OS Search 

### OpenSearch

Configure and deploy from the catalog.

OR Maps & Routing 

### OSRM

Configure and deploy from the catalog.

NG Web & Proxy 

### Nginx

Configure and deploy from the catalog.

LM Email & Marketing 

### Listmonk

Configure and deploy from the catalog.

WP CMS 

### WordPress

Configure and deploy from the catalog.

GH CMS 

### Ghost

Configure and deploy from the catalog.

DR CMS 

### Drupal

Configure and deploy from the catalog.

JO CMS 

### Joomla

Configure and deploy from the catalog.

DI Headless CMS 

### Directus

Configure and deploy from the catalog.

ST API & Headless 

### Strapi

Configure and deploy from the catalog.

HS API & Headless 

### Hasura

Configure and deploy from the catalog.

PG API & Headless 

### PostgREST

Configure and deploy from the catalog.

PA API & Headless 

### Parse Server

Configure and deploy from the catalog.

BR API & Headless 

### Baserow

Configure and deploy from the catalog.

NC Productivity 

### Nextcloud

Configure and deploy from the catalog.

MT Analytics 

### Matomo

Configure and deploy from the catalog.

PS Commerce 

### PrestaShop

Configure and deploy from the catalog.

UK Monitoring 

### Uptime Kuma

Configure and deploy from the catalog.

GT DevTools 

### Gitea

Configure and deploy from the catalog.

AR DevTools 

### Actions runner

Configure and deploy from the catalog.

FJ DevTools 

### Forgejo

Configure and deploy from the catalog.

VW Security 

### Vaultwarden

Configure and deploy from the catalog.

JF Media 

### Jellyfin

Configure and deploy from the catalog.

GF Monitoring 

### Grafana

Configure and deploy from the catalog.

PR Monitoring 

### Prometheus

Configure and deploy from the catalog.

PT DevTools 

### Portainer

Configure and deploy from the catalog.

MI Storage 

### MinIO

Configure and deploy from the catalog.

MB Analytics 

### Metabase

Configure and deploy from the catalog.

NO No-code 

### NocoDB

Configure and deploy from the catalog.

SX Search 

### SearXNG

Configure and deploy from the catalog.

HA IoT 

### Home Assistant

Configure and deploy from the catalog.

AF Orchestration 

### Apache Airflow

Configure and deploy from the catalog.

N8 Automation 

### n8n

Configure and deploy from the catalog.

FL AI flows 

### Flowise

Configure and deploy from the catalog.

LF AI flows 

### Langflow

Configure and deploy from the catalog.

CR AI agents 

### CrewAI Studio

Configure and deploy from the catalog.

OL AI runtime 

### Ollama

Configure and deploy from the catalog.

OW AI chat 

### Open WebUI

Configure and deploy from the catalog.

QD Vector DB 

### Qdrant

Configure and deploy from the catalog.

Built for agents too

## Let an agent do the deploy.

worqer-cli is a plain command-line tool with predictable output, so a coding agent can drive it the same way you would. Point Claude Code, Cursor or your own script at it and deploying becomes a step in the task rather than something a human stops to do.

- One binary, no SDK and no browser step

- Sign in once; the session refreshes itself

- Same permissions as the person who signed in

- Deploy, read logs and check status from a script or CI

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.

01 Prepare Connect code, credentials, runtime settings, and the worker that should own the deployment. 

02 Launch Choose Cloudflare, native Linux systemd, Docker Compose or Dockerfile for the project. 

03 Operate Manage containers, commands, restarts, logs, and service state from one surface. 

04 Share Open public URLs when you need previews, demos, callbacks, or quick validation. 

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.

Illustrative delivery workflow  build unit integration dev staging prod 

api · main       

web · develop       

worker · main       

docs · main       

Illustration of a delivery workflow. Tests and environment promotion depend on your build commands and external orchestration; worqer does not create this pipeline automatically.

Deployment activity `claim  mexica-worker connected - Private``credential  github-main shared with operators``sync  cardanfx/api -> branch main``deploy  compose web:3000 on mexica-worker``logs  container healthy - restart and commands ready``url  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 API, PostgreSQL storage, Firebase authentication, workers, Cloudflare deployments and team access.

](https://worq3r.com/en/docs#architecture) [02 

### Set up a worker

Install the worker on Linux or run its Docker image, complete device authorization and connect it to your workspace.

](https://worq3r.com/en/docs#workers) [03 

### Clone and deploy

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

](https://worq3r.com/en/docs/deploy) 

[Open documentation](https://worq3r.com/en/docs) 

Start now

## Start shipping from the machines you already own.

Sign in with email or Google, claim your first worker, and turn a repository into a running service from the dashboard.

[Sign in](https://worq3r.com/en/login) [Read the docs](https://worq3r.com/en/docs)
