head to head · open source
Refine vs Temps
Refine has 35,981 GitHub stars, 3,266 forks, 43 open issues and last shipped 2 months ago. Temps has 887 stars, 75 forks, 14 open issues and last shipped yesterday. Refine leads on adoption by 3,956% (35,981 vs 887 stars). Refine is written in TypeScript under MIT; Temps is written in Rust under Apache-2.0. Refine 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.
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
| Refine | Temps | |
|---|---|---|
| GitHub stars | ★ 36K | ★ 887 |
| License | MIT | Apache-2.0 |
| Written in | TypeScript | Rust |
| Last push | 2026-09-10 | 2026-11-02 |
| Forks | ⑂ 3.3K | ⑂ 75 |
| Self-hosting | Yes | Yes |
| Data ownership | Your server | Your server |
pick Refine if
- You weight community size — 36K stars and counting
- You want the MIT license terms
- Your stack matches TypeScript
- 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 Refine
Home Page Documentation Examples Discord Blog Refine The sweet spot between the low/no code and “starting from scratch” for CRUD heavy applications. Refine Core is an open source, React meta framework for enterprise. It provides a headless solution for everything from admin panels to dashboards and internal tools. Refine CORE also powers Refine's purpose built AI agent. What is Refine CORE? Refine CORE is a React meta framework for CRUD heavy web applications. It addresses a wide range of enterprise use cases including internal tools, admin panels, dashboards and B2B apps. Refine CORE's hooks and components…
read the full Refine 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 Refine or Temps more popular?
Refine has 35,981 GitHub stars and Temps has 887. Refine has the larger community by that measure.
Are Refine and Temps free?
Both are open source. Refine is licensed under MIT and Temps under Apache-2.0. Neither carries a licence fee.
What is the difference between Refine and Temps?
Refine is written in TypeScript 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, Refine or Temps?
Choose Refine if you want the larger community (35,981 stars) or its MIT licence terms. Choose Temps if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.