A zero‑friction, serverless continuous deployment (CD) engine built for mobile‑first developers.
Engineered by DemonZ Development for seamless integration with Android, Termux, and mobile IDEs.
DemonZ Deployer is a client‑side tool that runs entirely in your browser.
For local development or self‑hosting, you can install the package via npm:
npm install @demonzdevelopment/demonz-deployer
The package includes the frontend assets, Cloudflare Worker proxy script, and configuration templates. Refer to the Self‑Hosting section for setup instructions.
Deploying complex, multi‑directory projects from a mobile browser to GitHub is notoriously unstable. DemonZ Deployer eliminates the need for a local Git CLI or a dedicated backend. Developers simply compress their workspace into a workspace.zip archive and upload it through our browser‑based console. The engine securely streams the binary to the GitHub REST API, triggering an automated Actions pipeline that extracts, verifies, and commits the changes directly to your repository.
No manual token generation. No infrastructure. No friction.
The v2.0.3 One-Click Login update deprecates Device Flow in favour of the GitHub Web Application Flow, eliminating manual code entry and tab-switching entirely.
- GitHub OAuth 2.0 (Web Application Flow) – One-click authentication. GitHub redirects you back automatically — no codes to copy, no tabs to switch.
- 100% Serverless Architecture – Operates entirely in the browser, supported by a highly restricted Cloudflare Worker CORS proxy.
- Live Repository Integration – Instantly search, filter, and select from your personal and organisational repositories.
- Automated Pipeline Installation – Install the required GitHub Actions extraction workflow into any target repository with a single click.
- Volatile Session Security – Access tokens are stored securely in
localStorageensuring your session persists smoothly.
DemonZ Deployer requires zero installation and operates entirely within your browser.
- Authenticate Navigate to the Deployer Console and click Connect with GitHub. You'll be redirected to GitHub to authorise the app, then brought straight back automatically.
- Select Target Use the live search interface to select your target repository and branch.
- Initialize Pipeline (First‑Time Only) If the repository lacks the extraction workflow, click Setup Repository to auto‑install the pipeline.
- Deploy Workspace
Drag and drop your
workspace.zipinto the staging area and click Deploy.
The integrated terminal will output real‑time progress across all five deployment stages:
Auth → Encode → SHA Check → Upload → Deployed
DemonZ Deployer is built on a Zero‑Trust Client‑Side Model. Your code and credentials never touch our servers.
- Stateless Proxy – GitHub's OAuth endpoints lack CORS headers. To solve this without a traditional backend, we utilise a stateless Cloudflare Worker. This proxy strictly enforces an origin whitelist, payload size caps (1 KB), and IP‑based rate limiting via Cloudflare KV. It logs nothing.
- Direct API Commits – Once authenticated, all file uploads and Git operations are transmitted directly from your browser to
api.github.com. - Smart Delta Commits – The automated GitHub Actions runner extracts your zip, overlaying the existing codebase. If no structural changes are detected, it cleanly exits without polluting your Git history with empty commits.
| Issue | Cause | Fix |
|---|---|---|
| Fake 404 on Pipeline Install | Missing workflow scope in OAuth app | Add the workflow scope to your GitHub OAuth application. |
| Pipeline runs but commit fails | Missing Actions permissions | In the repository Settings > Actions > General, set "Workflow permissions" to Read and write permissions. |
| HTTP 422 Error on Upload | Payload too large | Ensure your workspace.zip is under 50 MB. |
For developers wishing to fork this repository or host an internal instance:
- Register a new GitHub OAuth Application and set the Authorization Callback URL to your app's hosted URL.
- Deploy the proxy script located at
worker/worker.jsto Cloudflare Workers. - Update
js/config.jswith your distinctCLIENT_IDand CloudflarePROXY_URL. - Host the frontend assets via GitHub Pages or any static CDN.
Please refer to CONTRIBUTING.md for architectural guidelines and PR submission standards.
DemonZ Development – Forging Digital Empires.