Email-first

Your inbox is the interface.

Send an agreement to SignIT and it becomes a structured, reviewable thread. Replies stay threaded. The database — not the mail provider — is the source of truth.

How a message flows

incoming email
  -> Cloudflare Email Worker (thin transport; HMAC-signs the raw message)
  -> SignIT inbound gateway  (verifies signature, replay window, digest)
  -> routed WITHOUT guessing the organization
       reply-route token  -> the exact thread it belongs to
       agreements@ intake -> the sender's single active organization, or quarantine
  -> canonical thread + message + ingested attachments
  -> proposed action (e.g. send for signing) — never executed automatically
  -> Needs Review in your dashboard

Addresses

[email protected] — start a new agreement thread.
envelope+<token>@reply.yousignit.org — an opaque per-thread reply route.
signing@ / notifications@ — outbound invitations and system mail.
contact@ / support@ / security@ — reach a human.

Reply routes are opaque keyed tokens: they reveal no database, organization, or envelope identifier, and they survive normal email address normalization.

Why email-first is safe

Every inbound request is authenticated at the trust boundary before SignIT trusts a byte of it.
The organization is resolved authoritatively or the message is quarantined — never assigned by guessing.
Incoming mail can propose actions; it can never send, void, or change signers on its own.

Request access Connect an AI client