Sign PDFs via Zalo or email, sealed with SHA-256.
Upload a PDF or hand off from a Ludy Engage quote, inspect it safely and place fields with suggestions from Vy. Send Zalo links or email with optional OTP, seal with SHA-256 and verify files offline in the browser.
Open source under the AGPL. Ludy eSign is in the self-hosted edition. On Ludy Cloud: coming soon.
- Turn #1 TuanPendingParty A, Zalo link
- Turn #2 HoaWaitingParty B (Bao Bì Phú Thịnh), email + OTP
Party A: Gạo Sạch Mekong
Party B: Công ty CP Bao Bì Phú Thịnh
Clause 5.2: Late delivery penalty of 8% of the delayed batch value
Only a person locks fields and sends
Four steps from a PDF to a sealed record
Runs out of the box when you self-host with docker compose, with no paid keys or external provider accounts.
Upload & inspect
Accepts PDFs (up to 25 MB, 200 pages) or one-click handoffs from a Ludy Engage quote. A zero-egress sandbox checks structure and rejects encryption or active scripts.
PDF passedPlace fields & check clauses
Place signature, initial, date, text and checkbox fields by hand, or ask Vy to suggest boxes and flag risky clauses within your AI budget.
Proposed, human-approvedSend via Zalo link or email
Parallel or sequential routing. Copy a fragment-only Zalo link (no-referrer) or send an email with optional 6-digit OTP. Signers sign on any phone without an account.
Sent to signersSeal & verify
Flattens signatures and Vietnamese text into the PDF, appends an audit certificate page with certificate.json and lets anyone verify SHA-256 offline.
Sealed with SHA-256
What Ludy eSign does today
Built for everyday service agreements, delivery acceptance minutes and quotes: safe PDF checks, field placement, mobile signing, SHA-256 sealing and offline verification.
Safe PDF inspection, field placement and quote handoff
Envelopes accept direct PDF uploads or a one-click handoff from a Ludy Engage quote, always running safety checks before sending.
- Accepts PDFs up to 25 MB and 200 pages inside a zero-egress sandbox: verifies PDF structure and rejects password-encrypted files, embedded scripts, auto-open actions and embedded attachments
- Stores eSign contracts under a dedicated document purpose so uploaded agreements never trigger Finance invoice OCR
- Pure-JS browser PDF viewer (zero .wasm assets) with keyboard and drag placement for 5 field types (Signature, Initials, Date, Name/Title, Checkbox) assigned to signers or approvers in parallel or sequential order, plus CC recipients who receive the sealed copy upon completion
- One-click handoff from Ludy Engage quotes (draft, sent or non-expired accepted): exports the quote PDF, creates the linked eSign envelope, pre-fills the buyer and shows live signing status back on the quote
- Per-organization app switch: switching eSign off hides the app from the switcher, returns 404 on app APIs and returns an identical generic 404 on every public signing and verify route
- Up to 25 MB and 200 pages, PDF structure verified
- Rejects encrypted files, embedded scripts and auto-open actions
- Isolated from Finance invoice OCR queues
- Signature
- Initials
- Date
- Name / Title
- Checkbox
No-referrer Zalo links, optional email OTP and mobile signing
Recipients open the link on a phone from 360px wide to draw, type their signature or confirm approval, with no account signup and no CAPTCHA.
- Each 32-byte signing token lives only in the URL fragment (/-/sign#<token>): the server stores only its SHA-256 hash, the page strips the fragment on load and every response sends Referrer-Policy: no-referrer
- Supports both one-click Zalo/chat links and email invitations; in sequential routing, later signers cannot download PDF bytes until earlier turns finish, with rate-limited reminders
- Optional 6-digit email OTP (10-minute TTL, max 5 guesses, max 3 sends per hour): the PDF remains locked until the recipient enters the code from their mailbox
- Mobile-first ceremony lets signers draw by touch/mouse or type their name as a validated PNG (SVG/XML rejected) and gives approvers a dedicated one-click approval screen without drawing a signature, backed by an atomic single-use guard and zero CAPTCHA friction
SHA-256 sealing, audit certificates and offline verification
Once all signers finish, Ludy seals the final PDF and creates a verifiable evidence bundle anyone can check locally.
- Inside the sandbox, Ludy flattens prior form fields and annotations, stamps validated PNG signatures and Vietnamese text (Be Vietnam Pro), strips interactive scripts and appends an Audit Certificate summary page
- Every envelope keeps an append-only, SHA-256 hash-chained event ledger (protected against updates and deletes at the database level) alongside canonical certificate.json and a CS-XXXX-XXXX-XXXX code
- The Verify PDF screen (/sign/verify) computes SHA-256 locally in the browser with Web Crypto so zero document bytes leave the device, matching against certificate.json offline or looking up the certificate code
- Upon sealing, Ludy emails the completed sealed PDF and certificate.json to the sender, signers, approvers and CC recipients (attaching files up to 18 MB, and always including certificate.json, the certificate code and the SHA-256 digest when a larger PDF is omitted)
- Certificate code
- CS-7F3A-91C2-04B8
- Original SHA-256
- 4a9c2e81b04f...7d31e5082a19
- Sealed SHA-256
- 8f3a1c04d92b...c61e4b902f7a
Computes SHA-256 locally via Web Crypto; file never leaves your browser
Vy suggests fields and flags risky clauses
When AI is on, Vy reads extracted PDF text to suggest field boxes and highlight clauses worth checking; when AI is off, manual placement and sending work identically.
- Field proposals and clause summaries run through the monthly AI budget in Ludy AI with zero tool access, treating extracted PDF text as untrusted data and checking box bounds and quote excerpts deterministically per page
- Suggested fields render as dashed proposal overlays labeled "Proposed"; only a human click on Apply or Apply all promotes them into real fields, and Vy can never send an envelope
- When AI is switched off, the kill switch is tripped or the monthly budget runs out, Vy shows a clear notice while PDF upload, manual field placement, Zalo/email links, OTP, sealing and verification keep running
12-month supply contract for 5-ply carton boxes, payment within 15 days after acceptance minutes.
- Auto-renews unless notified 30 days aheadNeeds reviewPage 2
- Late delivery penalty 8% of delayed batchNeeds reviewPage 3
Coming soon
These three items belong to Slice 2 or await live provider credentials and legal sign-off, so Ludy does not count them as usable out of the box today.
- Coming soon
Vietnam public CA connections (VNPT SmartCA, Viettel MySign, MISA WeSign) and PAdES-LTV envelope signing
Provider adapter and PAdES-LTV CMS embedding primitives are built in the repository; wiring them into envelope signing, the per-organization setup screen, live provider test credentials and legal compliance review under Law 20/2023/QH15, Decree 23/2025/ND-CP and PDPL 91/2025/QH15 are coming next.
- Coming soon
Reusable document templates and permanent direct signing links
Save role presets and field layouts to start new envelopes in one step, plus permanent direct links for frequently signed forms.
- Coming soon
Contract renewal reminders and HR labor contract handoff
Expiration and renewal reminders on sealed agreements, plus direct envelope creation from employee contracts in Ludy HR.
What Vy does in Ludy eSign
Vy is the AI general manager coordinating across Ludy apps. In Ludy eSign, Vy reads PDF text only when asked and budget allows; a person always approves fields and clicks send.
Vy does
- Reads extracted PDF text to propose signature, initial, date and text field coordinates per recipient
- Summarizes key terms and flags clauses worth checking (auto-renewal, penalty caps, unilateral termination) with page-verified quotes
- Respects monthly AI budgets and the Stop AI switch in Ludy AI; manual signing works identically when AI is off
Vy does not
- Never promotes proposed boxes into fields on its own or moves fields you placed
- Never mints signing links, emails invitations, sends reminders or voids an envelope
- Never replaces legal advice or an authorized person's decision to sign
Who Ludy eSign is for
Use standalone for daily agreements, or connected straight to quotes and archiving.
Solo founders and small businesses
Send service contracts, NDAs or delivery acceptance minutes over a compact Zalo link so counterparties sign on their phone in seconds instead of printing and scanning.
Sales teams using Ludy Engage
Hand off draft, sent or accepted quotes directly into an eSign envelope without downloading and re-uploading PDFs, and track signing status right on the quote.
People who self-host
Open source under the AGPL, running inside docker compose with all PDFs, signatures and audit evidence stored on your own server and storage.
Questions about Ludy eSign
What legal standing do Ludy eSign signatures have today?
Today Ludy eSign ships self-contained electronic signatures with a hash-chained event ledger, optional email OTP and SHA-256 PDF sealing, suited for commercial contracts and acceptance minutes where parties agree on electronic authentication. Documents that legally require certified Vietnam public digital signatures (such as VAT e-invoices or tax filings) wait for live CA setup after test credentials and legal review.
Do signers need a Ludy account or a CAPTCHA check?
No. Recipients open the Zalo or email link on a phone or desktop browser, verify an optional 6-digit email OTP if enabled, draw or type their signature, confirm consent and submit.
Why do signing links put the token after # instead of a query string?
Browsers never send the #fragment to servers or Referer headers. Ludy also enforces Referrer-Policy: no-referrer, clears the fragment from the address bar on load and stores only the SHA-256 hash of each single-use token.
Does Ludy eSign still work when AI is turned off?
Yes. PDF upload, sandbox safety checks, manual field placement, Zalo and email links, email OTP, mobile signing, SHA-256 sealing and offline verification all run without AI. Vy is strictly optional for field proposals and clause checks.
How can anyone verify a signed PDF without uploading it to a server?
Open Verify PDF (/sign/verify) and drop the sealed PDF. Your browser computes SHA-256 locally via Web Crypto so no file bytes leave your device, and checks it offline against certificate.json or via the certificate code lookup.
Try Ludy eSign with your next contract
Self-host for free with a single docker compose command. Already have an account? Sign in.