thumbnail_stacked-logs-1.png

stacked-logs-1.png

SaaS makes sense to manage server costs, launch large workloads and allow you to scale up or down. But handing off your critical data to a third-party SaaS is increasingly risky and complicated, when self-hosted solutions are getting cheaper and easier to run.

## The risk of privacy fatigue

IronCore's CEO, Patrick Walsh <a href="https://blog.ironcorelabs.com/warning-saas-privacy-debt-will-crush-your-roadmap-3869e79e3105?gi=88c98375b9" target="_blank">recently wrote a compelling argument</a> about not overlooking SaaS data privacy. He advocates not treating this as acceptable technical debt:

**Your data now requires extra protection, tracking, minimization, data retention, transparency around sharing and selling, and much more. Privacy laws tend to use broad but largely undefined terms and phrases like, "data protection by design and by default" without specifying what does or doesn't qualify as sufficient protection or sufficient design.**

Hit replay for a second when all things were SaaS. It makes a lot of sense to reduce server costs, manage large workloads and allow you to scale up or down. Yes, please. But now, we've added a new facet to consider: Where is your critical data living? This question is one that we need to ask ourselves. And, perhaps more importantly, it's one that our customers and partner ask of us. How are you protecting personally identifiable information (PII)? We all have to contemplate the tradeoffs with privacy and security. And, as Walsh says, "there's a significant privacy burden and fatigue" from the issue.

## Don't pay with your data

Evan Grabiner, founder and CEO of Aspecto (admittedly the AWS eco-system) puts a finer point on the issue in his [article:](https://medium.com/@eran_80147/is-data-privacy-killing-saas-2bbd096b1460)

**Natively, SaaS solutions require organizations to move data out of their hands, to the solution provider, with the result that organizations needed to trust a third-party service provider with their sensitive data, at the same time GDPR is telling them not to.**

Although Evan advocates for a virtual private cloud (VPC), I think there's another way. And we've built our technology to balance the need for data privacy with the need for, well, data.

Look at it this way, who do you want to have and use your data? These large SaaS platforms consume large amounts of your own data, on top of what you're already paying for usage. While you may think you're paying for data, I argue you're paying with your data. Logical considerations about privacy and compliance aside, the fact is, the one set of data you want to own and manage is your customer data.

## Own your data

First-party data stewardship is a founding principle at Resurface. Yes, we want to better understand how customers are using APIs, but we've also designed for information protection. Deep monitoring without a privacy-infringing footprint. Out customers own every bit of the entire API interaction – down to the granular individual detail. We're all about data independence, first-party data ownership, and customer-centric data management.

So, yes, SaaS isn't going anywhere. But it's worth looking at the kinds of data you're shipping to a third-party to ensure you can stay on top of ever-changing privacy regulations, and know the most about the customers you want to keep.

## See for yourself

Sign up for a demo to see how easy it is to monitor API calls with Resurface. Because your data is too valuable to share.


<a class="btn btn-primary my-3" href="https://resurface.io/calendly" target="_blank">Schedule Your Demo</a>


<p>SaaS makes sense to manage server costs, launch large workloads and allow you to scale up or down. But handing off your critical data to a third-party SaaS is increasingly risky and complicated, when self-hosted solutions are getting cheaper and easier to run.</p>
<h2>The risk of privacy fatigue</h2>
<p>IronCore's CEO, Patrick Walsh <a href="https://blog.ironcorelabs.com/warning-saas-privacy-debt-will-crush-your-roadmap-3869e79e3105?gi=88c98375b9" target="_blank">recently wrote a compelling argument</a> about not overlooking SaaS data privacy. He advocates not treating this as acceptable technical debt:</p>
<p><strong>Your data now requires extra protection, tracking, minimization, data retention, transparency around sharing and selling, and much more. Privacy laws tend to use broad but largely undefined terms and phrases like, "data protection by design and by default" without specifying what does or doesn't qualify as sufficient protection or sufficient design.</strong></p>
<p>Hit replay for a second when all things were SaaS. It makes a lot of sense to reduce server costs, manage large workloads and allow you to scale up or down. Yes, please. But now, we've added a new facet to consider: Where is your critical data living? This question is one that we need to ask ourselves. And, perhaps more importantly, it's one that our customers and partner ask of us. How are you protecting personally identifiable information (PII)? We all have to contemplate the tradeoffs with privacy and security. And, as Walsh says, "there's a significant privacy burden and fatigue" from the issue.</p>
<h2>Don't pay with your data</h2>
<p>Evan Grabiner, founder and CEO of Aspecto (admittedly the AWS eco-system) puts a finer point on the issue in his <a href="https://medium.com/@eran_80147/is-data-privacy-killing-saas-2bbd096b1460">article:</a></p>
<p><strong>Natively, SaaS solutions require organizations to move data out of their hands, to the solution provider, with the result that organizations needed to trust a third-party service provider with their sensitive data, at the same time GDPR is telling them not to.</strong></p>
<p>Although Evan advocates for a virtual private cloud (VPC), I think there's another way. And we've built our technology to balance the need for data privacy with the need for, well, data.</p>
<p>Look at it this way, who do you want to have and use your data? These large SaaS platforms consume large amounts of your own data, on top of what you're already paying for usage. While you may think you're paying for data, I argue you're paying with your data. Logical considerations about privacy and compliance aside, the fact is, the one set of data you want to own and manage is your customer data.</p>
<h2>Own your data</h2>
<p>First-party data stewardship is a founding principle at Resurface. Yes, we want to better understand how customers are using APIs, but we've also designed for information protection. Deep monitoring without a privacy-infringing footprint. Out customers own every bit of the entire API interaction – down to the granular individual detail. We're all about data independence, first-party data ownership, and customer-centric data management.</p>
<p>So, yes, SaaS isn't going anywhere. But it's worth looking at the kinds of data you're shipping to a third-party to ensure you can stay on top of ever-changing privacy regulations, and know the most about the customers you want to keep.</p>
<h2>See for yourself</h2>
<p>Sign up for a demo to see how easy it is to monitor API calls with Resurface. Because your data is too valuable to share.</p>
<p><a class="btn btn-primary my-3" href="https://resurface.io/calendly" target="_blank">Schedule Your Demo</a></p>


Why the Pendulum is Swinging Away From SaaS

Products

Docs

About

Legal