tidoly vs Coolify
Summary. Coolify installs the app. tidoly installs it and configures the connections.
Coolify
An open-source PaaS on Docker. A push triggers a webhook, Coolify builds an image with Nixpacks or your Dockerfile, connects to your server over SSH, and runs the container. Traefik issues the certificate and switches traffic. Its one-click catalog is the largest in this category.
There is no orchestrator. Containers restart, but they do not move to another machine if one fails. With several servers, Coolify manages each over SSH.
tidoly
A commercial platform on Kubernetes (k3s). You run an installer and enter a license key. Catalog entries declare the resources they need, and the platform creates and connects them.
Example: a team wiki
It needs a database, object storage, mail, a domain and sign-in.
Coolify — Deploy the wiki. Deploy PostgreSQL. Paste the connection string into the app. Create storage credentials and paste those. Point a domain at it. Register an OIDC client and paste the secret. Repeat when a credential changes.
tidoly — Select it from the catalog. Enter a domain. The rest is configured automatically.
Choose Coolify if
- You need open source
- You deploy your own code across many projects — Coolify has more build integrations
- Catalog size matters most
- Docker is enough for you
Choose tidoly if
- You run apps for a team, so sign-in and domains are required
- You want connections maintained rather than reconfigured
- You want Kubernetes without operating it
- You want a vendor to contact
Both
Both run on hardware you own. Your data and applications stay on your machine, and HTTPS certificates are managed automatically.