🩺 Vitals
- 🟢 Last active: 2026-08-04
- 📦 Latest release: v2.2.4 (2026-07-28)
- 🐞 Open issues: 21
- 🌟 Stars: 3.5k
What do these metrics mean?
- Last active: when code was last pushed, as of our last check. The dot is green when that was recent, grey otherwise. A long gap can mean a tool is finished and stable, not only unmaintained.
- Latest release: the most recent tagged, packaged version the maintainers published. Not every healthy project tags releases.
- Open issues: unresolved reports and requests. A high number is normal for a popular project and is not a warning on its own.
- Stars: how many people bookmarked the project on its forge. A rough popularity signal, not a measure of quality.
🏗️ Profile
- Official: opnform.com
- Source: github.com/OpnForm/OpnForm
- License: AGPL-3.0 + Enterprise (Proprietary)
- Deployment: Docker | SaaS
- Data Model: PostgreSQL
- Jurisdiction: France 🇫🇷 / EU 🇪🇺 (Sole Proprietor)
- Compliance (SaaS): N/A (Undisclosed)
- Compliance (Self-Hosted): GDPR Ready
- Complexity: Low (1/5) - Docker Compose, single configuration file
- Maintenance: Low (2/5) - Standard Laravel + Nuxt stack, manageable update cadence
- Enterprise Ready: Low (2/5) - Core forms only; SSO, custom domains, and branding require Enterprise license
1. The Executive Summary
What is it? OpnForm is a no-code, open-core form builder designed as a self-hostable alternative to Typeform and JotForm. The AGPLv3 core is deployable via Docker Compose and covers the full form-building lifecycle: logic jumps, conditional fields, webhooks, and PostgreSQL-backed submission storage. It is maintained by a single developer, which drives rapid iteration but introduces a governance risk that enterprises must weigh before treating it as mission-critical infrastructure.
The Strategic Verdict:
- 🔴 For Enterprises Requiring Long-Term Stability: Caution. A sole-proprietor project with no corporate entity or governance board carries a high bus factor. SSO and custom domains are also Enterprise-paywalled, leaving the Community Edition short of standard enterprise identity requirements.
- 🟢 For Sovereignty-Focused Teams Replacing Typeform: Strong Buy. EU-based, no CLOUD Act exposure, Docker self-hostable, and genuinely capable for standard form use cases, at zero per-response cost and with full PostgreSQL access to all submission data.
2. The "Hidden" Costs (TCO Analysis)
| Cost Component | Typeform (SaaS) | OpnForm (Self-Hosted) |
|---|---|---|
| Per-Response Fees | Yes (tiered plans) | None |
| SSO (OIDC) | Included (Business tier) | Enterprise License Required |
| Custom Domains | Premium tier only | Enterprise License Required |
| Data Sovereignty | Typeform Cloud | 100% Self-Owned |
3. The "Day 2" Reality Check
🚀 Deployment & Operations
- Installation: OpnForm ships a pre-configured Docker Compose file covering the Laravel backend, Nuxt frontend, and PostgreSQL database. The stack is well-understood and most teams are operational on a single modest VPS with minimal setup time.
- Scalability: The Laravel backend handles standard form workloads efficiently. High-volume deployments benefit from separating the queue worker from the web process, both of which are defined in the default Compose configuration.
🛡️ Security & Governance (Risk Assessment)
- Jurisdiction & Geopolitics (France 🇫🇷 / EU 🇪🇺): The project is operated by a sole proprietor in France, placing all commercial and data operations under EU/GDPR jurisdiction. No US entity, no US CLOUD Act exposure. For teams replacing Typeform (US, owned by Momentive) or JotForm (US), this is a meaningful sovereignty upgrade: submission data never transits US-jurisdiction infrastructure when self-hosted.
- The Compliance Shift: Self-hosting shifts infrastructure security, PostgreSQL encryption at rest and in transit, backup management, and network security entirely to the operator. OpnForm provides form functionality and GDPR-relevant application controls; the infrastructure compliance burden does not come with the software. Organizations in regulated industries must independently implement encryption, access controls, and audit logging at the infrastructure layer.
- License Risk (AGPLv3 + Open-Core Trap): The AGPLv3 core is clean for internal deployment: no source-sharing obligation unless you distribute modified code externally or offer it as a public network service. The structural risk is the open-core model: OIDC SSO, custom domains, branding removal, and advanced integrations are permanently proprietary. Any organization requiring centralized IdP integration must purchase a commercial Enterprise license. There is no community path to these features. The sole-proprietor governance structure adds a compounding risk: roadmap, licensing terms, and long-term project availability are subject to one person's decisions.
4. Market Landscape
🏢 Proprietary Incumbents
- Typeform: The polished SaaS form builder with per-response pricing tiers; organizations evaluate OpnForm to eliminate usage-based billing and reclaim submission data from Typeform's US-jurisdiction cloud.
- JotForm: The high-volume enterprise form platform; teams evaluate OpnForm when they need a self-hostable alternative without JotForm's cloud data residency constraints.
🤝 Open Source Ecosystem
- Typebot: The conversational form alternative, best suited for chat-style flows and guided interview experiences rather than structured data capture.
- Formbricks: Optimized for in-app micro-surveys and NPS measurement; a stronger fit than OpnForm when the primary use case is product feedback loops rather than general-purpose forms.