Is this project dead?

[jsahoka]

We would like to implement Cachet in our organization and I was thinking we would start with 2.x since localization is not available yet in the 3.x version but I am starting to wonder if it is advisable to implement this in production since it seems to be a dead product now?
I hope I don't sound entitled but I am just wondering.

Would you still start using this now or am I better of looking for a (paid) alternative?

[Ronald-Agorsah]

Might be

[Root-Aamir]

I wouldn’t call it dead, but I also wouldn’t treat 3.x as production-ready yet.

From what I can see, 3.x is still a rebuild/in-development track, so if your organization needs a stable status page today — especially with localization — I’d be careful about adopting 3.x in production right now.

If localization is a hard requirement, I’d suggest either:

1. Use the stable 2.x branch for now, after testing it properly in your environment.
2. Wait for 3.x to mature and confirm localization support.
3. Choose a paid/managed alternative if you need production support, SLAs, and predictable maintenance.

For an internal/demo environment, Cachet is still worth testing. For customer-facing production, I’d only use it after validating upgrade path, localization, security updates, backup/restore, and incident workflow.

[jbrooksuk]

Not dead, just slow moving - sorry! Work is busy, I have a young family who I like to spend time with and I'm trying to cycle more 😅

That said, I've been getting through a lot of features / outstanding issues with the help of Claude. I'm very keen to keep pushing Cachet forward. I've also updated the docs recently, which includes backfilling the changelog.

Recently we've:

Added

• (Core) Subscribers and email notifications for incidents and scheduled maintenance #372
• (Core) API endpoints to manage subscribers #377
• (Core) Settings to disable the API or require authentication for all API requests #378
• (Core) Support for Laravel 13 #368
• ​

Changed

• (Core) Redesigned dashboard #370
• (Core) Refined status page design with a unified components list and clearer incident timeline 94a2b4
• (Core) Cachet API routes no longer inherit the host application’s rate limiter #375

We're actually nearing an alpha release. I'd love to get more localizations in, once we've settled down on feature and bug work.