Launch from Git
Move from repository URL to running service with a guided path for branches, build settings, environment values, and target workers.
worqer.appOpening application…
Built for developers · test and production
Ship Docker apps on servers you own.
A dashboard, a command line, and a worker you run anywhere Docker runs. Point worqer.app at a Git repository and it builds, deploys, streams the logs, and hands back a public URL — on your VPS, your office box, or your laptop. AI agents, WordPress, APIs, bots — 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
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.
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.
AI agents and LLM APIs
Keep an agent, a RAG pipeline or a vLLM endpoint on your own GPU box instead of renting inference by the token.
WordPress and WooCommerce
The classic Compose stack — WordPress, MySQL, Redis — on a VPS you control, with logs and restarts a click away.
Next.js, Astro, Laravel, Django
Push to a branch, deploy it, get a subdomain. Preview environments for each client without another hosting bill.
n8n, Metabase, Postgres
Internal tools that hold company data and have no business living on someone else's servers.
Telegram and Discord bots
Small, always-on processes that cost more in platform fees than in actual compute.
Minecraft and game servers
Long-running containers with real memory needs, on the machine you already pay for.
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.
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 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.