Forms & surveys 2 min read

Form.io vs Open Forms: API-first form engines compared

Two engines that serve forms through an API: Form.io for app developers, Open Forms for government services. Licences, setup and open questions.

Same idea, different audiences

Both projects treat a form as something served through an API rather than a stand-alone survey page. Form.io's README describes a combined form and API platform: you build forms with a drag-and-drop builder and embed them in Angular.js and React applications with a <formio> element. Open Forms lets administrators create smart forms exposed via an API and shows them inside an existing website through its JavaScript SDK.

The audiences differ. Form.io is pitched at developers building data management applications. Open Forms follows the Common Ground principles, with many plugins for government use and a focus on usability for end users and administrators. Open Forms also lists FormIO among its README keywords, so check its documentation for how the two relate.

What each adds around the form

Open Forms' plugin architecture covers submission backends such as Open Zaak, authentication schemes, payment providers, calendar apps and pre-fill services. Fields are pre-filled where possible and choices personalised for authenticated users. This repository holds the Admin UI and the API, with the SDK in a separate repository.

Form.io's README concentrates on running the engine: a management application on port 3001, structured logging behind a feature flag and a CLI that deploys local projects to the hosted Form.io platform. It doesn't describe built-in payment or authentication-provider integrations, so check the documentation at help.form.io if you need them.

Licences and running costs

Form.io moved from BSD to OSL-3.0 on 8 March 2020; the README calls it a copyleft, OSI-approved licence and says the aim is proper attribution when proprietary products build on it. Manual installation needs Node.js and MongoDB, and Docker Compose is offered for local runs.

Open Forms is open source and free to use under the EUPL, but its README is direct about running costs. Safe production use needs security updates, dependency and release management, quality assurance and vulnerability handling, and the stakeholders expect public organisations using it in production to contribute financially to its maintenance. No amount is given.

Before choosing

Form.io's captured commit, which is also the v4.11.0 tag, is dated 14 October 2026. Open Forms' 4.0.7 tag is dated 30 October 2026, and its main branch had a commit on 5 November 2026. Neither project publishes GitHub release entries.

Neither product was installed or tested for this comparison, and no hosted or enterprise prices were captured. A public body should clarify the Open Forms contribution expectation early; a software team should read the enterprise server documentation linked from Form.io's README to see what sits outside the open-source engine.

Sources

Form.io: formio-project · Evidence: documentation · Not checked

Open Forms: open-forms-project · Evidence: documentation · Not checked

Next step

Tools in this guide

All forms & surveys tools
All guides