FormDB vs Formcarry
FormDB and Formcarry are form backends with server-side validation. Compare free limits, rule types, integrations, team seats and API access.
FormDB and Formcarry are both form backends that store submissions from your own HTML forms and can validate fields on the server. The main difference is in what surrounds that: FormDB adds a visual builder, more rule types and direct database integrations, while Formcarry states that it stores data in the EU and supports custom SMTP.
At a glance
Feature | FormDB | Formcarry |
|---|---|---|
Free plan allowance | 250 submissions a month | 50 submissions a month |
Forms limit | Unlimited on every plan | 1 on the free plan, unlimited on paid plans |
Data retention | 30 days on Free, unlimited on paid plans, optional per-form limit | Per-form setting, from 30 days to forever |
Server-side validation rules | Yes, 24 rule types | Yes, 6 rule types |
Spam protection | Honeypot, keyword filters and custom rules, country and language filters, duplicate detection, IP blocking, built-in captcha or your own keys | Own detection, honeypot, reCAPTCHA, address blocking, rate limiting |
File uploads | Every plan, 100 MB to 50 GB storage, 10 MB to 250 MB per file | Paid plans, 1 GB to 30 GB storage |
Integrations | Webhooks, Slack, Discord and Telegram on every plan, Google Sheets, Notion, Airtable, Stripe and Zapier on paid plans, custom SMTP on Business | Webhooks, Zapier, custom SMTP |
Team members | 1 on Free, 3 on Starter, 5 on Growth, unlimited on Business, extra seats on paid plans | 1 on free, 3 on Starter, 5 on Basic, 20 on Premium |
API access to submissions | REST API with keys on paid plans | REST API with keys, plans not stated |
Auto-responder emails | Paid plans | On some paid plans |
Where FormDB is different
More validation rule types, set in a builder
Both products check fields on the server. Formcarry documents six rules: Required, Number, Email, Url, Contains and NotContains. FormDB has rules for length, patterns, allowed email and link domains, number ranges and decimals, date limits, weekends, file size, file types, file counts and selection counts. You add them in a visual builder, which also generates form code in HTML, React, Vue, Fetch and jQuery flavours.
A larger free plan
FormDB's Free plan accepts 250 submissions a month across unlimited forms. Formcarry's free plan accepts 50 a month on 1 form. Formcarry's documentation says spam counts toward the monthly limit on its free plan. In FormDB, flagged spam does not count on any plan.
Direct Google Sheets, Notion, Airtable and Stripe integrations
Paid FormDB plans write submissions directly to Google Sheets, Notion and Airtable and can link Stripe payments to a submission. These were not mentioned in Formcarry's documentation when we checked, which lists webhooks and Zapier as the routes to other tools.
Larger uploads per submission
Formcarry's documentation lists a 10 MB limit per file. FormDB allows 10 MB per file on Free, 25 MB on Starter, 100 MB on Growth and 250 MB on Business, and lets you set your own per-file size and type rules. FormDB also accepts files on its Free plan, with 100 MB of storage, while Formcarry lists file uploads on paid plans. Paid FormDB plans scan uploads for viruses.
Where Formcarry is the better choice
- Stated EU storage. Formcarry says submissions, files and account data are stored in EU data centers. FormDB does not state an EU data region.
- Your own email server. Formcarry supports custom SMTP. In FormDB, sending through your own SMTP server requires the Business plan.
- Webhooks per form. Formcarry allows up to 10 webhooks per form. FormDB allows 1 on Free and 3 on Starter, and 10 from Growth.
Which should you choose?
Choose FormDB if you want a wider set of validation rules and a builder to manage them, more free submissions, larger uploads, or submissions written directly to Google Sheets, Notion or Airtable.
Choose Formcarry if you need a stated EU storage location, or if sending through your own SMTP server matters and FormDB's Business plan is more than you need.
Switching from Formcarry
- Create a form in FormDB and copy its endpoint. Follow the quickstart.
- Replace the Formcarry URL in your form's
actionwithhttps://api.formdb.io/f/your-form-id, and keepmethod="POST". See HTML forms. - Keep or add a hidden text input named
_gotcha. Both products use this name for the honeypot. Then recreate your validation rules in the FormDB builder. - Send a test submission and check your FormDB inbox.
Past submissions are not imported. Formcarry offers CSV and JSON export, so download a copy first if you need the history. For FormDB prices, see our pricing page.
Details about Formcarry come from their public pricing and documentation pages as of November 2026 and may have changed. Check their site for current information.