Who keeps the form running?
With OpnForm Cloud, OpnForm runs the form service. With a self-hosted installation, your team runs it and takes care of updates, backups and restoring access if the server goes down.
The core is open source under the AGPL. Some enterprise features use a separate license. Check which features your chosen installation includes before promising password protection or branding changes to a client.
Who can open the form and where do requests appear?
By default, anyone with the form address can answer. On an eligible plan you can set a password. Try the link in a private window because the editor can see it while signed in without entering the password.
Open Submissions to check what arrived. Export downloads answers as a CSV, a file of rows and columns you can open in a spreadsheet. Keep any needed original uploads and form settings separately when moving a workflow.
How do you test that a request arrived?
Create a disposable form with a made-up request field. Before opening it as a visitor, confirm that no real accounts, emails, files or connected services can be used by the form. If you can’t confirm that, review the settings and write out the expected steps on paper.
- Say what happens nextSet the success message to say the sample request was received and what a person should expect after that.
- Check both sidesSubmit a fictional request through the isolated link. Look for that message as the visitor and a matching record under Submissions as the owner.
- Keep a sample copyExport the sample and open the CSV to see whether the columns are enough for the person who will handle requests.
What can change the cost?
Cloud Free lists unlimited forms and submissions, one workspace and required OpnForm branding. Password protection, a custom domain and removing branding are listed on Pro. Upload quotas still apply.
The self-hosted core has no software subscription fee. Budget for the server and the work of maintaining it. Check licensing separately if you need enterprise features.