head to head · open source
Coolify vs Temps
Coolify has 65,550 GitHub stars, 5,910 forks, 649 open issues and last shipped yesterday. Temps has 887 stars, 75 forks, 14 open issues and last shipped yesterday. Coolify leads on adoption by 7,290% (65,550 vs 887 stars). Coolify is written in PHP under Apache-2.0; Temps is written in Rust under Apache-2.0. Coolify has attracted 9% as many forks as stars, Temps 8%. Temps was the more recently maintained of the two, and both are self-hostable with no licence fee. The two share 1 topic tag (docker), so they are genuine substitutes rather than adjacent tools.
Two open source projects, one decision. Both are free and self-hostable — the differences are community size, license terms, language stack and release pace.
← all 20902 open source comparisons
Side by side
| Coolify | Temps | |
|---|---|---|
| GitHub stars | ★ 66K | ★ 887 |
| License | Apache-2.0 | Apache-2.0 |
| Written in | PHP | Rust |
| Last push | 2026-11-02 | 2026-11-02 |
| Forks | ⑂ 5.9K | ⑂ 75 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Coolify if
- You weight community size — 66K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches PHP
- You value the larger contributor base for long-term maintenance
pick Temps if
- You want the Temps feature set and don't need the biggest community
- You prefer the Apache-2.0 license terms
- Your stack matches Rust
- You evaluated both and Temps fits your workflow better
About Coolify
Coolify An open source & self hostable Heroku / Netlify / Vercel alternative. About the Project Coolify is an open source & self hostable alternative to Heroku / Netlify / Vercel / etc. It helps you manage your servers, applications, and databases on your own hardware; you only need an SSH connection. You can manage VPS, Bare Metal, Raspberry PIs, and anything else. Imagine having the ease of a cloud but with your own servers. That is Coolify . No vendor lock in, which means that all the configurations for your applications/databases/etc are saved to your server. So, if you decide to stop using Coolify (oh…
read the full Coolify overview →
About Temps
Website · Docs · Discussions Features AI native — 440+ operations any agent can drive Every operation in the dashboard is also a CLI command — 440+ of them across 69 groups — and Temps ships the skills that teach an agent how to use them. Drop them into Claude Code , Codex , OpenCode , or any harness that reads .claude/skills/ , and your agent can deploy, inspect traces, run migrations, or add a domain without you writing the glue. Temps runs those agents for you too: workflow sandboxes execute Claude Code, Codex, or OpenCode against your repository, with platform wide skills and MCP servers injected…
read the full Temps overview →
More in Infrastructure & Operations
Related comparisons
More Server & VM Management projects
Compare either of these against the rest of the Server & VM Management field.
Frequently asked questions
Is Coolify or Temps more popular?
Coolify has 65,550 GitHub stars and Temps has 887. Coolify has the larger community by that measure.
Are Coolify and Temps free?
Both are open source. Coolify is licensed under Apache-2.0 and Temps under Apache-2.0. Neither carries a licence fee.
What is the difference between Coolify and Temps?
Coolify is written in PHP and Temps in Rust. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.
Which should I choose, Coolify or Temps?
Choose Coolify if you want the larger community (65,550 stars) or its Apache-2.0 licence terms. Choose Temps if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.