Hi WebDev,
during the last couple of years I'e build linkedrecords.com. Its a litte mit different to what you might be used too so you have to keep an open mind.
LinkedRecords makes all of this possible. It's not just another BaaS - it's a fundamentally different architecture for building collaborative applications.
WolfOliver introduces LinkedRecords, a new Backend as a Service (BaaS) platform that offers unique features like allowing users to choose where their data resides and integrating authorization into every operation. The platform aims to simplify building SaaS applications and enhance security. A user, electricity_is_life, questions the benefits of this approach compared to traditional self-hosted solutions, expressing concerns about security and compliance.
"What if you operate a SaaS on your infrastructure and your users could choose where their data lives - on their own infrastructure, in their own jurisdiction?"
I read the explanation of this on your website but I still don't really get it; why would a customer want that vs a normal self-hosted product where they host the UI in addition to the backend? Using a cloud-hosted UI seems like it would introduce a lot of security and compliance issues, and if the customer is already hosting the entire backend themselves It seems like they could pretty easily host the static UI server too.