Saasufy supports rollover deployment. It's serverless, meaning you don't need to write any server-side code. You just define the collections, schema, views/filt

Saasufy supports rollover deployment. It's serverless, meaning you don't need to write any server-side code. You just define the collections, schema, views/filters, access controls then deploy. It's radically different from anything that's out there. It makes it impossible to introduce back end bugs or security flaws (assuming that access control rules are defined correctly; which is a lot easier to verify via a simple UI than reading thousands of lines of back end code). Look at this app I built with it on the side: https://www.insnare.net/ https://www.insnare.net/ It's only ~1300 lines of custom code in total. Most of it is HTML. Throughout the entire process from start to finish, I never encountered a single back end bug. Deployment essentially never fails; the UI doesn't let you do anything invalid and it helps avoid inefficient queries. Yet look at the complexity of what kinds of queries and filters I can run against the data and all the different views. It has almost 1 million records... Indexes are not even fully optimized. Look at the data that's behind access control/associated with specific accounts (e.g. the Longlists). Go ahead and try to bypass access controls... The WebSocket API is documented here: https://github.com/Saasufy/saasufy-components/wiki/WebSocket-API https://github.com/Saasufy/saasufy-components/wiki/WebSocket... It would normally have taken months and tens of thousands of lines of code (front end and back end) to build that. The value is there in terms of security, development efficiency, maintainability etc... The hard part is getting people to see it.