OpnForm
Stack
OpnForm is an open-source form builder. It's an alternative to products like Typeform, JotForm, Tally etc.
Image details
Source details
Configuration
TypeComposelinuxjhumanj/opnform8380:80/persist : /portainer/Files/AppData/Config/opnformStandalone Install
Select an install method, to see config/commands for deploying OpnForm
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select OpnForm, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
Original stackfile
The compose file this template deploys, straight from its repo:
services:
opnform:
container_name: opnform
volumes:
- /portainer/Files/AppData/Config/opnform:/persist
ports:
- 8380:80
image: jhumanj/opnform
networks: {}
Or deploy it directly from the source:
git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/opnform.yml up -dMore install options in our documentation, or see jhumanj/opnform for app-specific guidance.
OpnForm
OpnForm is an open-source form builder.
Get Started
The easiest way to get started with OpnForm is to sign up for our managed service in the Cloud. You get support, backups, upgrades, and more. Your data is safe and secure, and you don't need to worry about maintenance or infrastructure. Check out our quick overview of cloud vs self-hosting.The cloud pricing page shows monthly equivalents for yearly billing by default. The Monthly / Yearly selector updates both the plan cards and the feature comparison table; yearly plans are billed annually.
Key Features
- 🚀 No-code builder with unlimited forms & submissions
- 📝 Various input types: Text, Date, URL, File uploads & much more
- 🌐 Embed anywhere
- 📧 Email notifications
- 💬 Integrations (Slack, Webhooks, Discord)
- 🧠 Form logic & customization
- 🛡️ Captcha protection
- 📊 Form analytics
For a complete list of features and detailed documentation, visit our Technical Documentation.
AI agents and MCP
OpnForm's remote MCP server lets AI agents create and preview a private form draft without requiring a login. OAuth adds workspace-aware form management and read-only submission search, statistics, and exports. The installable portable and native plugin package lives inplugins/opnform/. See the MCP integration guide.Quick Start
The easiest way to get started with OpnForm is through our official managed service in the Cloud.For self-hosted installations, please refer to our Deployment Guides. For local development, we provide a minimal Docker-based setup - check out our Docker Development Guide.
The client
npm run build also checks the public form bundle size and eager dependencies. This check reads .nuxt/dist/client/_nuxt, independently of Nitro's deployment output directory (including AWS Amplify's .amplify-hosting). Run its regression tests from client/ with node --test scripts/check-public-form-bundle.test.mjs.The public form budget is 425 KiB gzip. On 25 October 2026, the integrations-content update brought the unchanged
main build to 419.3 KiB, still within the old 420 KiB limit. The combined security fixes measured 421.7 KiB: an additional 2.4 KiB (about 0.6%). The previous baseline used 416.4 KiB of a 420 KiB budget. The new limit accepts this measured increase and restores comparable headroom without changing the forbidden eager-dependency checks. Regression fixtures verify that a route around 424 KiB passes and one around 426 KiB fails.Form list performance
The dashboard fetches lightweight summaries in batches of 50. The API keeps its default page size of 10 and its maximum of 100 for other callers. It paginates forms before loading view and completed-submission counts for the returned IDs. Historical views use an index onform_statistics.form_id, and the aggregate is explicitly aliased as total_views_count so the model uses the preloaded value.The index migration runs outside a transaction and uses
CREATE INDEX CONCURRENTLY on PostgreSQL to keep writes available. It also recovers an invalid index left by an interrupted build. Run this migration through Laravel normally; do not wrap it in an external transaction. MySQL and SQLite use the standard schema index migration.Codex worktrees
Codex creates an isolated local environment for each worktree. It uses a dedicated PostgreSQL Docker volume and local Laravel/Nuxt processes, so sibling worktrees do not share ports, data, or API configuration.Use the Codex
Start app, Reset DB, and Stop app actions when available. You can also run the scripts directly:./scripts/codex-worktree-setup.sh
./scripts/codex-worktree-up.shThe startup command prints the worktree-specific URL. Opening its root URL automatically signs in the local Codex admin (
[email protected] / Abcd@1234). The seed also creates three forms, including five completed submissions across two public forms, so the dashboard and submission screens are immediately useful. Reset only the current worktree database with:./scripts/codex-worktree-reset-db.shRun the browser suite against the running worktree with:
./scripts/codex-worktree-test-e2e.shDependency security
The API resolves dependencies for PHP 8.3.36; use a patched PHP 8.3 or 8.4 runtime compatible with the lock and runcomposer check-platform-reqs. The client requires Node ^22.22.3 || ^24.15.0 || >=26; CI and Docker use 24.22.1, also recorded in client/.nvmrc.Nuxt Content uses the native
node:sqlite connector, including on Amplify's Node 24 runtime. Its Zod dependency is pinned to the patched v4 line through a scoped npm override; keep that override until Nuxt Content updates its dependency range.Pinia 4 requires
@pinia/nuxt 1.x. Installing client dependencies also compiles better-sqlite3 13, so local builds need Python 3, Make, and a C++ compiler. Both client Docker build stages include these tools; the production stages stay separate.The executable npm audit policy is in scripts/npm-exceptions.json. Dependabot checks Composer, client npm packages, and GitHub Actions weekly, with up to three open version-update PRs per ecosystem. Compatible application updates are grouped; major application dependency updates remain separate except for the coordinated VueUse packages. GitHub Actions updates are grouped together. Security update handling is unchanged.
The lock requires node-forge 1.4.1 or newer. Its former RSA-verification exception has been removed; dated exceptions for other packages remain enforced.
Date fields
Clearing a date with a click, Enter, or Space keeps the calendar closed. Reopen it to choose another date.Editor history
The form editor shows whether changes are saved. For an existing form, Save Changes saves both its design and settings; changes to a published form take effect immediately. In Settings, use Save and close to save directly, or Close to return to the editor with your changes still pending. While saving, Settings cannot be edited or dismissed. Failed saves preserve the pending edits for retry, and validation errors lead to the relevant field editor. For a new form, Done applies settings without creating or publishing it. Leaving the editor with unsaved changes asks for confirmation.Clearing editor history uses the currently loaded form as the undo baseline and discards pending history updates. A subsequent edit can be undone back to that form without restoring an earlier loading state.
Submission file references
File fields accept temporary upload references. To retain an existing upload through a URL, send its valid, unexpired signed download URL for the same form and application origin. Refresh submission data to obtain a new URL if it has expired. A prefilled file configured in the editor is copied into submission storage under a fresh name for each submission; its shared source remains available. Other shared form assets and arbitrary external URLs cannot be used as submission uploads. Submission processing only moves files from temporary upload storage; it never moves shared form images.Spreadsheet exports
Spreadsheet exports preserve numeric zero values, account identifiers with leading zeroes, and Unicode. Null and empty fields remain blank.PDF template fields
The PDF editor removes zones linked to deleted fields and lists them before you continue. Save the template to keep the cleanup. Mappings retain field names when created or saved, so deleted fields can still be identified. Older mappings without a saved name appear as “Deleted field” with their page number.PDF output follows the template page order and dimensions. Zones near the bottom of a page stay on that page; text is clipped to the zone height rather than creating extra pages. The pagination cache version bypasses PDFs generated before this fix, without changing saved templates.
Support & Community
If you need help or have questions, please join our Discord community. For more information and assistance, check out the following resources:License
OpnForm is open-source under the GNU Affero General Public License Version 3 (AGPLv3) or any later version. You can find it here.Dual Licensing
OpnForm uses a dual-license model to make the project sustainable:- Core OpnForm (AGPL-3.0): The main application is free and open-source under AGPLv3, giving you the freedom to use, modify, and distribute it.
- Enterprise Edition (Proprietary): Advanced features under
api/app/Enterprise/are available under our Enterprise License and Enterprise Terms. These features help fund ongoing development and keep OpnForm sustainable.
By offering Enterprise features alongside our open-source core, we can continue to invest in making OpnForm better for everyone while keeping the project financially sustainable.
Security remediation rollout
See October 2026 deployment and compatibility notes before deploying the API/client changes.Form validation translations
Public submissions use the form's language for API validation messages. When adding a translated validation message, update the catalogs underapi/resources/lang/ for all languages in Form::LANGUAGES, preserving placeholders such as :attribute, :min, and :max.Run
vendor/bin/pest --filter=FormValidationTranslationsTest from api/ to check supported catalogs and render invalid date range, rating, selection, and Arabic file-type errors. The tests do not require a database. The catalog check excludes custom attribute aliases and the legacy password key, whose structure differs between Laravel versions. Client text coverage is checked separately by test/unit/form-locale-keys.test.ts in client/.Production performance
See runtime limits, caching and reproducible local measurements.Compare date fields in conditions
For a single date field's Equals, Before, After, On or before, or On or after condition, choose Fixed date to use the calendar or Field or variable to compare against another single date field or a computed variable returning an ISO date. This works in conditional logic and custom validation. Date ranges are excluded from reference selection. Relative conditions such as Within next X days still take a number of days. A comparison against an empty date does not pass.Date operands are validated on the server when saving the form. References must point to another existing single date field or a variable returning a date. At evaluation, both runtimes reject nulls, empty strings, non-string values, impossible dates, and non-ISO date text. Fields without time compare calendar dates, ignoring the time and offset carried by the input. Fields with time compare instants with timezone offsets applied; timezone-free values use UTC. Field references must have matching time settings. Fractional seconds use millisecond precision in both runtimes. For fields with time, equality compares the instant, so timestamps with different offsets can be equal. Optional empty fields need an explicit Is empty OR date comparison rule if blanks should pass.
Dependency audit overrides pin compatible glob consumers (v9+) to 14.0.3 and minimatch consumers (v5+) to 11.0.3. Legacy ESLint consumers retain minimatch 3.1.5 because its callable CommonJS API differs from v11. The exact advisory, version and paths are reviewed until 6 November 2026 in
scripts/npm-exceptions.json: the reported optimizationLevel >= 2 vulnerability
has no corresponding preprocessing phase in v3. Raw audit findings remain visible;
new versions, severities, paths and advisories still fail the gate.Serve OpnForm on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.
Proxying opnform.example.com to http://opnform:80
Add this to your Caddyfile
opnform.example.com {
reverse_proxy http://opnform:80
}Check the logs first
Nine times out of ten the logs tell you exactly what went wrong.
- In Portainer, go to Containers, click the container, then Logs. Or run
docker logs <container> - Exit codes help too:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Port already in use
If deployment fails with "Bind for 0.0.0.0:8380 failed: port is already allocated", something else on your server is using that port.
- Find what's using it:
sudo ss -tlnp | grep :8380 - Stop the other service, or pick a different host port. In
8380:80only the left number is yours to change, the right one belongs to the app.
Running but the page won't load
The container is up but nothing appears in your browser.
- Use your server's real IP:
http://your-server-ip:8380. The 0.0.0.0 link Portainer shows isn't a real address. - Give it a minute after first deploy, opnform can take a while to initialise.
- Make sure your firewall allows the port, e.g.
sudo ufw allow 8380
Permission denied on volumes
If the logs show "permission denied", the app can't write to its data folder on the host.
- Fix the ownership:
sudo chown -R 1000:1000 /portainer/Files/AppData/Config/opnform
Image won't pull
Test the pull directly on the host: docker pull jhumanj/opnform
- "manifest unknown" means the tag no longer exists. This template uses
latest, so try pinning a specific version instead. - "toomanyrequests" is the Docker Hub rate limit. Log in with
docker loginto raise it. - "no space left on device" means a full disk. Reclaim space with
docker system prune
"exec format error"
This means the image was built for a different CPU architecture than your server.
- This image supports:
amd64 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Stack won't deploy
Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.
- YAML only accepts spaces for indentation, a single tab breaks the whole file.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue on jhumanj/opnform
- Template not working: Open an issue on xneo1/portainer_templates
- This website not working: Open an issue on lissy93/portainer-templates
A Compose stack
OpnForm is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.
The app image
An image is the app packed up ready to go, everything OpnForm needs bundled into one download. This template pulls jhumanj/opnform, which Docker fetches once (about 434 MB) and then starts your own copy from.
Where the image comes from
Docker pulls its images from registries, public libraries of ready-built apps. OpnForm's comes from Docker Hub, published by jhumanj.
Version tags
The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is 1.2.6. Pin a specific tag if you would rather stay on one version.
Which machines it runs on
Every image is built for particular CPU types. This one ships for amd64, so it runs on regular x86 PCs and servers, though not ARM boards like a Raspberry Pi.
Ports
A port is the door the app answers on. A mapping like 8380:80 means it's reachable on port 8380 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:8380 in a browser. It opens:
8380:80, likely the web interface
Volumes
A volume is where OpnForm keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:
/persistfrom/portainer/Files/AppData/Config/opnformon the host
Networking
Nothing custom is set, so OpnForm sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
Container name
Once it's deployed, Portainer names the container opnform. That's what you'll spot in the containers list and use in commands like docker logs opnform.
Platform
The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.
Portainer app templates
Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set OpnForm up. Add the template list to Portainer once, then deploying OpnForm is a click rather than a wall of config.