Hacker News Reader

A lot of what we're trying to do is abstract some of the backend systems to allow for quick building. When you make a form, we host it on our servers, provide an accounts system for inviting team members and a permissions system for controlling access. Right now we're working on securely implementing both custom SQL queries and javascript-based scripting for backend validation and frontend customization.

View on HN

Ok, so for arguments sake it's a persistent form builder rather than anything really to do with building things for databases?

We're still working on exposing lower-level operations to advanced users. I'd still say we're a database builder, since we provide a system for making relational connections, and allow all CRUD operations on records. A form builder would probably only provide Create.

The accepted keywords for this kind CRUD-application builder are pretty generic, to be honest. The biggest one that I see used is "Online Database", which is so broad it's nearly meaningless.

I also thought the form builder was going to output Postgres (or any database) SQL to create the tables, fields, and relationships.

Reply on news.ycombinator.com