Documenso
Documenso is open-source document signing, a self-hosted alternative to DocuSign for contracts, engagement letters and approvals. Upload a PDF, place signature and text fields, send it for signing and track completion, either through the web interface or entirely through its API, with the signed documents and their audit evidence staying inside your own infrastructure.
View the repo · documenso/documenso ↗Firms that send a steady stream of agreements and want signing inside their own stack, and product teams that need signature flows embedded via API without a per-envelope bill. It suits organisations that already self-host other tools and can care for one more. If you sign a handful of documents a year, a hosted signing service is less effort; the case for self-hosting builds with volume and with data-control requirements.
Install itgit clone https://github.com/documenso/documenso.git
cd documenso && cp .env.example .env # set the required secrets first
docker compose -f docker/production/compose.yml up -d Before production Electronic signature law varies by jurisdiction and by document type, and some instruments still demand more than a standard electronic signature, so confirm the legal position for your use before relying on it. Operationally it needs a Postgres database, reliable outbound email for signing requests, and signing certificates configured for sealing completed documents. Back up the database and the document store together, because a signed artefact and its audit trail are only useful as a pair.
Where Blash AI comes inWe connect signing into intake and onboarding so nothing waits on manual chasing: a deal closes in the CRM, n8n generates the engagement letter, Documenso sends it, and the countersigned copy lands in the right folder with the record updated. Signature status becomes a field your workflows can act on rather than an inbox someone has to watch.
When you want this running on your real stack, that is the engagement
Book an AI audit →n8n →
n8n is workflow automation you run on your own infrastructure. It connects the applications a business already uses through a visual editor, with hundreds of prebuilt nodes, a code step for anything bespoke, and native support for calling language models mid-flow. Think of it as a self-hosted alternative to Zapier or Make that you own outright, including every piece of data passing through it.
Ollama →
Ollama runs open-weight language models on your own machine or server. One command downloads a model and serves it behind a local API that most existing AI tooling can talk to, so an application built against a hosted provider can point at your own hardware instead. Sensitive data stays inside your network, there are no per-token fees, and it keeps working with no internet connection at all.
LiteLLM →
LiteLLM is a gateway that lets you call models from Anthropic, OpenAI, Google and many other providers through one consistent API. It runs as a Python library inside your code or as a standalone proxy server in front of your whole stack, with cost tracking, per-key budgets, rate limits and automatic fallbacks for when a provider has a bad day.