Own endpoint
Best when you already run a backend and need full control over storage, routing, and policies.
static site forms ยท practical guide
Contact form without backend for static sites
Most static-site contact forms are simple until the submission needs a safe destination. This guide compares a custom endpoint, a serverless function, and a hosted form endpoint before you commit to one.
No payment is accepted from this page. No SLA, support promise, deliverability guarantee, or platform affiliation is included.
contact.html
<form method="POST" action="https://forms.example.com/f/site-form">
<input name="email" type="email" required />
<textarea name="message" required></textarea>
<button>Send</button>
</form>Use this as a setup example for the kind of form action the relay flow supports.
decision checklist
When a hosted form endpoint makes sense
Use a hosted endpoint when the form is important enough to need logs, spam controls, and delivery visibility, but not complex enough to justify maintaining your own backend.
setup paths
Three low-maintenance paths
A custom backend gives the most control. A serverless function reduces hosting work but still leaves secrets, retries, spam handling, and logs on your side. A hosted endpoint trades some control for faster setup and simpler client handoff.
Small function
Good for developers who can maintain secrets, retries, spam checks, and error monitoring.
Form endpoint
Useful for static sites and client projects where setup speed and handoff are more important than control.
early-access CTA
Want a narrow endpoint for static/client sites?
ClariForm Relay is collecting early-access interest from builders who need a contact form working before launch. Joining does not create an account, charge a card, or guarantee production access.