For product teams
Signing infrastructure for the product you are building
If your customers sign documents inside your product, you have three options: build signing yourself, resell a platform that also sells directly to your customers, or use infrastructure built to sit underneath someone else’s product. This is the third one.
Why this is different from wrapping a consumer e-signature tool
Multi-tenant from the first migration
Your customers are separate organizations in the data model, isolated by PostgreSQL Row Level Security — not by a tenant column your code has to remember to filter. That is the property you cannot retrofit later.
Test and live are separate by construction
API tokens are scoped and split between environments. Your staging cannot send a real signing request to a real customer by accident.
Webhooks with idempotency
Every state change reaches your backend. Writes accept an idempotency key, so a retried call does not create a second envelope.
Your brand, not ours
Signer invitation emails carry your customer’s branding. The signer experiences your product, not a co-branded detour through ours.
Verification your customers can hand to a third party
Anyone can verify a signed document publicly with its code — no account required. Your customer’s counterparty, auditor or lawyer never needs a login on our platform.
We do not compete with you
We sell signing. We do not sell the vertical product you are building, and we will not show up in your customer’s inbox trying to.
From signup to first signature request
- Create an account and issue a test-scoped API token.
- POST an envelope with your document and signers.
- Receive the webhook when the envelope is signed, and pull the evidence dossier.
What we do not do yet
Same rule as our Trust Center: you should hear this from us, not discover it in week three of integration.
- No embedded signing inside an iframe in your own application. Signers today sign on a link we host, with your customer’s branding. If in-app embedding is a hard requirement, we are not ready for you yet.
- No official client SDKs. The API is REST with documented examples in cURL, Node.js and Python; you will be writing the client.
- No US data residency. Everything runs in the European Union.
Get a token and try the API today
No sales call, no waiting list. Create the account, issue a test token, send an envelope.