Deploy to your own servers.
It watches them for you, and Claude can fix them.
Docksy is a simple, self-hosted PaaS. You get git-push deploys with zero downtime, monitoring and alerts on by default, backups that are proven to restore, and first-class Claude integration.
$ curl -fsSL https://raw.githubusercontent.com/osmanyousaaf/docksy/main/install.sh | sudo bash
Three things, done properly
Docksy is deliberately smaller than other PaaS tools. What it does, it does by default.
Monitoring on by default
Live CPU, memory, disk and network for every server and container, from a sub-15 MB agent.
- 10 alert rules preconfigured
- Uptime checks auto-created per domain
- Public status page
- Discord, Slack, Telegram, email, webhooks
Claude-native
A first-party MCP server and Claude Code plugin. Claude deploys, reads metrics, diagnoses and fixes, always with your consent.
- 34 MCP tools + deterministic
diagnose - Skills: deploy, diagnose, incident, dockerize
- SRE subagent
- No AI inside Docksy, ever
Simple, reliable deploys
Push to GitHub and it ships. The old version keeps serving until the new one is healthy.
- Dockerfile, compose, image or auto-detect
- Automatic HTTPS (Caddy)
- One-click rollback
- One-click databases + verified backups
Your on-call SRE, in the terminal
An alert fires. You type one line. Claude gathers the evidence, explains the cause, and fixes it once you say yes.
> /docksy:diagnose api โ docksy ยท diagnose(appId: "api") โ docksy ยท get_server_metrics(prod-1, 1h) mem โโโโโ โโโโ 97% โ docksy ยท list_deployments(api) โธ api: crash-looping, OOM-killed 6ร in 10 min Cause: deploy a1b2c3d (13:58, "add in-memory cache") โ memory 61% โ 97% โ container OOMKilled โ 502s on api.example.com (confidence: high) Evidence: State.OOMKilled=true ยท RestartCount 6 ยท uptime check down since 14:03 Fix: 1. rollback_app(api โ 9f8e7d6, yesterday 18:20) zero downtime, ~30s 2. cap the cache size, then redeploy Roll back api to 9f8e7d6? yes โ Rolled back. Memory 58%, uptime check green, alert resolved.
Docksy vs Coolify
Coolify is a great, far more mature project with a much larger catalog, and we owe it a lot. This is an honest look at where each one stands.
| Capability | Docksy | Coolify |
|---|---|---|
| Open source, self-hosted | โ Apache-2.0 | โ Apache-2.0 |
| Git-push deploys, rollback, automatic HTTPS | โ | โ |
| Server & container metrics | โ on by default | โ (Sentinel) |
| CPU & memory alerts | โ default rules | โ |
| Disk usage alerts | โ | โ |
| Uptime checks & public status page | โ | โ |
| Scheduled database backups to S3 | โ | โ |
| Automatic backup restore verification | โ | โ |
| MCP server | โ | โ |
Deterministic diagnose tool for AI | โ | โ |
| Claude Code plugin (skills, SRE agent, safety hook) | โ | โ |
| One-click services catalog | 12 templates | โ hundreds |
| Preview deployments, Swarm, many git providers | not yet | โ |
| Paid tiers | none, free forever | free self-hosted; paid cloud option |
Based on Coolify's public source and docs as of November 2026. Spotted something wrong? Tell us and we'll fix it.
Get going
From a fresh VPS to a live, monitored app in a few minutes.