head to head · open source
CasaOS vs Temps
CasaOS has 37,521 GitHub stars, 2,209 forks, 833 open issues and last shipped 1 months ago. Temps has 887 stars, 75 forks, 14 open issues and last shipped yesterday. CasaOS leads on adoption by 4,130% (37,521 vs 887 stars). CasaOS is written in Go under Apache-2.0; Temps is written in Rust under Apache-2.0. CasaOS has attracted 6% 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
| CasaOS | Temps | |
|---|---|---|
| GitHub stars | ★ 38K | ★ 887 |
| License | Apache-2.0 | Apache-2.0 |
| Written in | Go | Rust |
| Last push | 2026-09-28 | 2026-11-02 |
| Forks | ⑂ 2.2K | ⑂ 75 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick CasaOS if
- You weight community size — 38K stars and counting
- You want the Apache-2.0 license terms
- Your stack matches Go
- 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 CasaOS
CasaOS Your Personal Cloud Connect with the community, establish autonomy, reduce the cost of SaaS, and MAXIMIZE the potential for a personalized copilot. Website Demo GitHub Why do you need Personal Cloud? In 2020, the team noticed three important trends: The cost of computing power and storage was decreasing fast. A part of cloud computing was moving towards edge computing. The issue of consumer data asset ownership and attribution had been ignored. Based on these trends, the team proposed a thought experiment internally: what if personal clouds were available under $100 in next five years? This personal cloud…
read the full CasaOS 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 CasaOS or Temps more popular?
CasaOS has 37,521 GitHub stars and Temps has 887. CasaOS has the larger community by that measure.
Are CasaOS and Temps free?
Both are open source. CasaOS is licensed under Apache-2.0 and Temps under Apache-2.0. Neither carries a licence fee.
What is the difference between CasaOS and Temps?
CasaOS is written in Go 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, CasaOS or Temps?
Choose CasaOS if you want the larger community (37,521 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.