CauliCloud
Free AWS cost monitoring
I developed notifications for Slack, but it turns out that Slack wants me to have tested this out on 11 different Slack accounts before submitting the app for review, I have only tested it out on 1 so far (mine)!
So I've now put the Slack functionality behind a feature flag and going to make it an invite only feature until I have 11 accounts to test with.
So, if you're interested in free AWS cost notifications to your Slack every month, give me a shout!
I started developing this product last year, and built an MVP using serverless technologies: Lamdba, DynamoDB & API Gateway.
To be honest the developer experience wasn't great for me. I used TFCDK for IaC and the development feedback loop was incredibly slow, maybe 10 minutes when you made an API change. There could have been more tools to use to make this easier. Because of this I lost interest in the project and basically gave up on it.
Recently this problem came around again, I believe companies don't fully understand where they are spending their money and what they can do to save cloud computing costs.
So I decided to completely re-develop the product using NextJS & PostgreSQL. Developer experience has been much better and I've developed the MVP, which is now publicly available.
The MVP is a simple cloud cost monitoring application which sends an email at the beginning of the month with some basic insights of last months spending.
After working with AWS services for a nunber of years, for a company that used AWS pretty extensively, I realised that we didn't have an easy way to proactively monitor the costs of our AWS resources.
So I came up with CauliCloud, an easy and free way to monitor AWS costs, which can be filtered by account and team.
1 Comment
I think you forget to highlight the lead here. You are building a replacement for the AWS cost explorer and likely a competitor to: https://www.cloudzero.com/blog/aws-cost-explorer-alternatives.
Slack just doesn't let you list it in the app marketplace immediately, but people can still install it, there is no reason to have it behind a feature flag, that just adds unnecessary extra effort for both you and your customer.