Documenso

  • Documenso — Full Profile (2026-09)

    Documenso is a Hamburg, Germany-based company founded in 2023 by Timur Ercan with early contributions from Lucas Smith. The firm has raised approximately $3.5 million in total funding, including a $1.54 million pre-seed round and an additional $2.2 million in early funding backed by OSS Capital. It operates as a VC-backed independent private company under an open-core AGPL-3.0 license model. The business status is clearly defined: non-bootstrapped (institutional backing from OSS Capital), unacquired, non-public, non-PE-owned, and not classified as a platform primitive.
    As of September 2026, Documenso does not offer a first-party hosted MCP server. Its external connectivity is limited to REST and tRPC APIs plus webhook functionality. Agent integration is only achievable through generic third-party HTTP MCP bridges, with no official vendor-hosted MCP solution available. This places Documenso in the non-first-party MCP cluster alongside Motion, Todoist, Qualtrics, MonkeyLearn and Clipdrop, differentiating it from tools with fully supported first-party GA MCP capabilities such as Klaviyo, Feedly, n8n and Databox.

    Website

    Field Value
    Official Website https://documen.so (marketing) · https://documenso.com (app/blog) · pricing: https://documen.so/pricing · self-host: https://documenso.com/self-hosted · docs/API: https://docs.documenso.com · GitHub: github.com/documenso/documenso (~13.7K stars Sep 2026, v2.16.0, AGPL-3.0)
    Company
    Headquartered in Hamburg, Germany, Documenso GmbH was founded in 2023 by Timur Ercan. As a VC-backed independent private open-core enterprise, the company completed a $1.54 million pre-seed financing round led by OSS Capital, with a total fundraising scale ranging from $2.2 million to $3.5 million. It maintains an independent operating status with no initial public offering, private equity takeover or corporate acquisition records to date. The platform adopts a dual licensing model, including the open-source AGPL-3.0 Community Edition and commercial paid licenses covering Business, Platform and Enterprise tiers, which provide a professional AGPL licensing escape hatch for commercial scenario deployment. In 2025, Documenso achieved remarkable operational results, accumulating more than 34,000 total users, over 340 paying customers, and completing approximately 400,000 electronic document signing services. In terms of compliance and certification, it obtained SOC 2 certification in September 2025, fully complies with GDPR requirements, and supports mainstream industry standards such as eIDAS, ESIGN and PAdES, while the Enterprise Edition is equipped with exclusive AATL certification. The product is built on a mature modern technical stack including TypeScript, React Router v7, Hono, Prisma, PostgreSQL and tRPC, and supports flexible self-hosted deployment through Docker and Kubernetes.
    Status Active, v2.x (2.0 Nov 2025 PH Product of Day, AI Auto-Field Dec 2025), no MCP server
    Category ai-productivity-data
    Pipeline Stage none

    Title

    Field Value
    Product Documenso
    Descriptive Title Documenso — Open-Core Electronic Signature Platform (The Open Source DocuSign Alternative): Upload PDF → drag signature/text/date/checkbox/initials/dropdown fields → multi-recipient sequential/parallel signing with roles (signer/viewer/cc/approver) → PAdES-sealed PDF + verifiable audit trail (signer/IP/timestamp/auth) → REST v2 + tRPC API + webhooks (document.signed/completed/etc.) + embedded signing iFrame (Teams+) + white-label (Platform+) + Organizations/SSO (Business+) + self-hosted Community Edition free under AGPL-3.0 (unlimited signatures, your infra) OR cloud Free 25 → Teams 8) → Platform $250 unlimited/whitelabel → Enterprise custom; 2023 Hamburg Ercan OSS-Capital pre-seed AGPL-3.0 no-first-party-MCP-2026
    One-line Positioning Team uploads contract PDF → places fields in canvas → invites signers in order → recipients sign via email link or embedded iFrame → Documenso seals PAdES + writes audit row → webhook fires to your CRM/n8n/Slack → agents can drive it only via REST/tRPC through a generic MCP-HTTP bridge (no vendor mcp.documenso.com); billing is flat per-account/per-user, no per-envelope fee​ (reverse DocuSign 0 license + your VPS; ownership VC-independent open-core (OSS Capital), not per-seat-like-Motion, not per-interaction-like-Qualtrics.

    Features

    Field Value
    Signing Core Upload PDF/DOCX, field types signature/initials/text/date/checkbox/dropdown/radio/number/email/name, multi-recipient with signing order (sequential/parallel), roles signer/viewer/cc/approver, direct-link signing, templates, bulk send, AI Auto-Field placement (Dec 2025), Dictate Next Signer (v1.10), PAdES cryptographic seal binding audit log to PDF, completion certificate
    Audit / Compliance Per-event audit trail (actor/email/IP/timestamp/auth method/action), tamper-evident seal, eIDAS/ESIGN/UETA aligned, SOC 2 (Sep 2025), GDPR, AATL-compliant cert on Enterprise EE, 21 CFR Part 11 claim (makerstack, verify per-use)
    Workflow / Collab Organizations (Jun 2025), team workspaces, folders (v1.10), embedded authoring, embedded signing iFrame, public profile, email notifications via react-email, webhooks on every state change (document.created/sent/signed/completed, recipient.viewed, etc.)
    API / Dev REST API v2​ (Jan 2025) + tRPC​ typed client, API keys, OAuth 2.0 app tokens, webhooks (HMAC-validated), Docker Compose / Helm self-host, Next.js→React Router v7 migration Mar 2025, @libpdf/core PDF engine, Prisma/PostgreSQL, optional Redis/SMTP/S3
    AI Layer AI Auto-Field placement (Dec 2025, heuristic+ML field detection), no conversational AI analyst, no MCP-exposed agent tools — AI is assist-only, not agent-surface
    MCP None first-party​ as of 2026-09 — no mcp.documenso.com, no MCP Server Trigger node, no Composio connector listed; agent builders mount it via generic MCP HTTP/SSE bridge → Documenso REST v2​ (community pattern, not vendor-supported) → aligns Motion/Todoist/Qualtrics none-cluster, distinct from n8n/Databox/Klaviyo first-party
    Security / Admin SAML SSO (Teams+), OIDC auto-redirect (Jun 2026), granular signin-disable flags, whitelabel email domain (Enterprise), EE SLAs + roadmap priority + custom AATL cert, 2FA, RBAC in Organizations

    Pricing (2026-09, flat account/user, NO per-envelope, self-host free AGPL)

    Field Value
    Free (Cloud) $0​ — 5 documents/mo, up to 10 recipients/doc, API access, templates, audit trail, no card, free forever (not trial)
    Individual **300/yr) — unlimited documents, API for personal use, email support, premium profile, all field types
    Teams **480/yr) — 5 users included, +$8/user/mo​ beyond, unlimited documents, API for automation, embedded signing, team workspace, SAML SSO, folders/orgs
    Platform **3,000/yr) — unlimited users + documents, unlimited API, white-labeled embedded signing, Slack integration support, commercial license escaping AGPL​ for embedding in your SaaS
    Enterprise (Cloud or Self-hosted) Custom​ — SOC 2 + AATL cert, SSO/whitelabel email, priority + SLAs, roadmap priority, EE self-host license (often ~$30K/yr self-host floor cited by resellers, vendor custom)
    Self-Hosted Community (CE) $0​ AGPL-3.0 — full codebase, unlimited signatures, your infra, community support only, no SLA, no AATL cert, AGPL obligations apply if you embed/modify-distribute
    Self-Hosted Business (BE) Fixed yearly license, reliable app-support, no infra support, no SLA — contact sales
    Type flat-account-no-per-envelope + per-additional-user-on-teams; starting_paid=0 + VPS; reverse DocuSign per-envelope, reverse Motion per-seat, reverse Qualtrics per-interaction, reverse Nanonets block-run
    Note $250 Platform buys AGPL commercial exemption (embed in closed-source SaaS), not more “features” than Teams — key buyer confusion point; Free 5-doc/mo is casual-only

    Reviews

    Field Value
    G2 No standalone “Documenso” G2 profile​ (e-signature grid folded under DocuSign/Adobe Sign/PandaDoc; adjacent open-source mentions only) → print no-rated-b2b-profile-standalone-2026 (same rule as MonkeyLearn-standalone/FFmpeg/FB-Ads-API primitive: young OSS infra, dev-reviewed not G2-reviewed)
    Capterra None​ — no standalone Capterra page; auxiliary near-zero
    Trustpilot No B2C page​ (B2B-only) → no-rated-consumer-profile excluded (aligns FFmpeg/MonkeyLearn/Qualtrics/Feedly/n8n/Databox)
    GitHub / Dev sentiment ~13.7K stars, 4.1K forks, active PRs; HN/Reddit/PH 4.9/427 upvotes (Nov 2025 launch); praise AGPL auditability, self-host sovereignty, REST v2 + tRPC DX, break-even vs DocuSign at 250-500 docs/mo, AI auto-field; gripes young (2023) so enterprise certs thinner than DocuSign, CE→BE upgrade friction, external PR intake paused (fork diverges), no first-party MCP, QES not native (DocuSeal has it, Documenso roadmap)
    Editorial Gappsy/WFHAutomation/Dev.co/MakerStack 7.0-7.7/10 band, ToolRadar-style 4.4 equiv; consensus “credible open DocuSign alt, not enterprise-equal yet”
    Praise AGPL source auditable, self-host = zero per-signature, REST v2 + tRPC + webhooks clean, PAdES audit seal real, Platform $250 beats DocuSign at 250+ envelopes/mo, Organizations+SSO land mid-market, AI auto-field decent
    Gripes No G2/Capterra star (hard to social-proof in procurement), AATL/QES weaker than DocuSign/Adobe, CE support community-only, no vendor MCP (agent builders hand-roll HTTP bridge), 2023 vintage means fewer court-precedent references than DocuSign, BE/EE licensing opaque (talk-to-sales)

    Review Sources Breakdown

    Field Value
    G2.com no-rated-b2b-profile-standalone-2026 — e-sign grid has no Documenso row, dev-tool not bought-SaaS G2 pattern
    Capterra none → no-standalone-capterra-profile
    Trustpilot none → no-rated-consumer-profile excluded
    GitHub/PH/Reddit/HN 13.7K stars + PH 4.9/427 + dev sentiment directional only, not star
    Editorial (Gappsy/WFH/Dev.co/MakerStack) 7.0-7.7/10 band ≈ 4.4/5 normalized, not G2-grade
    Conclusion​ Prints “no G2/Capterra/TP standalone star, GitHub 13.7K + PH 4.9/427 dev-sentiment, editorial 4.4-norm” — aligns MonkeyLearn-standalone/FB-Ads-API primitive rule (young OSS infra, not G2-rated bought SaaS); do NOT fabricate 4.x

    Access

    Field Value
    Web App app.documen.so — document/field/signer manager, templates, orgs, dashboards; no desktop app
    API REST v2​ (Bearer API-key, /api/v2/documents, /recipients, /webhooks, /templates) + tRPC​ typed router (self-host/admin automation), OAuth 2.0 app tokens, webhooks HMAC-signed; rate limits by plan
    MCP None first-party​ — no mcp.documenso.com, no Claude/Cursor native mount; community pattern = MCP HTTP/SSE proxy → Documenso REST v2 (not vendor-supported, not in MCP cluster)
    Integrations Zapier (ready), Make, n8n (HTTP node), Cal.com, Stripe (billing), Slack (Platform tier), webhooks → any CRM/warehouse; no native 130-connector eco like Databox
    Login Email/password, Google/Microsoft SSO (Pro+), SAML/OIDC (Teams+), 2FA all
    Self-host Core differentiator​ — Docker Compose / Helm, PostgreSQL + Redis + SMTP + S3 + signing cert, CE free AGPL, BE/EE paid license, EU/US/APAC your choice, air-gap capable

    Best For

    Field Value
    Audience 1 Dev/SaaS teams embedding e-sign into their product (Platform $250 AGPL-escape vs DocuSign embed enterprise pricing)
    Audience 2 SMB/mid-market sending 250-5,000 envelopes/mo who refuse DocuSign per-envelope bleed
    Audience 3 EU/regulated orgs needing data residency + audit trail on own infra (self-host CE/BE, GDPR, SOC 2 vendor-side)
    Audience 4 Agencies/HR/legal ops with templates (NDAs/contracts/vendor agreements) and webhook→CRM automation
    Audience 5 OSS-first buyers auditing signature code (AGPL, GitHub readable, PAdES seal inspectable)

    Not For

    Field Value
    Exclude 1 Enterprises needing QES (qualified e-signature) out-of-box — Documenso lacks native QES add-on (DocuSeal has $2-4/sig); must wire external QTSP
    Exclude 2 Procurement teams requiring G2/Capterra star-social-proof + 20-yr court-precedent library (DocuSign/Adobe win on inertia)
    Exclude 3 Buyers expecting first-party MCP for Claude agents — must hand-roll HTTP bridge (reverse Klaviyo/Databox/n8n)
    Exclude 4 Zero-devops teams wanting pure managed no-infra — Free cloud 5-doc/mo too thin, self-host needs Node22+PG+Docker
    Exclude 5 Heavy CLM (contract lifecycle, redlining, negotiation threads) — Documenso signs, doesn’t author/negotiate (PandaDoc/Agiloft better)
    Exclude 6 Per-envelope budgeting finance teams — Documenso is flat-seat/account, they’ll mistrust “unlimited signatures”

    Competitors

    Field Value
    DocuSign Market leader, per-envelope $0.50-2.00, deepest legal precedent + QES + CLM-adjacent, no AGPL/self-host, 10x+ cost at volume
    Adobe Sign Bundled in Creative/Acrobat, enterprise SSO strong, no self-host AGPL, per-seat
    PandaDoc Proposal+sign+billing bundle, richer doc authoring, no self-host, per-seat
    Dropbox Sign (ex-HelloSign) Simple embed sign, Dropbox-bundled, no AGPL/self-host, per-envelope
    DocuSeal Closest OSS twin (AGPL, 11.4K stars, Ruby), field-first builder, native QES add-on, cheaper Pro $20/user, weaker orgs/SSO maturity than Documenso
    OpenSign AGPL Node/React/Mongo, smaller feature set, real but thinner
    SignRequest / Yousign EU mid-market, per-envelope/seat, no AGPL
Do Not Sell or Share My Personal Information Cookie Settings