Rutba Sign
The signature is the easy part. The evidence is the product.
Send agreements for signature by link (your counterparty needs no account) and get back a sealed, hash-chained record of who was invited, how they proved who they were, what they saw, and what they agreed to. Anyone can verify the result, forever, for free.
In early access. Signing and verification are always free, and you pay only to send.
The evidence record: hash-chained, append-only
- 09:14:02Envelope sent
- 09:16:41Link opened: Ada Osei
- 09:17:05Identity: phone code
- 09:19:22Disclosure accepted
- 09:21:48Signed, as Director
- 09:21:49Receipt issued & countersigned
- 11:03:12Notarised in person
- 11:03:14Sealed & countersigned
Reorder or thin this chain and public verification says so.
Why this one
Built so the record holds up, not just the picture
Anyone can put a picture of a signature on a page. What decides a dispute two years later is whether you can still show what happened, and that not one byte has moved since.
Evidence, hash-chained
Every step of the ceremony (invitations, views, consents, phone codes, location, the signing act itself) lands on an append-only chain that is sealed on completion and countersigned with an RFC 3161 timestamp from a public authority.
Identity evidence you choose
Per signer, per envelope: email possession, a phone code, an access code, recorded location. The sender proposes the rungs; the signer sees and agrees to each one: evidence collected without consent is not evidence.
Signers never pay
The people you send to need no account and are never charged. Pay per envelope sent, or one flat organization subscription, never per seat for six people who send thirty contracts a year.
More than signers
Ordered, parallel or mixed signing with approvers, witnesses, attesters and cc parties, each in a stated capacity. Comments travel with the envelope, versions are retained, and a revision voids exactly the signatures it invalidates.
Verification is public, forever
A completed record verifies without an account and keeps verifying if you stop paying: evidence that expired with a subscription would not be evidence.
An API like the ones you know
The same envelope, template and bulk-send operations the app uses, under your own API key, with signed webhooks: the shape integrators already know from the incumbents.
Start from the paper you have, or from questions
Answer a few questions and have the agreement drafted for the jurisdiction it is for. Or upload a PDF, pick one from Drive, or draft it together in the shared word processor with every version kept, then print it into the envelope with a captioned pad for each party.
Everyone leaves with a receipt
Send by link, into a colleague's inbox, or hosted in person. Each person who acts is handed their own seal over their act, countersigned by Rutba that instant: proof they hold whether or not the envelope ever completes.
Stamps, seals, notaries, renewals
Declare the stamp duty, corporate seal or notarisation the paper needs. Do it yourself with the proof attached, or ask Rutba to arrange it. Then the calendar: term ends, renewal reminders, and a renewal chained to the original.
How it works
Four steps, one sealed record, and a life after it
The short version. The eight stages, in order, with what the record holds at each, are on the lifecycle page.
Start and prepare
Have it drafted from your answers, upload, pick from Drive, or draft together. Add the people in their capacities, a captioned pad for each, the evidence to ask for, the formalities, the calendar.
Send, three ways
By link to anyone, into the app for a colleague, or in person on your own device. Everyone signs at the table and leaves holding a receipt countersigned by Rutba.
Sealed and countersigned
When every party has acted and every formality is met, the whole record is hash-chained, sealed, timestamped by a public authority and countersigned by Rutba.
Verify, manage, renew
The executed copies and certificate land in your Drive; anyone verifies them, free, forever. The agreement manager watches the term and renews on a record chained to this one.
Questions
The ones a careful buyer asks
Can I start sending today?
Rutba Sign is in early access. The app runs at app.sign.rutba.io, where organizations with a Rutba licence use it today, each on its own instance. Onboarding is hands-on and there is no card checkout yet, so ask for early access and we will set you up. Rutba Sign for individuals is built, but its accounts are not open to the public yet.
Is a signature collected this way legally binding?
Electronic signatures are recognised in most jurisdictions (the UK, the EU under eIDAS, the US under ESIGN/UETA and many others) for most agreement types, and what a court weighs is the evidence behind the signature. That is the part this product is built around. Some documents (deeds, wills, some property transfers) have extra requirements per jurisdiction; the composer knows the rules it can know and refuses what it cannot support rather than guessing.
What happens to my documents if I stop paying?
You keep every completed envelope, its executed copy and its evidence, permanently, and public verification keeps working. Evidence that expired with a subscription would not be evidence.
Do my counterparties need an account?
No. Each party signs through their own link, proves the identity evidence the envelope asks for, and is never charged.
Can I run it on my own instance?
Yes. Organizations on a Rutba suite licence run Sign as an app on their own instance, opened at app.sign.rutba.io, with signed documents landing in their own Drive. Rutba Sign for individuals is one shared instance where each person sees only their own work; it is built, and not open to the public yet. API keys and webhooks belong to an organization’s own instance.
Can somebody sign in person, or from inside the app?
Both. A colleague who uses the same instance signs from their own inbox, their identity bound to the act by the session they are already in. Somebody sitting beside you signs on your device, with the sender hosting the ceremony and the record saying so. The ceremony itself is the same one the emailed link opens.
What about stamp duty, corporate seals and notaries?
Declare the formality on the envelope with the moment it is owed (before sending, or before the seal) and the envelope holds the door until it is met. Satisfy it yourself with the reference and the proof attached, or ask Rutba to arrange it and the reference comes back to your record. Nineteen jurisdictions are described on day one; none of it is a refusal, because a missing stamp is your exposure to judge, not ours.
What happens when an agreement comes up for renewal?
Every agreement has a calendar: effective date, term end, renewal notice. The agreement manager lists what ends soon, reminds the sender ahead of the notice period, and renews as-is or with changes on a new envelope chained to the old record: same people, same pads, same formalities, the original untouched.
Rutba Sign is in early access
Pay as you go per envelope, or a monthly package for the organization, from one sender to the whole office. No seat counts, no charge to signers, no charge to verify. Card checkout is not open yet, so onboarding is hands-on.