Back to videos

Why I started Shoreline

Companies spend more on the people managing their cloud infrastructure than on the cloud infrastructure itself.
4 min

We all think that our AWS bills are intolerably large. But if you go to LinkedIn, you’ll find 1.3M people with titles such as SRE or DevOps Engineer. If you assume 150,000 per engineer, that's $200B – 2x the size of the cloud itself. What’s even crazier is that it’s growing at 40% YoY – the same rate as the cloud. Why?

The reason is that production-ops is done manually. Thanks to the cloud, developers are innovating and releasing stuff faster than ever. Automations in other steps of the software development lifecycle – building, testing, installing, and configuring – have further boosted this speed. Pity the poor person who's sitting at the tail end of this tsunami, responsible for managing things in production.

There's little to help them fix issues in production. A lot of DevOps companies work in the spaces of observability (detecting what's going on) and incident management (the processes around assigning, prioritizing, and deduplicating). But there hasn’t been much progress in helping engineers on-call reduce the number of incidents or solve them faster. It is still mostly manual. That’s why I created Shoreline. We help production-ops by:- bending the cost curve through automation- reducing the toil of operations for commonplace issues- expanding the number of people who can safely fix things that require some judgment- making it easy to debug things across your fleet for new issues that arise.

As a result:- companies save a lot of money and time on manual labor- production-ops people can lead a calmer life as they don’t have to wake up to incidents and escalations every single day.


View more Shoreline videos

Looking for more? View our most recent videos
2 min
Automate based on frequency not recency
Beware of recency bias when automating incidents!
1 min
How to Safely Fix Issues Without Escalation
The only real solution is incident automation.
1 min
Shoreline on Shoreline: Open Port Check
It's critical to close ports like 22 and 3389 that can be opened unintentionally in a development environment