Leave the dashboard when you want to,
ship from the terminal instead
DeployPages supports teams who prefer terminal and CI-driven workflows. Publish static builds from local development or automation systems with a process that feels repeatable and scriptable.
Why teams move deployment into CLI workflows
Better fit for CI and release automation
Once a static build already exists in CI, the cleanest path is often a deploy command that can be scripted, repeated, and audited.
Safer machine-to-platform authentication
Deploy workflows should rely on scoped deploy credentials rather than human account passwords.
A natural next step after manual uploads
Teams can start with drag-and-drop publishing, then move to CLI-based release workflows without changing the deployment platform underneath.
CI-friendly deployment snippet
steps:
- uses: actions/checkout@v2
- run: npm install && npm run build
- run: npx deploypages-cli ./dist --token ${{ secrets.DEPLOY_TOKEN }}Frequently asked questions
Q: Can this run on Windows, macOS, and Linux?
That is the intended workflow. A CLI deploy path only makes sense if it fits the environments teams actually build from.
Q: Can I target a specific project from automation?
Yes. Scriptable deployment only works well when teams can explicitly bind a release flow to the right project context.
Q: Does this fit monorepos?
Yes. Teams with monorepos need a deployment path that can target specific working directories and release outputs cleanly.
Ready to try it?
Drop in your static project below and publish it with a live URL in minutes.
~ deploypages publish .
Scanning directory...
✓ Uploaded files instantly via edge network
✓ Fast, Secure, and Global Delivery
🚀 Powered by DeployPages