Open Source Jotform Alternatives

HeyForm turns data collection into conversational forms that anyone can assemble, whether the goal is a survey, a quiz or a poll. It removes the usual tradeoff between a hosted form service and owning both the responses and the branding around them.

The project is a monorepo. A Node server and a React web app sit alongside a form rendering library, a JavaScript embed library and shared submission utilities used on both sides of the wire.

The builder covers the fields themselves and the work that follows a submission.

• Versatile inputs: text, email and phone fields alongside picture choices, date pickers and file uploads.
• Smart logic: conditional branching and URL redirection let a form adapt as it is answered.
• Integrations: webhooks, analytics, marketing platforms and automation tools such as Zapier and Make.
• Visual themes: fonts, colors and backgrounds matched to your brand, with custom CSS for deeper changes.
• Analytics and export: drop-off and completion rates on screen, results out as CSV.

Self-hosting is documented, including one click templates for several providers and a generic OpenID Connect setup for identity providers such as Authelia, Authentik or Keycloak. The hosted version, run by the two person team behind the project, is the quicker path for anyone who does not want to maintain a server.

OpnForm is an open source form builder. Its no-code editor covers the whole path from designing a form to reading the answers, with unlimited forms and submissions rather than a quota that quietly pushes you onto a paid tier.

Forms are assembled from a range of input types, text, date, URL and file uploads among them, and then embedded anywhere. Form logic decides what a respondent sees next, customization handles the look, and captcha protection keeps automated junk out of the results.

The rest of what the builder gives you.

• Email notifications: submissions arrive in an inbox as they happen.
• Integrations: Slack, Discord and webhooks receive the same events for anything more elaborate.
• Form analytics: view counts and completion behavior sit alongside the responses themselves.
• MCP server: a remote server lets AI agents create and preview a private form draft without a login, and OAuth adds workspace-aware management plus read-only submission search, statistics and exports.
• Local development: a minimal Docker setup and per-worktree scripts spin up an isolated environment with a seeded database.

Self-hosting is documented through deployment guides, and a managed cloud service handles support, backups and upgrades for teams that would rather not. The core is licensed under AGPLv3, with advanced features in a separate enterprise directory under a proprietary license that funds the work.

Running since 2006, LimeSurvey is an online survey platform used in more than 80 countries by businesses, academic institutions, teachers, students, governments and financial institutes. It covers the full cycle, from writing a questionnaire to analyzing what comes back, without a cap on surveys, questions or responses.

The editor carries more than 30 question types and over 900 templates, and surveys can be brought on brand with custom fonts, colors, logos, CSS and JavaScript. Skip logic and question branching decide what each respondent sees next, and a survey can run in more than 80 languages at once.

Beyond the editor, several capabilities matter for serious use.

• Distribution: share by public link, QR code or social post, or restrict a survey to invite-only personal links in closed access mode.
• Analysis: responses, statistics and data analysis tools, with export plugins for R and STATA XML.
• Integrations: SAML, LDAP, SURFconext, a REST API and RemoteControl over XML-RPC or JSON-RPC.
• Security: two-factor authentication, response anonymization and GDPR compliance.
• Accessibility: WCAG 2.0 compliance, which matters when a survey has to reach every respondent.

LimeSurvey is a self-hosted PHP application. It needs PHP 8.1.29 or newer with mbstring and PDO drivers, a PHP-ready web server such as Apache or nginx, and MySQL 8, MariaDB 10.3.38, PostgreSQL 14 or MSSQL 2019. The latest stable release is the recommended download, since the development repository may hold untested versions. The code is GPL v2.0 or later, and a hosted service exists for teams that want to skip the setup entirely.

Ikiform pairs a form editor with the analytics and delivery machinery around it, so a form, the submissions it gathers, its reporting and its outbound webhooks live in one product instead of three.

It is a Next.js 16 application on the App Router with React 19, Supabase behind it and Tailwind v4 for styling, using Base UI primitives through the shadcn CLI. Forms are published on a public slug or embedded elsewhere, and a Playwright suite covers the interaction paths and UI regressions.

The dashboard is organized around the work of running a form.

• AI builder: a chat driven builder drafts a form and edits it from a description.
• Analytics chat: submission analytics come with a conversational view that keeps its own history.
• Customization: appearance, themes and Google Fonts are set per form on a customize screen.
• Webhooks: inbound and outbound webhooks can be tested, resent and inspected in a log.
• File uploads: uploaded files are stored and their links refreshed when they expire.
• Admin area: an internal view lists accounts, the forms behind them and their submissions.

Local development runs on Bun, with an install, a copied environment file and one dev command before the app is serving. Ikiform suits a small team that would rather own the form stack alongside its own codebase than rent a hosted form product, and the roadmap is published on the project site.

Palform is a form builder whose entire codebase is public, marketing pages included, and whose responses are encrypted end to end. It keeps third-party scripts to a minimum and is free to use on the team's European servers, and the repository holds everything needed to operate the service.

Several Rust and JavaScript components make up the system. Rocket and SeaORM run the backend, Svelte runs the main app, and shared crates compile to WebAssembly for the frontend. The team chose Rust for stability rather than ease of feature work, and reports memory and CPU use close to nothing in practice.

The design choices worth knowing about are structural.

• Typed identifiers: database IDs are custom TSIDs with a per-resource prefix mapped to a Rust type, so passing the wrong kind of ID is caught in code.
• Generated bindings: TypeScript clients for the API come out of an OpenAPI generation step rather than being written by hand.
• WebAssembly modules: encryption and bulk analytics compile with wasm-pack because they run far faster than the JavaScript equivalents.
• PGP encryption: Sequoia handles form encryption and key management on both the backend and the frontend.
• Content sites: Astro and Svelte build the landing page while Docusaurus serves the blog and documentation.

Self-hosting is possible but not officially supported: there are no versioned releases yet, so the main branch carries no stability promise and no setup documentation. Contributions transfer copyright to the company behind the project, and the source is AGPL licensed.