It of cause makes sense for closed source software, but being open source it invites in people who at the very least want to read the `README.md`, star the repo and most likely want to have a look at the source code.

I kind of panicked when the download button actually downloaded - I was like "hey stop! wait a sec! I want to check out the code first" - maybe it's just me ;)

The demo page doesn't look cachable: a "Cache-Control: no-cache" header, no ETag or Last-Modified headers. It's obvious that they don't want stale pages in a cache, but why not take advantage of a simple Last-Modified to remove most traffic from people refreshing every few seconds?

We've struggled a lot with caching under CloudFlare and have an open issue to fix the headers - something I'll be looking at very soon!

It's great to see Stoke-on-Trent represented in the startup arena.

As I'm really keen to see more local jobs and affluence, my comment would be, there's nothing about how the project will be sustained financially, no payment plans or premium support.

Look forward to seeing more about this at Staffs Web Meetup.

At the moment Cachet is open source. We'd accept donations but don't actively ask for them.

We're also selling stickers on StickerMules marketplace, but other than that no income.

I'm looking into this though.

Catch you next time.

Did you see my talk on Depression & Anxiety?

that said it's pretty much the only free alternative out there, so it's a welcome and refreshing change. props up to the devs too that have been very fast and responsive on github, fixing issues, bugs and suggestions on the same day sometimes. a rare breed.

(Disclaimer: I wrote Statytus)

Thanks for your continued support :)

Documentation is still draft.

Does anyone have some more detail about the required steps to integrate the checks?

What Cachet is not

Here is a list of things that Cachet is not or does not do:

1. It does not monitor your services. It works only as a way to display the status of your services. However, Cachet is able to receive updates from third-party services via its API.

2. It does not work on a plugin system. There are no monitoring services to extend.

So basically we need both Cachet for displaying the status and another tool to check it (it wouldn't be very good if the tool was on the app itself otherwise it might not be effective when it's truly needed).

I was hoping to have both in one place (the monitoring and the status), is there a "cachet-ready" system?

Once we're stable then we'll finish it off. Things change too often recently.

There are a lot of people using Cachet in the same way as we do and even for services or business that are making money.

If the two are on par feature-wise, I suppose it comes down to the cost savings of maintaining your own versus the time savings of outsourcing the problem to someone else. It might be nice just to forget about monitoring maintenance.

However I've since removed this feature in the Laravel 5 rewrite.

[0]https://github.com/cachethq/Cachet/commit/5043a86b80080e92ae...