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.
worqer.appOpening application…
Built for developers · test and production
Run Docker apps on servers you own.
Stop waiting on someone else's queue. A dashboard, a command line, and a worker you run anywhere Docker runs: point worqer.app at a Git repository and it builds, tests, deploys, streams the logs, and hands back a public URL — on your VPS, your office box, or your laptop. Your machine starts the job the second you ask. No build minutes, no egress bills, no vendor holding your infrastructure.
DashboardDeploy, share and watch every projectworqer-cliThe same power from your terminalworqer-runnerFree on your own machine, or use a hosted one
Every project gets a free subdomain. Running on your laptop? An ngrok tunnel puts local environments on a public URL too.
Platform architecture
One control panel. Free capacity, managed capacity, shared capacity.
Free means either machine: run the worker on a VPS, an office box or your laptop, or use a hosted one we provide — both cost nothing and behave identically from the panel. Move to managed production workers when it matters, and share any worker, free or paid, with your team. The panel coordinates auth, jobs, access rules, repositories, credentials, containers and public URLs the same way regardless of where the work lands.
Built on tools you already trust
Next.jsReactTypeScriptGoFirebaseDocker HubnpmSQLiteGitHubGitngrokNode.jsCloudflare
A self-hosted alternative to GitHub Actions
Your CI provider goes down. Your deploys keep going.
worqer runs on machines you own. There is no shared queue to wait in, no minutes to run out of, and no incident on someone else's status page that stops you from shipping.
Deploy your first workerA 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.
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
Every project gets a free subdomain, so a deploy is shareable straight away. Working from a laptop or a machine behind NAT? An ngrok tunnel publishes that local environment on a real URL — same flow, no port forwarding.
Free remote databases
Connect a free remote database or deploy PostgreSQL, MySQL, Redis, MongoDB, Supabase and more on your own worker. Keep credentials together and choose where the data lives.
BugFixer
Premium AI diagnostics group production errors, inspect the authorized repository and prepare a minimal Git diff for review before any branch or hotfix commit.
What people run on it
If it runs in Docker, it runs here.
No templates and no supported-framework list. You bring a Dockerfile or a Compose file and it goes up — the same path whether it is a landing page or a GPU-hungry agent.
PostgreSQL
Configure and deploy from the catalog.
Supabase Postgres
Configure and deploy from the catalog.
MySQL
Configure and deploy from the catalog.
MariaDB
Configure and deploy from the catalog.
Redis
Configure and deploy from the catalog.
MongoDB
Configure and deploy from the catalog.
CouchDB
Configure and deploy from the catalog.
ClickHouse
Configure and deploy from the catalog.
Neo4j
Configure and deploy from the catalog.
InfluxDB
Configure and deploy from the catalog.
Elasticsearch
Configure and deploy from the catalog.
OpenSearch
Configure and deploy from the catalog.
WordPress
Configure and deploy from the catalog.
Ghost
Configure and deploy from the catalog.
Drupal
Configure and deploy from the catalog.
Joomla
Configure and deploy from the catalog.
Directus
Configure and deploy from the catalog.
Strapi
Configure and deploy from the catalog.
Hasura
Configure and deploy from the catalog.
PostgREST
Configure and deploy from the catalog.
Parse Server
Configure and deploy from the catalog.
Baserow
Configure and deploy from the catalog.
Nextcloud
Configure and deploy from the catalog.
Matomo
Configure and deploy from the catalog.
PrestaShop
Configure and deploy from the catalog.
Uptime Kuma
Configure and deploy from the catalog.
Gitea
Configure and deploy from the catalog.
Actions runner
Configure and deploy from the catalog.
Forgejo
Configure and deploy from the catalog.
Vaultwarden
Configure and deploy from the catalog.
Jellyfin
Configure and deploy from the catalog.
Grafana
Configure and deploy from the catalog.
Prometheus
Configure and deploy from the catalog.
Portainer
Configure and deploy from the catalog.
MinIO
Configure and deploy from the catalog.
Metabase
Configure and deploy from the catalog.
NocoDB
Configure and deploy from the catalog.
SearXNG
Configure and deploy from the catalog.
Home Assistant
Configure and deploy from the catalog.
Apache Airflow
Configure and deploy from the catalog.
n8n
Configure and deploy from the catalog.
Flowise
Configure and deploy from the catalog.
Langflow
Configure and deploy from the catalog.
CrewAI Studio
Configure and deploy from the catalog.
Ollama
Configure and deploy from the catalog.
Open WebUI
Configure and deploy from the catalog.
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.
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.
Pipelines
buildunitintegrationdevstagingprod
api · main
web · develop
worker · main
docs · main
Several pipelines at once on machines you own. Nobody is queued ahead of you, so a run starts the second you ask for it — and the same worker carries it from the first unit test through to production.
Deployment activity
claim 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 publishedWatch 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
Open documentationArchitecture
Understand the control panel, Firebase state, Docker workers, queues, containers, and public URLs.
02Set up a worker
Run the Docker Hub image, persist the worker identity, copy the claim token, and attach the host.
03Clone and deploy
Add credentials, register a repository, sync branches, select a worker, and launch the service.
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.