Coolify
BetaDeploy Shipper applications and multi-service stacks to self-hosted or cloud Coolify instances.
Initial provider implementation. Test against the target Coolify version and API permissions before production use.
Provider notes
Operating Coolify through Shipper
Use this provider when your infrastructure already runs through Coolify. Shipper keeps the deployment workflow consistent, while provider-specific capabilities and limits still depend on what Coolify exposes on the target account or instance.
Operational model
Keep the workflow consistent
What Shipper handles
Environment-independent deployment orchestration, profile selection, and a consistent project configuration surface across providers.
What stays provider-specific
Authentication details, resource identifiers, available features, and behavior that can differ between plans, regions, or instance setups.
Production gate
Check the exact account first
- Validate authentication and resource identifiers against a non-critical project first.
- Confirm every feature you plan to use on the overview page support matrix.
- Test deploy, rollback, and any provider-managed resources on the exact account type you run in production.