The magic behind the clean up is Resoto's inventory graph - the graph captures the clean up steps for each individual AWS resource.
One of Resoto's users, D2iQ (now part of Nutanix), reduced their monthly cloud bill by ~78%, decreased from $561K to $122K per month. There's a step-by-step tutorial on our blog how they did it.
I don't mean to hijack Dashdive's thunder here though, congrats on the launch!
This is the first time I'm hearing about your company but I am already a huge fan of the tools you're building. I've had a need for most of them and next time I am met with those needs, I will use your tools. Please keep going!
The important piece of that vendor contract however was the integration with the point-of-sale system of each liquor shop. That's how Drizly knew what was on the shelf, and was able to sell inventory.
Drizly was one of our customers at my earlier company where I learned about these integrations. The world of POS systems is highly fragmented and arcane - there's no one system.
One asset that Drizly had developed was an integration platform that connected to any possible POS any of the liquor stores were using. No one else had done that. They just kept chipping away at it. Literally every sprint, they'd add more integrations. I believe the goal was 2 integrations per sprint. That includes data model, etc. to create the analytics downstream.
That integration platform was almost something like a natural monopoly. Hard to replicate by another party.
In 2016, I wrote a pretty detailed answer for "Spark vs. Redshift" question. This was in the very early days of what today I guess is called "the modern data stack"
The core of the answer was that cloud warehouses are not suitable for real-time use cases, because the batch processing and transformations take too long. If you want real-time, you need to pay up - hence Databricks / Spark. I did call out the fraud use case in that answer.
There were 1st generation ETL tools like Alooma that tried to go into the direction of streaming, and they pushed the limits.
Back then (we had built cloud warehouse monitoring tool), the closest to real-time I've ever seen any company get was IronSource. The time between an event and until that event was available in a dashboard was five minutes (they were using Redshift).
I'll stick my neck out and say that certain industries will be all over Artie, whereas others will shrug their shoulders.
The industries that I think will be all over Artie:
These are industries where a couple of minutes of difference in data recency can make a difference of millions of dollars. And you'll probably cost less than existing streaming solutions, which is obviously nice. But I think the real advantage will be simplicity.
I know you can't support all destinations at once, and need to go with where demand is. But I would expect that the Materialize and Clickhouse crowds are good target users for you.
As someone who drives around that area a lot, I can confirm that things do flatten out a lot. Everything West and East of I-5 is orchards, as well as North and South of I-80.
Quite a bit of that area is already water (the Delta), and we've seen during the heavy rains during 2017 (the period the article refers to) how the land around it can take a lot of flooding.
I've driven down the road from the dam to Winters, and the chutes I think would act like a giant water cannon. I wouldn't have high hopes for Winters. Driving down that road, I kept thinking "why would anyone buy real estate here?" - yet people do.
You probably need to add a zero to that amount, but it's a start.
Three years ago, I overheard a conversation of three CalFire employees on the way up to Tahoe.
The topic of the discussion was that "some" fire is desirable. And then I remember what the Chief said, and I'm roughly paraphrasing - "People tend to forget that CalFire's charter is to extinguish fires. [...]", and then hinting that unless that charter changes, more fuel will build up over time.
