Connect Dokploy or Coolify
Both can be connected at once; each site deploys through the one it is linked to.
Dokploy
- In Dokploy: Settings → Profile → API/CLI → generate a key. Cleanups and the server list need a key of an admin or owner.
- In Moatline: Settings → Dokploy → base URL and the key.
Linked automatically: every repository whose GitHub repository and branch one Dokploy application deploys. Databases are found too (for the database and backup checks), and containers are matched to their service.
Coolify
- In Coolify: Settings → API → turn the API on.
- Keys & Tokens → API tokens → create a token with read and deploy. (Ticking deploy resets the list to deploy only — add read again.)
- In Moatline: Settings → Coolify → URL and token.
Coolify has no rollback in its API: a broken deploy is undone with a git revert of the merge, then deployed again.
What a connected platform enables
- Merge & deploy, auto-deploy after a security fix, with the build followed and the live URL watched
- Rollback (Dokploy's image rollback, otherwise a git revert)
- Self-healing: a site that stays down is restarted
- Redeploy / restart buttons on the server's containers
- Database checks: public ports, missing, disabled, failed or late backups