Show HN: I just made my profitable online form builder open-sourced
An online form builder that was previously run as a profitable SaaS has been released under an open-source license, prompting debate over the motives, benefits, and legal nuances of using GPL/AGPL for such a product. Commenters weigh the trade-offs between free self-hosting and paid hosting, with particular interest from organizations seeking privacy-friendly, self-hosted alternatives to Google Forms and Typeform, and concerns about AGPL obligations for derivative or hosted services. Technical choices like NestJS, MongoDB, and Redis, as well as potential integrations with tools like Nextcloud and NocoDB, are also examined in terms of complexity, openness, and suitability for long-term maintenance.
Motivation for Open-Sourcing & Business Impact
- Author says goal is global collaboration, faster innovation, transparency, and trust.
- Project is already generating satisfactory revenue; open-sourcing is partly strategic/marketing but “not the main reason.”
- Some view this as a clever way to shrink the commercial market: competitors must beat a free, open-source baseline.
- Others see it largely as free advertising via HN, but there’s pushback that this dismissal is overly cynical.
License Choice & Legal Ambiguity
- Initial confusion over GPL vs AGPL; repo license changed over time.
- Docs page previously tried to “explain” GPL with extra conditions that don’t fully match GPLv3, leading to criticism that it’s misleading.
- Several argue AGPL is a better fit for a SaaS form builder and explicitly allows attribution requirements.
- One commenter stresses AGPL is only “dangerous” if you want to sell closed derivatives; others praise AGPL as ideal share-alike for networked apps.
“Meaningful Implementation” & Dependencies
- Skepticism from some that the “real” SaaS infrastructure remains proprietary, so “open source” may confuse users.
- Counterpoint: even with proprietary dependencies (MongoDB, Redis), source availability enables audits, forks, and replacement of components with open alternatives.
Self-Hosting, Privacy, and Integrations
- Strong interest from organizations that must self-host for privacy or policy reasons.
- Requests for integrations with Nextcloud, NocoDB, and other self-hostable tools; author is open to collaboration and asks for issues to be filed.
- Discussion of business models like charging for admin UIs or higher-tier features to support open core.
Technical Stack & Framework Debate
- Project uses NestJS and MongoDB; author later suggests they might choose MySQL/Postgres instead today.
- Extended debate on NestJS:
- Fans praise DI, structure, and productivity, especially for Angular/Java backgrounds.
- Critics call it overengineered, boilerplate-heavy, “Java for Node,” with brittle DI errors and too much magic.
- Some prefer lighter stacks (Express/Fastify, itty-router + Zod, RoR with Turbo/Stimulus).
Use Cases & Alternatives
- Interest from people building or using form tools for clubs, associations, and privacy-sensitive orgs.
- Mentions of alternatives: LimeSurvey, FramaForms, Grist, formbricks, NocoDB, and various custom/SaaS form builders.