Skip to content
Français

Features

Everything here works today.

No roadmap on this page. These are the validators, conditions, delivery tools, and access controls in the product now, with the numbers counted from the code.

Start free

Counted from the code

15
native validators, plus Required and your own regex
11
condition operators, combined with all, any, and not
5
delivery attempts at most for temporary failures
10
email providers to connect, depending on the plan
9
alpha framework packages

Validation

15 native validators, enforced on the server.

Pick validators in the builder, and Formerie applies them to every submission, whatever client sent it. Errors come back per field, with stable codes.

  • Required, plus custom regular expressions up to 500 characters
  • Add several rules to a field
  • A browser can’t skip them, because the server decides
  • Contains
  • Country code
  • Domain
  • Email
  • Ends with
  • IP address
  • IPv4
  • IPv6
  • Doesn’t contain
  • Phone (E.164)
  • Postal code
  • Region code
  • Starts with
  • URL
  • UUID

Conditions

Rules that depend on the answers.

Use 11 operators, such as equals, in, greater than, is filled, and matches, and nest them with all, any, and not.

  • Show or hide fields based on other answers
  • Require or check a field only when a condition is met
  • Answers to hidden fields are dropped on the server
  • Send to a recipient only when a condition is met

Delivery visibility

Every attempt on record, with retries.

Temporary failures retry up to 5 times in all, 60 seconds apart. Each delivery shows as queued, retrying, delivered, or failed, with a readable reason and a next step.

  • Managers can retry a failed delivery from the submission
  • Send a real test before you publish, with readiness checks
  • Search and filter deliveries and submissions
  • Export metadata to CSV: answers stay out of the file
The Deliveries screen, with a status for each message.
A delivery’s path: queued, attempted, then delivered. A temporary failure retries automatically, and a failed delivery can be retried by hand.QueuedreceivedAttemptat the providerRetrytemporary failureDeliveredlogged A delivery’s path: queued, attempted, then delivered. A temporary failure retries automatically, and a failed delivery can be retried by hand.QueuedreceivedAttemptat the providerRetrytemporary failureDeliveredlogged

Senders, recipients, domains

Only verified addresses receive and send.

Recipients confirm by email, or are covered by a domain you’ve verified with a TXT record. The Free plan sends from notifications@mail.formerie.com.

  • Domain verification works on every plan
  • On plans that include them: your own sender through a provider connection
  • On plans that include them: forms on your own hostname through a CNAME
  • Provider credentials are encrypted at rest with AES-256-GCM
  • SMTP
  • Sender.net
  • Brevo
  • Postmark
  • SMTP2GO
  • Resend
  • Mailchimp Transactional
  • Mailtrap
  • Mailgun
  • SendGrid

Templates

Notification emails you control.

Write the notification email for a form or a whole workspace, with draft and published versions, using built-in variables and references to your fields.

  • Draft safely, then publish
  • Share a template across a workspace, or keep it to one form
  • Set in the app, never in a browser request

Roles and activity

The right access for each person, and a record of changes.

Workspace roles are owner, admin, editor, and viewer. On a single form, people can be admin, editor, submissions, or viewer.

  • Keep clients and teammates to the forms they need
  • Activity history for configuration, members, and delivery retries
  • Security events on your account
  • MFA and passkeys
A submission’s page, with its values and verification result.

Publishing

Hosted, embedded, or your own markup.

Every published form has a hosted URL and a script embed. The builder has 37 field types, and hosted forms collect them with standard controls: text, text area, dropdown, number, and checkbox groups.

  • Open and close a form on a schedule, with your own closed message
  • English or French form language
  • Eight brand colours, your submit label, and your success message
  • Explicit publishing, so drafts stay drafts
The Forms screen, listing forms in a workspace.

Spam and abuse

Layers that are on before you ask.

New forms start with a honeypot, a minimum fill time, and a limit on links. Public routes are rate limited at the edge.

  • Optional Cloudflare Turnstile or reCAPTCHA v2 and v3, per form
  • An allowlist of origins for browser requests
  • Checks run before a submission is stored

SDK and API

A client, a JSON API, and 9 framework packages.

All packages are in alpha, so their APIs may change. Use them for schema loading, validation, and submission from your own UI.

  • FormerieRuntimeClient for any JavaScript project
  • A browser mount that renders a form from its public schema
  • A command-line tool, including a Formerie skill for Codex
  • A JSON API for any language

Not in the product yet

What we don’t claim.

So you can decide with the whole picture. These are planned, with no dates, unless a page says otherwise.

  • Step-by-step hosted forms: sections show together on one page
  • Processing rules in the app, such as sanitizing or transforming values
  • Webhooks
  • Response reporting and completion tracking
  • Confirmation emails to the person who submitted
  • File upload and signature fields
  • Dedicated hosted controls for rating, slider, password, hidden, and content fields
  • Logos, fonts, dark themes, or custom CSS on hosted forms: colours and wording only for now

Create a workspace and publish your first form.

In early access. New workspaces start on the Free plan.

Start free See the plans