kysigned's answer:

E-signatures are expensive for one reason: a signature is only worth something if it holds up later, so everyone pays a premium to the provider they trust most. We removed that trade entirely, because kysigned never asks for your trust. Signatures ride on the email system the whole world already relies on (the same DKIM signatures that authenticate every email), and every signed document comes with proof you can check yourself, offline, forever. And it is open source: read the code to see exactly what we do, build your own signing service on top of it, or just use the hosted version at an extremely low price ($0.25 a document, no subscription).

kysigned's answer:

Every e-signature product ultimately says "trust us": their portal, their storage, their word that it will hold up. We built the opposite: the signature comes from your signer's own email provider (DKIM), the proof is a file anyone can verify offline in a browser, and the code is open source, so nothing rests on our word. It is also about as easy as signing gets: no account, no app, your signer just replies to an email. And because we are not selling trust, we do not charge a trust premium: $0.25 a document, no subscription, no per-seat plans.

kysigned's answer:

Anyone who signs a handful of documents a month and resents paying a monthly plan for it: freelancers, small firms, landlords, advisors, anyone with the occasional contract. For them it is $0.25 per document, and the signing side needs nothing installed. The second audience is developers and self-hosters who want an open signing engine they can run themselves, embed, or build their own service on.

kysigned's answer:

It started with a simple question: why do e-signatures cost so much? The answer is trust. The incumbents spent years and millions earning confidence, and that hard-won trust is the moat, and the moat is the price. A newcomer cannot out-trust them, so we changed the game instead: move the trust to the email system everyone already relies on, publish the code, and let anyone verify everything themselves. That became kysigned, the first Open SaaS product from Kychee, the AI-native software factory.

kysigned's answer:

Boring, proven building blocks, on purpose: a trust product should not be clever. DKIM verification is done with mailauth (no hand-rolled crypto), every signed document is checked byte-identical via SHA-256, timestamps are doubled (an RFC 3161 token plus an OpenTimestamps Bitcoin anchor), and the DKIM keys are captured at signing and corroborated against a public archive. The verifier runs offline in the browser. It all runs on run402, our own open-source, agent-native backend (Postgres, REST API, auth, storage, hosting), which gets its own launch soon.