head to head · open source

Refine vs Temps

Refine has 35,688 GitHub stars, 3,214 forks, 43 open issues and last shipped 8 days ago. Temps has 756 stars, 59 forks, 14 open issues and last shipped yesterday. Refine leads on adoption by 4,621% (35,688 vs 756 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.

Refine ★ 36K Temps ★ 756 category Infrastructure & Operations

← all 8884 open source comparisons

Side by side

Refine Temps
GitHub stars ★ 36K ★ 756
License MIT Apache-2.0
Written in TypeScript Rust
Last push 2026-09-10 2026-09-17
Forks ⑂ 3.2K ⑂ 59
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

full Refine profile →

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

full Temps profile →

About Refine

Refine is an open source React meta framework for building CRUD heavy internal tools, admin panels, dashboards, and B2B applications. It operates in the React ecosystem and targets developers who need structured, scalable frontends without the constraints of low code platforms or the overhead of building everything from scratch.

read the full Refine overview →

About Temps

Temps is an Apache 2.0 licensed Rust binary that combines deployment, monitoring, analytics, error tracking, email, OpenTelemetry, sandboxes, and an AI gateway in one self hosted system. It is positioned as an alternative to Vercel, Sentry, PostHog, Pingdom, Resend, and E2B.

read the full Temps overview →

More in Infrastructure & Operations

Immich ★ 114K Uptime Kuma ★ 91K worldmonitor ★ 87K mall ★ 85K NetData ★ 81K Elasticsearch ★ 78K

Related comparisons

coolify vs refine dokploy vs refine coolify vs dokploy coolify vs casaos coolify vs 1panel dokploy vs casaos dokploy vs 1panel casaos vs 1panel uptime-kuma vs worldmonitor uptime-kuma vs netdata uptime-kuma vs grafana worldmonitor vs netdata worldmonitor vs grafana netdata vs grafana uptime-kuma vs huginn worldmonitor vs huginn immich vs paperless-ngx immich vs ceph immich vs filestash immich vs garage immich vs storj immich vs alarik immich vs spinifex paperless-ngx vs ceph

More Server & VM Management projects

Compare either of these against the rest of the Server & VM Management field.

Refine vs Coolify Refine vs Dokploy Refine vs CasaOS Refine vs 1Panel Refine vs Cosmos Server Refine vs aaPanel Refine vs YunoHost Refine vs OpenPanel

Frequently asked questions

Is Refine or Temps more popular?

Refine has 35,688 GitHub stars and Temps has 756. 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,688 stars) or its MIT licence terms. Choose Temps if its feature set, stack or Apache-2.0 licence fits better. Both are self-hostable.