WHY WE CREATED GRAVWELL

1. Why We Created Gravwell We felt like our first blog post should start at the place all good stories start: the beginning. The Gravwell story begins in the trenches. Our founders were working in cybersecurity and large scale emulytics dealing with huge amounts of data while trying to investigate interesting questions like "what happens if

2. you reboot the internet?" or "how does malware propagate between hundreds of thousands of android devices?" Unfortunately, the analytics tool offerings available were causing some strife. Such massive amounts of data generation required some serious hardware to keep up, which was the fun part. The part that was not fun was the price tag that went up along with the amount of data. Hard decisions were made about which data was to be kept and which could be dropped on the floor -- a decision that goes against the ideals of big data analysis. Once the data was ingested we could start doing some fun analysis. Search queries were created, fine tuned, and launched...and then the waiting started as a single core lit up while much of the hardware did nothing. Like any good engineer we thought, "we can do this better". Unlike any good engineer, we were dumb enough to try.

3. A couple years have passed and Gravwell has moved from a side project to a part-time job to a full stack enterprise analytics platform. Our team is growing as we find more and more people who feel the same pain we felt. Modern analytics should handle binary data streams. They should not force customers to drop data because of licensing costs. And most importantly, they should not force you to know what you want before you have it. This blog will contain regular how-to analytics guides, usage tips, and release information plus any requests for content from our user base. We're excited to be launching Gravwell and look forward to helping people like us drink from the data firehose. Source: https://www.gravwell.io/blog/why-we-created- gravwell