Cachely is the managed self-hosted remote cache for Nx and Turborepo - the cache backend you'd otherwise build and run yourself, hosted for you on Cloudflare's edge (R2). It's a drop-in replacement for a DIY @nx/s3-cache / S3 bucket setup: point your build tool at Cachely with a token and two environment variables, and share build cache across CI and every developer's laptop.

Unlike a self-hosted cache, Cachely enforces read-only tokens at the API, so pull-request and fork builds can read but never write - closing the Nx cache-poisoning attack (CVE-2025-36852). It adds ROI reporting (the real build minutes and dollars the cache saved), per-tool insights, and build-optimization suggestions on top.

Pricing is a flat per-workspace subscription with no per-seat fees - add every developer, bot, and CI actor without watching the bill. Cachely never stores your source code; it caches only task outputs and their content hashes. Nx and Turborepo today; Bazel on the roadmap.

As a maintainer of a few open-source projects, I’ve always wanted to better understand the traffic sources and trends for my repos. Unfortunately, GitHub’s built-in analytics only show limited data from the past 14 days, which doesn’t provide much insight.

That’s why I built Repohistory, a better GitHub repo analytics platform. It automatically fetches and stores your traffic data every day, so you’re no longer limited to just 14 days. The dashboard shows you:

• Daily star growth
• Total views & clones over time
• Top referral websites
• Most-viewed pages in your repo

So if you have any public repos on GitHub, Repohistory can give you a much clearer picture of your traffic trends.

Try it here: https://repohistory.com