| > DX that abstracts over where the tenant data actually is This goes against any of the main items that @jph closed with: COMPLIANCE. So - abstracting the implementation complexity is difference than abstracting the "where data lives" - especially with Compliant requirements such as SOX and HIPAA, wtc. -- Its been a while but I've done some significant sized HIPAA and SOX, SAS70 and other compliance audits - and one of those reqs is "data retention for ~7 years" in many compliance laws... and so abstracting where data resides no beuno. (Surely you didnt mean that literally?) I am currently working on am 10DLC compliant SMS routing platform... and so I get to dive back into compliance - and I know already I have to know where all my flows tick KPIs in a way I can visibly and empirically document life-of-a-data And "Secure, Multi-tenant DB Routing as a Service." might be a better DNA for the tag-line. -- Also, I think I recall youre previous HN announcement for the AI scraping? But - in conjunction with this, it would be great to have a PWA-DB that is my own RLS multi-tenant for my personal data that I own all my records and companies have to subscribe to RLS access to my PII and blacklist all databrokers and scrape for who has my PII so I can actively manage who is accessing any of it - (Using both of your AI Scraper/Crawler tool and some-version of this seems like that could be a reality) (I love what youre doing - as other HNers said, Got to get the right CorpoSpeak bolted on here for BigBanko :-) |
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.