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 Read the docs

DashboardDeploy, share and watch every projectworqer-cliThe same power from your terminalworqer-runnerConnect 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

$ worqer-cli install
✓ worqer-runner online · claim token 8f3aQ2…

$ worqer-cli claim 8f3aQ2
✓ Mexica claimed · docker 27.3 · 8 vCPU

$ worqer-cli deploy api --worker Mexica
  build   ████████████████   compose.yaml
  deploy  ████████████████   3 services
✓ api healthy · https://api.example.com

The worqer-runner worker image on Docker Hub

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.

Dashboard, CLI and Git connect to a control panel for your workers, Cloudflare deployments and team access.

Built on tools you already trust

Next.jsReactTypeScriptGoFirebaseDocker HubnpmSQLiteGitHubGitngrokNode.jsCloudflare

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

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.

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.

PGSQL