Techeve Form Gateway

Turn form submissions from static websites into email, safely — without a backend on the customer's site.

The Techeve Form Gateway turns form submissions on static websites into emails — without the site needing a backend of its own. One service serves any number of tenants (customer sites), each with its own recipient address, its own origin allowlist, and optionally its own SMTP outbound.

The customer site embeds a single script tag; the gateway handles the rest: challenge handshake, proof-of-work, spam scoring, quarantine, and delivery.

Who this is for

For anyone shipping static sites (Astro, Hugo, Eleventy, plain HTML) who still needs contact forms — without handing the data to a US service like Formspree and without running a backend per customer site. One installation, one binary, any number of sites.

Try it in three lines

make build
./bin/form-gateway -demo

Demo mode starts a local SMTP sink, creates two demo tenants, and prints their site keys — submit the form, and the mail lands as a file on disk. Nothing leaves the machine.

Where to go next

I want to …	Page
install and run the gateway	Installation
know what it can do	Features
embed a form on my site	Embedding a form
operate tenants, routes, and quarantine	Operating the admin UI
understand `config.json`	Configuration
contribute to the code	Architecture

The technical foundation — why the gateway is built the way it is — lives in the Concept.

The path of a submission

Customer site                   Form Gateway                    Mail server
    │                                │                               │
    │  GET /v1/challenge?site=…      │                               │
    │ ─────────────────────────────► │  signed token, PoW bits       │
    │ ◄───────────────────────────── │                               │
    │                                │                               │
    │  solve proof-of-work (worker)  │                               │
    │                                │                               │
    │  POST /v1/submit               │                               │
    │ ─────────────────────────────► │  verification pipeline        │
    │                                │  → quarantine or queue        │
    │ ◄───────────────────────────── │ ────────────────────────────► │
    │       {ok:true}                │       tenant's SMTP route

The individual verification layers and their order are listed under Features and, in technical detail, in the Architecture page.