Self-hosted forms and surveys in 2026: revisit Formbricks, LimeSurvey and OpnForm before you collect another response through Google Forms or Typeform
Almost every organisation collects data through forms. Admission enquiries, job applications, event registrations, customer feedback, employee pulse surveys, vendor onboarding. Most of this goes into Google Forms or Typeform because they are quick to start. Over time, the responses pile up in someone’s personal account, links are shared on WhatsApp, and nobody remembers which form holds phone numbers or Aadhaar details of real people.
Self-hosted form tools offer another path. You run the software, the responses sit in your own database, and you decide who can see them. In 2026 three open source projects come up often: Formbricks, a survey and experience management platform written in TypeScript; LimeSurvey, the long running PHP survey tool used by researchers and governments; and OpnForm, a newer form builder built on Laravel and Nuxt that feels close to Typeform.
This post revisits all three calmly. We look at history, licences, stack, features, operations, backups, security, the Indian consent angle, and when not to adopt each. We did not run a hands-on drill for this post. Facts below come from the official GitHub repositories, licence files, release pages and README files, read on 3 November 2026. Where we write from general knowledge, we say so.
A scenario to keep us honest
To keep the discussion practical, we use an invented organisation. This organisation is illustrative only; any resemblance to a real one is accidental.
Kochi Coastal Skills Foundation (invented) is a non profit in Kerala that runs vocational training for young people in fishing villages: marine engine repair, tailoring and basic computer skills. It has about 30 staff, one IT person named Anand, and a part time volunteer developer. Today:
- About 25 Google Forms are in use, created by different coordinators from their own accounts.
- Admission forms collect name, age, phone number, parent details, caste certificate details for scholarships, and sometimes a photo of an ID card.
- A Typeform account on a paid plan is used for donor feedback and a yearly impact survey.
- Some trainees fill forms on shared phones with weak network, often in Malayalam.
- A CSR funder has asked how trainee data is stored, who can access it, and how long it is kept.
The foundation wants one place for forms, clear access control, and an honest answer for the funder.
Where these tools came from
LimeSurvey
LimeSurvey is the oldest of the three. The licence header in its repository says “Copyright 2003 LimeSurvey Project Team / Carsten Schmitz”, and the README says the team has been doing this “since 2006”. The GitHub repository was created in January 2012 and had about 3,800 stars when we checked. It moves fast for an old project: tags on GitHub show the 7.0.0 release (tag 7.0.0+260526) followed by a long run of 7.x releases up to 7.9.0 (tag 7.9.0+261029), while 6.17.x tags (6.17.14 to 6.17.19) were also published alongside the 7.x line.
Formbricks
Formbricks is maintained by Formbricks GmbH. The repository was created in June 2022 and had about 13,200 stars on 3 November 2026. Release pages show 6.0.0 on 21 September 2026, 6.1.0 on 19 October 2026, and 6.1.3 on 2 November 2026, with 6.0.5 also published on 27 October for those still on the 6.0 line. The 6.1.3 notes are mostly dependency and security bumps, including running the Docker image on Node 24.22.2 and upgrading the Better Auth library.
OpnForm
OpnForm is the youngest in style, though its repository dates to September 2022. The first release on GitHub is v1.0.1 from August 2023. It had about 4,000 stars when we checked. The project releases very often: v2.3.0 on 11 August, v2.5.0 on 2 September, v2.6.0 on 14 October, v2.7.0 on 27 October, v2.8.0 on 28 October, and v2.8.3 on 3 November 2026. The v2.8.3 notes describe tighter URL filtering for webhooks and PDF images, rejecting Teredo IPv6 addresses, and say plainly that access to internal services through this gap “has not been demonstrated”.
Licences, in plain words
Licences matter here because forms often end up embedded in websites and apps.
LimeSurvey
- Licensed under GPL version 2 or later, as stated in the repository licence file.
- There is a hosted cloud service from the company, but the community edition you download is the full open source product.
Formbricks
- The core is AGPL 3.0.
- Code under
apps/web/modules/eeis under a separate enterprise licence defined in that folder. - The SDK and survey packages (
packages/js,packages/android,packages/ios,packages/api,packages/surveys,packages/survey-ui) are MIT, which is helpful if you embed surveys in your own app. - In practice: the open core is usable, but some features live in the enterprise folder. Check which features you need before planning, because the exact split changes between releases (this last point is general knowledge, not checked feature by feature).
OpnForm
- The core is AGPL 3.0.
- Code under
api/app/Enterpriseis under a separate enterprise licence. - Same advice: list the features you need and confirm they are outside the enterprise folder.
What AGPL means for you
From general knowledge: AGPL lets you run and modify the software freely. If you modify it and offer it to users over a network, you must make your modified source available to them. For an organisation running an unmodified copy for its own forms, this is rarely a concern.
How each is built
LimeSurvey
- PHP application. The README lists PHP 8.1.29 or newer with mbstring and PDO drivers.
- Web server: Apache 2.4 or newer, nginx 1.1 or newer, or any PHP ready server.
- Database: MySQL 8.0 or newer, PostgreSQL 14 or newer, MariaDB 10.3.38 or newer, or MSSQL 2019 or newer.
- This is the classic LAMP style. Any team that has run WordPress or Moodle will find it familiar.
Formbricks
- TypeScript and Next.js web application (Next.js from general knowledge of the project; the repository language is TypeScript).
- The official Docker Compose file uses PostgreSQL with pgvector (image
pgvector/pgvector:pg18) and Redis, with a comment saying you can point it at an external Redis or Valkey instead. - Docker is the expected way to run it.
OpnForm
- Backend in Laravel (PHP), frontend in Nuxt (Vue), as described in the README.
- The official Docker Compose file runs separate API and client images, Redis 7, PostgreSQL 16 and nginx.
- The README notes MySQL and SQLite paths for some migrations, but PostgreSQL is what the official Compose file uses.
Features that matter for a forms team
LimeSurvey
- From its README: 30+ question types, 900+ templates, 80+ languages, skip logic and branching, closed access mode with personal invite links, statistics, a RemoteControl API over XML-RPC and JSON-RPC, two factor authentication, plugins, and integrations with SAML and LDAP.
- The README claims WCAG 2.0 compliance and GDPR compliance. These are the project’s own claims.
- Strong fit for long surveys, research, multilingual work and invite only panels.
- From general knowledge: the editor feels older and denser than the other two, and new staff need some training.
Formbricks
- Built around surveys: link surveys, website surveys and in app surveys triggered by user actions, using its SDKs.
- Good for product teams asking “why did you cancel” or “how was onboarding” inside an app.
- Webhooks and integrations to push responses elsewhere (details from general knowledge).
- Its strength is feedback at the right moment, not long admission forms.
OpnForm
- A clean, Typeform like builder: drag and drop fields, logic, file uploads, webhooks, and PDF generation (PDF and webhook features are visible in its release notes).
- The release notes also mention AI form generation, including for guests on the hosted service.
- Good for registrations, applications and enquiry forms that non technical staff create themselves.
Operations
Installation
- LimeSurvey: download the stable release from the official site, unzip onto a PHP server, run the web installer. Can also run in containers, but the classic way is still common.
- Formbricks: use the official Docker Compose file, set the required environment values (the Compose file refuses to start without
POSTGRES_PASSWORD), and put it behind HTTPS. - OpnForm: use the official Docker Compose file. Note that it uses
latestimage tags by default. Pin a specific version tag in production so an upgrade happens only when you choose.
Upgrades
- All three release often. OpnForm had six minor releases between August and early November 2026. LimeSurvey had more than twenty 7.x tags in a few months.
- Plan a monthly upgrade window. Read release notes, take a database backup, upgrade a staging copy first if you can.
- For Formbricks, follow the supported line. The project backports fixes to both 6.0 and 6.1, which shows that staying on a minor line for a while is possible.
- For LimeSurvey, decide whether to stay on 6.x or move to 7.x. Do not jump major versions in the middle of a running survey season.
Monitoring
- Watch disk space, especially where file uploads are allowed.
- Check that email (for invitations and notifications) is actually being delivered. A form tool that cannot send confirmations quietly fails.
Backups
Form data is often the only copy of the information. Treat it seriously.
- Database: daily dump of MySQL or PostgreSQL, kept off the server, encrypted.
- Uploaded files: LimeSurvey keeps uploads on disk; OpnForm and Formbricks can use local storage or S3 compatible storage depending on configuration (storage options from general knowledge). Back up whichever you use.
- Configuration: keep the
.envfile and Compose file in a private repository or a secrets store, never in a public one. - Restore test: once a quarter, restore to a fresh machine and open a few real responses. A backup that was never restored is only a hope.
- Retention: delete old responses on a schedule. Backups should also expire, otherwise deleted data lives on in old dumps.
Security
Exposure
Forms must be public, but the admin panel need not be. Where possible, restrict admin URLs to office IPs or a VPN, and keep only the public form routes open.
Accounts
- Turn on two factor authentication. LimeSurvey lists it as a feature.
- Use SSO where available. LimeSurvey supports SAML and LDAP. Formbricks has a SAML database setting in its Compose file, which suggests SSO support, though some SSO features may sit in the enterprise licence (general knowledge, check before planning).
- Give each coordinator their own account. No shared admin password.
Advisory record
- On 3 November 2026 the GitHub security advisory API listed one published advisory for Formbricks and none for OpnForm or LimeSurvey. This only covers advisories published on GitHub. LimeSurvey tracks issues on its own bug tracker, and from general knowledge it has had several CVEs over the years, as any twenty year old web application would.
- OpnForm’s v2.8.3 notes show the team actively closing server side request risks in webhook and PDF features. That is a good sign, and also a reminder: features that fetch URLs need careful network rules.
Uploads and spam
- File uploads are the highest risk. Limit types and sizes, scan if you can, and never serve uploads from the same domain as the admin panel without care.
- Public forms attract bots. Use a captcha or rate limiting on high traffic forms.
The Indian context: consent and the DPDP Act
This section is written from general knowledge of the Digital Personal Data Protection Act, 2023 and its rules. It is not legal advice and was not checked line by line against the statute.
- A form is often the exact point where consent is collected. The notice should say plainly what data is collected, why, and how to withdraw consent.
- Collect only what you need. If a scholarship needs a caste certificate number, ask for it only on that form, not on every enquiry form.
- Data about children needs extra care. Many training and school forms collect data of people under 18, and the Act expects verifiable consent from a parent or guardian.
- Keep a record of consent: which form version, what text, when it was submitted. A simple consent checkbox stored with the response helps.
- Allow people to ask for correction or deletion, and have a way to actually find and delete their responses.
- Delete data once the purpose is over. A retention period per form is a good habit.
- Self-hosting does not make you compliant. It only gives you control. Where the server sits, who can log in, and how long you keep data are still your responsibility. Hosting inside India is often a comfort for funders, though the Act does not make it a blanket requirement (general knowledge).
When not to adopt each
Do not choose LimeSurvey if
- Most of your forms are short registrations and you want staff to build them without training.
- You want a modern, mobile first look out of the box with no theme work.
Do not choose Formbricks if
- You mainly need long admission or application forms with file uploads. It is strongest at in app and website feedback.
- You need features that turn out to be in the enterprise folder and cannot pay for a licence.
Do not choose OpnForm if
- You need large research surveys with panels, quotas and complex statistics. LimeSurvey is better there.
- You cannot keep up with frequent releases and pin versions carefully.
Do not self-host at all if
- Nobody can own upgrades, backups and restore tests for the next three years.
- You have a handful of forms with no personal data. A hosted tool under an organisation account may be simpler.
Back to Kochi Coastal Skills Foundation
Here is a calm recommendation for our invented organisation.
- Inventory first. List all 25 Google Forms and the Typeform account, who owns each, what personal data each collects, and how long responses go back. Move ownership of every form to an organisation account immediately, even before any migration.
- Pick OpnForm for everyday forms. Admissions, event registrations and enquiries are short forms built by coordinators. OpnForm’s builder is the easiest for them. Run it with the official Compose file on one small VM, but pin the version tag instead of
latest, and keep the admin panel behind a VPN. - Keep LimeSurvey in mind for the yearly impact survey. If the CSR funder wants a long multilingual survey with Malayalam and English versions and invite only links for trainees, LimeSurvey handles that better. Do not run two tools from day one; trial it when the next impact survey is due.
- Skip Formbricks for now. The foundation has no product app where in app surveys would help. Revisit if they launch a learner app later.
- Fix the data before moving it. Do not copy old responses with ID card photos into the new system. Export, keep what the scholarship process still needs, and delete the rest from Google Drive.
- Write a one page data note for the funder. Where the server is, who has access, the backup schedule, the retention period per form, and how a trainee can ask for deletion.
- Test on shared phones with weak network. Before admissions season, ask a few coordinators to fill the new forms on the same phones trainees use.
The goal is not to remove Google Forms in a week. The goal is to know where trainee data lives and who can see it.
Key takeaways
- LimeSurvey is the mature research grade survey tool. Formbricks is the product feedback platform with in app surveys. OpnForm is the friendly Typeform style form builder.
- LimeSurvey is GPL 2 or later. Formbricks and OpnForm are AGPL 3.0 cores with separate enterprise folders, so check where your must have features live.
- All three release frequently. Pin versions, back up, and upgrade on a schedule.
- Protect the admin panel, limit uploads, and keep each user on their own account.
- Under the DPDP Act, clear consent text, minimal fields and real deletion matter more than which tool you pick.
Learn what each tool is good at, unlearn the habit of creating forms from personal accounts, re-learn data minimisation, practise with one pilot form, and apply it before the next admissions season.
Sources
- Formbricks repository and releases: https://github.com/formbricks/formbricks
- Formbricks licence: https://github.com/formbricks/formbricks/blob/main/LICENSE
- LimeSurvey repository and tags: https://github.com/LimeSurvey/LimeSurvey
- LimeSurvey website: https://www.limesurvey.org
- OpnForm repository and releases: https://github.com/OpnForm/OpnForm
- OpnForm licence: https://github.com/OpnForm/OpnForm/blob/main/LICENSE
Releted Posts
Self-hosted newsletters and email campaigns in 2026: revisit listmonk, Mautic and Keila before you send another campaign through Mailchimp
Email is still the one marketing channel that a company really owns. Social platforms change their feed rules, ad costs keep rising, but a list of people who asked to hear from you stays with you.
Read moreOpen-source ERP in 2026: revisit ERPNext, Odoo Community and Dolibarr before you move another business onto a new ERP
An ERP is the one application that touches almost everyone in a company. Sales raises the order, stores issue the material, production books the output, accounts raise the invoice and file the tax return, and management reads the numbers at month end.
Read moreSelf-hosted CRM in 2026: revisit Twenty, EspoCRM and SuiteCRM before you move another sales pipeline off Salesforce
A CRM looks simple from outside. It is a list of companies, contacts, deals and follow ups. Inside most organisations, though, the CRM slowly becomes the record of every customer conversation, every quote, every renewal date and every promise a sales person made.
Read more