Hi Cleavr Team 
,
I’ve been using Cleavr for a while now and it has become an essential part of how I manage my servers and sites. However, one limitation I keep running into is the lack of an external API.
I saw an older discussion about this topic here: “When will the API be available?” and wanted to bring this request back to attention, as the need has grown even more in 2025.
Why a Public API Would Be a Major Benefit
Automated Provisioning & Deployments
Having an API would allow us to automate server setup, deployments, backups, SSL checks, and other routine tasks. This is especially useful when scaling up or managing multiple projects.
Integration With CI/CD Pipelines
A public API would let us trigger deploys from GitLab, GitHub Actions, Bitbucket Pipelines, n8n, etc. without relying only on webhook triggers or manual steps.
Multi-Environment Management
Agencies and SaaS developers (like myself) often need to create/manage staging and production environments automatically. A Cleavr API would make this seamless.
Better Monitoring & Health Checks
Fetching server status, deployment history, queue worker status, etc. through an API would allow us to integrate everything into our dashboards.
More Advanced Workflows
With tools like n8n, Zapier, Make.com, and custom scripts, we could automate a lot of Cleavr’s actions to save time and reduce human error.
Examples of Useful Endpoints
- Create server
- Deploy site
- Restart services (PHP, Nginx, queue workers, etc.)
- Trigger backup
- Access logs
- Update environment variables
- List deployments, tasks, and statuses
Cleavr is already a great platform — an API would make it even more powerful and open the door for deeper integrations with modern dev workflows.
Is this something that could be added to the roadmap?
Thanks for considering it! 