Keep the simple HTML endpoint and hand off deployment, backups, upgrades, scaling, file storage, and delivery operations. Form Plume gives production forms a managed path from first submission to connected workflow.
Side by side
FormTo and Form Plume start with the same useful idea: point an ordinary form at an endpoint. The difference is ownership after that POST. FormTo gives you an MIT-licensed application to deploy; Form Plume provides the receiving, storage, security, and delivery service as a managed product.
| Decision point | Form Plume | FormTo |
|---|---|---|
| Hosting model | Fully managed form backend Endpoints, storage, availability, upgrades, and delivery operations are included | Self-hosted Docker Compose stack You operate Caddy, a React frontend, Fastify backend, and PostgreSQL 16 |
| Setup and ongoing maintenance | Create an endpoint and ship No domain, reverse proxy, database secret, image rebuild, or migration runbook | Simple self-hosting, still your service Clone, configure secrets, launch Docker, then pull and rebuild for updates |
| Cost and capacity | Free hosted plan and published tiers 500 monthly submissions on Free and 10,000 on $12/month Pro | No software subscription or product cap MIT-licensed; practical capacity and cost depend on your server and operations |
| Inbox and data portability | Managed inbox, API, and exports Search submissions, track deliveries, export data, and apply retention controls | Searchable workflow inbox and PostgreSQL Statuses, notes, reply by email, analytics, plus CSV and JSON export |
| Notifications and integrations | Managed email plus broader automation Native destinations, Zapier, Make, MindCloud, and signed webhooks | Bring-your-own SMTP, Slack, Telegram, and webhooks JSON posts can target Zapier, Make, n8n, Discord, or a custom endpoint |
| Files and submission storage | Managed file uploads included on Free 100 MB on Free and 10 GB on Pro without provisioning a storage service | PostgreSQL submission storage The official feature list documents submission records and exports, not file uploads |
| Spam and security controls | Layered filtering with recoverable quarantine Four CAPTCHA choices, adaptive scoring, origins, rate limits, blocklists, and email hygiene | Honeypot, rate limits, and manual blocking Block email, domain, or IP; webhook SSRF, XSS, SQL injection, JWT, and password safeguards are documented |
| Maturity and support responsibility | A service team owns the platform Operational support and product continuity do not depend on your private fork | Young community-maintained project The repository showed six commits and one release; v1.1.0 shipped April 11, 2026 |
Where Form Plume pulls ahead
Self-hosting can be the right architectural requirement. When it is not, Form Plume turns the same endpoint workflow into less infrastructure, fewer recovery procedures, and more time for the product around the form.
FormTo makes initial deployment refreshingly direct, but your team still owns DNS, the Docker host, Caddy, PostgreSQL, secrets, logs, capacity, incidents, and every future rebuild. Form Plume removes that recurring operational assignment.
FormTo documents pg_dump and psql commands for backup and restore. A production plan must still schedule them, copy data off-host, monitor failures, encrypt archives, and rehearse recovery. Managed storage keeps that work out of the form project.
FormTo covers email, Telegram, Slack, and generic webhooks well. Form Plume adds managed files, signed payloads, recoverable spam review, native destinations, and broad app automation without asking you to maintain the receiving stack or connector credentials there.
Choose by situation
Marketing site owned by a small product team
Form Plume
The team can launch a reliable endpoint and connected workflow without adding a server, database, backup job, and patch schedule.
Organization requiring submissions on its own network
FormTo
Its MIT-licensed application and PostgreSQL database can run entirely on infrastructure the organization controls.
Agency collecting files across many client sites
Form Plume
Managed uploads, unlimited forms, central operations, and broader integration paths avoid repeating infrastructure work for every client.
Developer already operating a secure Docker platform
It depends
FormTo offers source control and infrastructure-defined capacity; Form Plume buys back maintenance time and supplies managed support.
FAQ
FormTo is an MIT-licensed application you run with Docker Compose, while Form Plume is a managed form backend. Both accept ordinary HTML form submissions; the key decision is whether your team or the provider should own hosting, storage, updates, availability, and delivery operations.
Yes. FormTo uses the MIT license and does not charge a SaaS subscription. It is not cost-free to operate: you supply compute, PostgreSQL storage, bandwidth, email delivery, monitoring, backups, security maintenance, and the engineering time needed to recover from failures.
Choose Form Plume when the form is important but running its backend is not a competitive advantage. It keeps deployment, scaling, backups, upgrades, upload storage, and delivery infrastructure out of your backlog while preserving the familiar endpoint workflow.
Usually. Create a Form Plume endpoint, replace the existing action URL, and keep the field names your frontend already sends. Test success behavior, notifications, spam controls, and every downstream delivery before directing all production traffic to the new endpoint.
Yes. Its README documents a searchable inbox where users can archive submissions, reply by email, add internal notes, and move work through new, in-progress, and resolved statuses. It also lists analytics, tags, filters, and CSV or JSON export. Form Plume provides a managed submissions dashboard with delivery visibility and export tools.
FormTo lets operators bring an SMTP provider and configure Telegram, Slack, and generic JSON webhooks. Form Plume manages notification delivery and adds native app destinations, Zapier, Make, MindCloud, and cryptographically signed webhooks for safer downstream automation.
FormTo documents honeypot detection, public-endpoint rate limiting, and blocking by email, domain, or IP. Form Plume covers those core layers and adds four CAPTCHA providers, adaptive scoring, time traps, origin controls, email hygiene, and a quarantine where suspicious submissions can be reviewed instead of disappearing.
The official FormTo feature list reviewed on July 9, 2026 documents PostgreSQL-backed submissions and CSV or JSON export, but does not advertise file attachments. Form Plume includes managed file uploads and 100 MB of storage on Free, with 10 GB on Pro.
It had recent activity when checked. GitHub listed v1.1.0 from April 11, 2026, adding dark mode and several security fixes. The repository was still small, with six commits and one release, so teams should evaluate its release cadence, issue response, upgrade testing, and their willingness to maintain a fork.
Choose FormTo when deployment on infrastructure you control is a firm requirement, source-level modification matters, and your team already has the operational discipline to secure, monitor, back up, patch, and restore the stack. Form Plume deliberately does not market a self-hosted edition.
One line. Zero backend.
