john2360

That makes complete sense. A little correction from what David was saying: We don't want to abstract away the data stores; we want you to have complete ownership and observability of that. However, we want to make the infrastructure easy to manage, set up, and interface with. This is why we are making a big push to BYOC to allow you full data ownership. I like the direction of your tag line. Making sure that our security and privacy mission is loud and clear is important.

That is a super interesting idea. We have also been really tickled with the idea of owning our own data, and that is somewhat of the mission that drives us to make data security and privacy more accessible for developers. I love the connection to scraping.

I like your product. I think that data observability is super important for the future. Did you have to implement something similar to Fortress for your client?

Thanks for the question! In addition to helping with DevOps tasks, we built the infrastructure to help you securely manage your tenants in shared and dedicated instances. The shared instances have logical data separation, so there can be no data leakage. Our goal was it make it so developers did not have to worry about that infrastructure or security. - John

That is a super interesting question. I don't think we are too worried about cloud providers building this feature natively right now. While they can do that for specific database product lines, we don't think we will see that universally across their products. Our goal is to be database and cloud provider agnostic. So even if cloud providers build multi-tenancy natively, you will still have to manage it across all your different clouds. Thanks for the question!

We don't currently support local database development, but we are working on making that possible!

Exactly! That is a high level of what is happening in the background, but in the foreground, all you have to do is reference the tenant's ID. We also manage key rotations and other nitty gritties to secure your databases.

John here. Interesting! So, this is a per-session variable? Right now, we provide our customers with full logical separation in the same cluster. Do you have a preference for RLS or logical separation?

John, here. Thanks for the feedback. I see where you are coming from, and we will work on that tagline. Our goal is to be database and cloud provider agnostic.

Thanks for your thoughts! John here. We completely agree with you, and that's the premise of Fortress. We abstract away all the security risks and vulnerabilities of building your own solution.

Hi, this is John, one of the co-founders. Thank you so much for the feedback. We agree with you. We are in the process of getting our SOC2 compliance. We want to be the data infrastructure that is immediately HIPPA, SOC2, and GDPR. Similar to what Porter builds on your cloud, it is SOC2.