FormRoost
Start free

Form backend for developers

The reliable backend for every form.

Accept submissions, manage leads, and deliver signed webhooks without building the infrastructure yourself.

Start free — no cardRead the docs

50 production200 sandboxsubmissions every month

Lead inboxSample data
3 submissions
Avery ChenNew
Name
Avery Chen
Company
Northstar Labs
Role
Product Engineer
Message
We want to route product consultations into our internal workflow.
Submitted at
May 14, 2026 10:24 AM
Submission ID
sub_01HV7Q9Z2B8J
cURL request
curl -X POST https://formroost.com/s/v1/production/contact-demo \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 8f81f5d8-21c4-4b64-9271-7178d31f84ef" \
  -d '{
    "name": "Avery Chen",
    "email": "[email protected]",
    "company": "Northstar Labs",
    "message": "Product consultation"
  }'
WebhookDelivered
URL
https://hooks.northstar.dev/formroost
Event
submission.created
Delivered at
May 14, 2026 10:24:01 AM
Signature
v1,TO41ZVSzQNVuZqNFDYbOd6Gk...
Sandbox first

Test end to end with separate disposable data.

Lead inbox

Search, qualify, and manage every accepted lead.

Signed webhooks

Deliver verifiable events to systems you control.

Built for the form lifecycle

From submission to webhook.

FormRoost handles the backend so you can stay focused on your product.

Your inputYour HTML form
SubmitNative form POST
FormRoostValidate · organize · sign
DestinationCRM or helpdesk
Static HTMLQuickstart
<form method="post" action="https://formroost.com/s/v1/production/contact-demo">
  <input name="email" type="email" required />
  <button>Send</button>
</form>
HTTP is the integration surface. No SDK or hosted form required.

Everything after submit, accounted for.

You keep control of the form and its user experience. We make the backend path durable, searchable, and observable.

Accept with confidence

Validate the request against its published contract, apply idempotency, and store accepted data before returning success.

Work every lead

Search and filter the inbox, move leads through status, and retain notes, tags, and activity in one inspectable record.

Deliver verifiable events

Sign CloudEvents, retry transient failures, expose attempt history, and let you replay failed deliveries deliberately.

Test freely. Publish deliberately.

Sandbox and production are separate by design, with one explicit path between them.

  1. 01
    Sandbox

    Build against disposable test data with a separate allowance.

  2. 02
    Review

    Inspect schema and webhook-affecting changes.

  3. 03
    Publish

    Create one immutable production configuration version.

  4. 04
    Accept

    Store the canonical submission before it consumes allowance.

  5. 05
    Operate

    Manage the lead and observe every signed delivery attempt.

Capacity changes. Capabilities do not.

Every public plan gets the same product. You pay for measurable resources.

See full plan policy
PlanProductionSandboxPayloadWebhooks / form
Free50200256 KB1
Starter1,0002,000256 KB1
Growth10,00020,000512 KB3
Agency100,000200,0001 MB5
EnterpriseCustomCustomNegotiatedCustom

Paid allowances and prices remain provisional until local workload benchmarks are complete.

Clear boundaries. Portable edges.

Security and interoperability should be documented properties, not marketing adjectives.

Scoped by environment
Credentials, origins, allowances, and data remain visibly separated between sandbox and production.
Portable by default
Canonical JSON stays queryable, with CSV and NDJSON exports for the workflows you already use.
Standards at every edge
OpenAPI, JSON Schema, Problem Details, CloudEvents, and Standard Webhooks define public contracts.

Know the boundaries before you sign up.

Public documentation includes the request contract, examples, limits, errors, and webhook verification flow.

Read the documentation
Does FormRoost build or host my form?

No. You design and host the form; FormRoost provides its backend.

What consumes production allowance?

A valid production submission counts only after it is accepted and durably stored. Validation failures and idempotent replays do not count.

Does sandbox traffic affect production?

No. Sandbox is isolated, uses a separate monthly allowance, and retains disposable data for 30 days.

Do higher plans unlock features?

No. Public plans share application capabilities and differ through measurable capacity.

Send the first sandbox submission.

Start with 200 sandbox and 50 production submissions every month. No payment card required.

Start free — no cardTalk about Enterprise