Deploy Coolify to any cloud VPS with one command
Quicklify is a CLI tool that automates Coolify installation on cloud VPS providers. One command to deploy your self-hosted PaaS platform.
Before Quicklify:
Create VPS manually (5 min)
SSH into server (2 min)
Install Docker (10 min)
Configure firewall (5 min)
Install Coolify (10 min)
Total: ~30 minutes + manual work
With Quicklify:
npx quicklify init
# Hetzner: ~4 minutes | DigitalOcean: ~6 minutes
# Zero manual work ✨
--provider --token --region --size --name flagsnpx quicklify init
npm install -g quicklify
quicklify init
Hetzner Cloud:
DigitalOcean:
npx quicklify init
You'll be prompted for:
After deployment (Hetzner ~4 min, DigitalOcean ~6 min):
✅ Deployment Successful!
Server IP: 123.45.67.89
Access Coolify: http://123.45.67.89:8000
Visit the URL, create your admin account, and start deploying!
Important: Port 8000 is publicly accessible after deployment.
Recommended next steps:
For production use, we recommend setting up a domain instead of using the IP address directly.
| Provider | Status | Starting Price | Architecture |
|---|---|---|---|
| Hetzner Cloud | ✅ Available | €3.49/mo | ARM64 + x86 |
| DigitalOcean | ✅ Available | $12/mo | x86 |
| Vultr | 📋 Planned | $2.50/mo | x86 |
| Linode | 📋 Planned | $5/mo | x86 |
Perfect for:
When to use alternatives:
| Solution | Monthly Cost | Setup Time | Management |
|---|---|---|---|
| Vercel (Hobby) | $20+ | 5 min | Easy |
| Vercel (Pro) | $50+ | 5 min | Easy |
| Netlify (Pro) | $19+ | 5 min | Easy |
| Quicklify + Hetzner | €3.49 | ~4 min | Easy |
| Quicklify + DigitalOcean | $12 | ~6 min | Easy |
| Manual VPS + Coolify | €3.49 | 30+ min | Hard |
Savings: ~$180-240/year per project! 💰
quicklify list, quicklify status [query], quicklify destroy [query]quicklify init --provider --token --region --size --name for CI/CD~/.quicklify/servers.json for list/status/destroydestroyServer() added to provider interface (Hetzner + DigitalOcean)/datacenters API for real availability per locationany types - full type safety~/.quicklify/servers.json)destroyServer() on provider interface# Deploy new Coolify instance (interactive)
quicklify init
# Deploy non-interactively (CI/CD friendly)
quicklify init --provider hetzner --token YOUR_TOKEN --region nbg1 --size cax11 --name my-server
# List all registered servers
quicklify list
# Check server and Coolify status
quicklify status 123.45.67.89
quicklify status my-server
# Destroy a server (with double confirmation)
quicklify destroy 123.45.67.89
quicklify destroy my-server
# Show version
quicklify --version
# Show help
quicklify --help
Pass all options as flags to skip interactive prompts (useful for CI/CD pipelines):
quicklify init \
--provider hetzner \
--token $HETZNER_TOKEN \
--region nbg1 \
--size cax11 \
--name production-coolify
Using environment variables (recommended for CI/CD):
# Set token as environment variable (avoids shell history exposure)
export HETZNER_TOKEN="your-api-token"
# or
export DIGITALOCEAN_TOKEN="your-api-token"
# Token is read automatically from env var
quicklify init --provider hetzner --region nbg1 --size cax11 --name my-server
Token resolution order: --token flag > environment variable > interactive prompt.
If some flags are missing, only the missing values will be prompted interactively.
All steps support ← Back navigation to return to the previous step.
# Run all tests
npm test
# Run tests in watch mode
npm run test:watch
# Run tests with coverage report
npm run test:coverage
# Lint code
npm run lint
# Format code
npm run format
tests/
├── __mocks__/ # Mock modules (axios, inquirer, ora, chalk)
├── unit/ # Unit tests
│ ├── cloudInit.test.ts
│ ├── config.test.ts # Config CRUD operations
│ ├── config-edge.test.ts # Config edge cases (corruption, empty files)
│ ├── destroy.test.ts # Destroy command unit tests
│ ├── healthCheck.test.ts # Health check polling tests
│ ├── healthCheck-edge.test.ts # Health check edge cases (302, 401, 500)
│ ├── list.test.ts # List command unit tests
│ ├── logger.test.ts
│ ├── prompts.test.ts
│ ├── providerFactory.test.ts # Provider factory tests
│ ├── status.test.ts # Status command unit tests
│ └── validators.test.ts
├── integration/ # Integration tests (provider API calls)
│ ├── hetzner.test.ts # Including destroyServer tests
│ └── digitalocean.test.ts # Including destroyServer tests
└── e2e/ # End-to-end tests (full command flows)
├── init.test.ts
├── init-noninteractive.test.ts # Non-interactive mode E2E
├── status.test.ts # Status command E2E
└── destroy.test.ts # Destroy command E2E
Tests run automatically on every push/PR via GitHub Actions across:
Current coverage: 97%+ statements/lines, 89%+ branches, 96%+ functions. 233 tests across 18 test suites.
"Invalid API token"
"Server creation failed"
"Cannot access Coolify UI"
ssh root@YOUR_IP "cat /var/log/quicklify-install.log | tail -20"Contributions are welcome! See CONTRIBUTING.md for development setup, code guidelines, and PR process.
Areas for contribution:
MIT © 2026 Ömer FC
See LICENSE file for details.
If Quicklify helped you, please:
Made with ❤️ by @omrfc
Saving developers time, one deployment at a time. ⚡
FAQs
Automate Coolify deployment on cloud providers
The npm package quicklify receives a total of 56 weekly downloads. As such, quicklify popularity was classified as not popular.
We found that quicklify demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
AI agents are writing more code than ever, and that's creating new supply chain risks. Feross joins the Risky Business Podcast to break down what that means for open source security.
Research
/Security News
Socket uncovered four malicious NuGet packages targeting ASP.NET apps, using a typosquatted dropper and localhost proxy to steal Identity data and backdoor apps.
Research
An emerging npm supply chain attack that infects repos, steals CI secrets, and targets developer AI toolchains for further compromise.