[augustflanagan]

https://cronitor.io started as a weekend project. I had an acute need for the product which enforced getting a working version quickly. After using the result of that first weekend hackathon in production for a couple of weeks my co-founder and I decided to put in another couple weekend afternoons and evenings to make it a saas product. We've been working on it part-time ever since.

I wrote more about it in an Indie Hackers interview a few months ago - https://www.indiehackers.com/businesses/cronitor

[O_H_E]

I really think you should write something about the purpose of the project & the stack used

[andrewhayter]

This is cool! Please talk about the stack!

[encoderer]

Mostly Python. Django for web app and rest API. The Falcon micro-framework for telemetry collection API.

The dashboard is a React SPA (since 2014!) that is powered entirely by our REST API so new features are always API-enabled.

Alerting rules are handled by a Python daemon that processes the event stream.

Healthchecks are dispatched by coordinators to Lambda workers in a half dozen regions around the world. We started using Lambda before the launch of great frameworks like Serverless so we had to roll our own lambda deployment tooling with Fabric and Boto.

We use several AWS services including Route53 for global latency-based routing, SQS and SNS, etc. You can check out our May AWS bill if you're interested in learning more: https://blog.cronitor.io/the-aws-spend-of-a-saas-side-busine...