head to head · open source

telegraf vs Cachet

telegraf has 17,807 GitHub stars, 5,839 forks, 449 open issues and last shipped yesterday. Cachet has 15,242 stars, 1,632 forks, 7 open issues and last shipped yesterday. telegraf leads on adoption by 17% (17,807 vs 15,242 stars). telegraf is written in Go under MIT; Cachet is written in PHP under a custom or non-standard licence. telegraf has attracted 33% as many forks as stars, Cachet 11%. Cachet 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.

telegraf ★ 18K Cachet ★ 15K category Infrastructure & Operations

← all 8884 open source comparisons

Side by side

telegraf Cachet
GitHub stars ★ 18K ★ 15K
License MIT Custom / other
Written in Go PHP
Last push 2026-09-17 2026-09-17
Forks ⑂ 5.8K ⑂ 1.6K
Self-hosting Yes Yes
Data ownership Your server Your server

pick telegraf if

  • You weight community size — 18K stars and counting
  • You want the MIT license terms
  • Your stack matches Go
  • You value the larger contributor base for long-term maintenance

full telegraf profile →

pick Cachet if

  • You want the Cachet feature set and don't need the biggest community
  • You prefer the Custom / other license terms
  • Your stack matches PHP
  • You evaluated both and Cachet fits your workflow better

full Cachet profile →

About telegraf

Telegraf is a Go based, MIT licensed open source agent that collects, processes, aggregates, and writes metrics, logs, and other arbitrary data, and it is aimed at engineers who run their own monitoring and observability pipelines.

read the full telegraf overview →

About Cachet

Cachet is an open source, self hosted status page system. It lives in the PHP and Laravel ecosystem, and it is categorized under Infrastructure and Operations and Monitoring and Observability. The project is intended for teams that need a dedicated place to communicate service status and downtime in a transparent way.

read the full Cachet overview →

More in Infrastructure & Operations

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

Related comparisons

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 mall vs prometheus mall vs nocodb mall vs etcd mall vs dbeaver mall vs orm prometheus vs nocodb mall vs milvus mall vs tidb

More Monitoring & Observability projects

Compare either of these against the rest of the Monitoring & Observability field.

telegraf vs Uptime Kuma telegraf vs worldmonitor telegraf vs NetData telegraf vs Grafana telegraf vs huginn telegraf vs Sentry telegraf vs SigNoz telegraf vs Grafana Loki telegraf vs beszel telegraf vs cilium telegraf vs Apache SkyWalking telegraf vs jaeger

Frequently asked questions

Is telegraf or Cachet more popular?

telegraf has 17,807 GitHub stars and Cachet has 15,242. telegraf has the larger community by that measure.

Are telegraf and Cachet free?

Both are open source. telegraf is licensed under MIT, and Cachet has no licence declared in this registry. Both are free to self-host.

What is the difference between telegraf and Cachet?

telegraf is written in Go and Cachet in PHP. The practical differences are community size, licence terms, language stack and release cadence — all compared in the table above.

Which should I choose, telegraf or Cachet?

Choose telegraf if you want the larger community (17,807 stars) or its MIT licence terms. Choose Cachet if its feature set, stack or Custom / other licence fits better. Both are self-hostable.