Ultra simple back end for static websites

What does &quot;for static websites&quot; mean in the context of letting a website connect to a backend? That it can only connect at build time but not at request time?<p>Also interesting how the FAQ says &quot;Is App Backend secure? Yes [...]&quot; while the Privacy page says &quot;we cannot guarantee or warrant the security of any information you transmit to us and you do so at your own risk.&quot;<p>Tons of typos: &quot;make [it?] dynamic&quot; &quot;newseletter&quot; &quot;Peoples&quot; &quot;2 Project&quot; etc.<p>I believe non-article submissions should be prefixed &quot;Show HN&quot; although perhaps it&#x27;s not as simple as that.

Not much info to go on here..<p>From the FAQ: &quot;How does App Backend work? App Backend utilizes a database to store and manage table data. It offers APIs and tools to perform CRUD (Create, Read, Update, Delete) operations on tables and their respective records. This allows developers to easily handle data organization and manipulation in their small projects.&quot;<p>A.. database you say?<p>&quot;Is App Backend secure? Yes, security is a top priority for App Backend. It incorporates authentication and authorization mechanisms to ensure secure access to data. Additionally, it follows best practices for data encryption and implements measures to protect against common security vulnerabilities.&quot;<p>Both authentication AND authorization. Definitely secure.

Kind of interesting they put Strapi in the &quot;Peoples from these companies loving this software&quot; [sic] section, since it seems like direct competition to what Strapi offers if I understand it correctly.

I want to add what others noted... I love the idea, definitely something very interesting, maybe it could be better targeted.<p>Instead of running static gen on our machines, we have a backend which runs it... I think there is something in that idea.<p>If I was developing this idea, I would go for different integrations but again... I am not your target probably.