Case 08 · Real Estate / Document Automation

Documenso Self-Hosted E-Signature with AI Field Detection

Document-Signing Platform & Applied-AI Engineersdocumenso.comProduct EngineeringAI & AutomationCloud & DevOps
← All case studies

Documenso is an open-source DocuSign alternative with PAdES-standard PDF signing (Next.js/tRPC/Prisma). We self-hosted it inside the client's VPC and added an LLM job that pre-fills signing fields from uploaded contracts.

The challenge

A real-estate brokerage needed isolated, compliant document signing for buyer disclosures hosted in their own VPC — no third-party SaaS holding sensitive PDFs. They also wanted signing fields pre-filled automatically instead of placed by hand on every disclosure.

  • Self-hosting a full e-signature stack inside the client's VPC with valid PDF signing certificates.
  • Extracting field positions and values from heterogeneous uploaded PDFs to auto-place signature fields.
  • Wiring signed-document events into the client's transaction-management system.
Our solution

We deployed Documenso via Docker inside the client's VPC, generated PAdES signing certificates, and built a field-detection job (AWS Textract → Claude) that populates Documenso field records through the TypeScript SDK, with a webhook firing on document.signed.

  • A self-hosted Documenso deployment (docker compose) inside the client's VPC with a generated .p12 PAdES signing certificate.
  • An AI field-detection job using AWS Textract plus Claude to read uploaded PDFs and pre-populate documenso.field records via the sdk-typescript.
  • A document.signed webhook that pushes completed, signed disclosures straight into the brokerage's transaction-management system.

A customized view of the system we shipped for this engagement — the components and how requests and data flow between them.

detectfieldssignsigned🖥️Signing UI(Next.js)📄UploadedContracts⚙️tRPC / Documenso🧠Textract +Claude🔐PAdES SigningCert🗄️PostgreSQL(Prisma)🏢TransactionSystem
Next.jstRPCPrismaPostgreSQLDockerAWS TextractClaude APIDocumenso TypeScript SDK
Stood up compliant PAdES e-signing entirely inside the client's VPC — no SaaS holding disclosures.
Replaced manual field placement with AI pre-fill from uploaded PDFs.
Auto-pushed signed disclosures into the transaction system via webhook, removing re-entry.
Direct value addedGives the brokerage DocuSign-class signing they fully own and host, plus AI pre-fill that removes the per-document field-placement chore.
Why it mattersRegulated document workflows demand data isolation. A self-hosted, open signing platform keeps sensitive PDFs in the client's VPC while AI extraction removes the manual setup tax.

Before — manual bottleneck flow

1SaaS Signing ConcernBottleneck
Compliance · Blocks adoption

Sending sensitive disclosures through a third-party SaaS fails the brokerage's data-isolation rules.

2Manual Field PlacementBottleneck
Transaction Coordinator · 20 mins/doc

Signature and initial fields are dragged onto every PDF by hand.

3Re-Key Into TMSBottleneck
Coordinator · 15 mins/doc

Signed files are downloaded and re-entered into the transaction-management system.

After — automated optimized flow

1VPC Upload
Coordinator · 10 secs

Disclosure is uploaded into the self-hosted Documenso instance inside the VPC.

2AI Field Pre-Fill
Textract + Claude · 8 secs

Fields and values are detected and placed automatically via the SDK.

3Signed → TMS Webhook
Webhook Node · Instant

On document.signed the completed file is pushed straight into the transaction system.

Portrait of Richard Cole
The disclosures never leave our own environment now, which was the whole point for us, and the fields come in already placed. It took a small but constant chore off every transaction without changing how our agents work.
Richard Cole at RE/MAX

Have a problem like this?

Tell us your goal and we'll turn it into a structured plan — from idea to stable, scalable reality.

Contact us