Wraft

Self-hosted document automation, honestly reviewed. Built for teams that want to own their contract and document infrastructure.

TL;DR

• What it is: Open-source (AGPL-3.0) document lifecycle management platform — templates, e-signatures, approval workflows, and document storage in one self-hosted package [1][2].
• Who it’s for: Legal, HR, and ops teams that generate repetitive structured documents (contracts, proposals, letters) and want to stop paying per-seat SaaS fees to DocuSign or PandaDoc [2].
• Cost savings: PandaDoc starts at $19/user/mo; DocuSign Business Pro runs $40/user/mo. Wraft self-hosted runs on a VPS you already pay for, with no per-seat or per-document pricing [2].
• Key strength: Full lifecycle approach — it covers authoring, collaboration, signing, and storage in one stack, not just one step. Uses Pandoc + LaTeX/Typst for document rendering, which means real typographic control [1][2].
• Key weakness: 129 GitHub stars, private beta status, no public pricing, no third-party reviews exist yet. This is early-stage software — the gaps in documentation and polish are real [1][2].

---

What is Wraft

Wraft is an open-source document lifecycle management platform. The pitch is straightforward: you create document templates, fill them from data, route them for approval, collect e-signatures, and store the finished versions — without handing that workflow to a SaaS vendor.

The company behind it is Functionary Labs Pvt, and the project is hosted at github.com/wraft/wraft. As of this review it has 129 GitHub stars, which puts it firmly in the “interesting but unproven” category. The website still carries an “In Private Beta” badge [2].

What makes the technical approach interesting is how it handles document generation. Rather than a custom rendering engine, Wraft uses Pandoc to convert markdown documents into PDFs, with LaTeX or Typst as the styling layer [2]. For teams that have ever fought with WYSIWYG editors that produce garbage PDFs, this is the right call — structured input, deterministic output. The content is stored in markdown and JSON, which the README describes as “open formats” that keep your documents “always accessible and future-proof” [1].

The feature pillars, as described by the project itself, are four: Create (templates), Sign (e-signature and approval workflows), Automate (generate documents from data), and Store (document repository with structured search) [2].

The CLM (Contract Lifecycle Management) page emphasizes a specific positioning: “70% of organizations are concerned about data privacy in cloud CLM solutions. Wraft is built for them — complete control, zero vendor lock-in” [3]. That’s the honest case for self-hosting this kind of tool. Every contract that flows through a cloud CLM platform is metadata at minimum — who signed what, when, with whom. For a law firm, an HR department, or a startup with sensitive commercial agreements, that’s a reasonable concern.

---

Why people choose it

There are no independent third-party reviews of Wraft available at the time of writing. The GitHub star count (129) confirms this is not yet a widely-adopted tool. The absence of reviews is itself data — it means you’re an early adopter if you deploy this today, not someone following a well-worn path.

The case that can be made from first principles: the alternatives in this space divide into two camps. SaaS platforms (DocuSign, PandaDoc, Adobe Sign, HubSpot’s document tools) are mature, polished, and expensive. Open-source alternatives are either narrowly scoped (Docuseal covers e-signatures only; Papermerge covers storage only) or are general document management systems that don’t address contract-specific workflows.

Wraft is attempting to cover the entire chain: template → fill → collaborate → approve → sign → archive. That’s a broader scope than most self-hosted alternatives tackle, which explains both why someone would want it and why it’s still rough at 129 stars.

The AGPL-3.0 license is worth understanding before you commit. Unlike MIT or Apache 2.0, AGPL requires that if you run Wraft as a network service and make modifications, you must publish those modifications. For internal use — a company deploying it for its own team — this is essentially irrelevant. For an agency or SaaS company considering embedding Wraft in a product you sell to clients, you need to read the license carefully before deciding [1].

---

Features

Based on the README, website, and CLM feature page:

Document authoring:

• Template-based document creation [2]
• Markdown and JSON as the underlying format — portable, not locked to the app [1]
• Content structured for consistency across documents [2]

Document generation:

• Pandoc converts markdown to PDF and other formats [2]
• LaTeX or Typst for typographic control and layout [2]
• API-to-PDF endpoint — generate documents programmatically from external data [2]

Signing and approval:

• Built-in e-signature workflows [2]
• Approval routing — get documents signed with defined approval chains [2]
• “Transparent from Draft to Signature” compliance tracking [3]

Contract lifecycle management (CLM):

• Contract repository — centralized storage and organization [3]
• Draft-to-signature tracking [3]
• Privacy-first positioning: self-hosted means contract data never leaves your infrastructure [3]

Storage and retrieval:

• Structured document storage (not just file storage) [2]
• Advanced search and retrieval [2]
• Built on object storage [2]
• Document archive for long-term retention [2]

Integrations:

• REST APIs [2]
• SSO (Single Sign-On) [2]
• Webhooks [2]

Upcoming features (not yet shipped):

• Smart Blocks — reusable content blocks that adapt to business rules [2]
• Deeper integration with external systems for auto-populating documents [2]
• Custom workflow builder [2]

The “upcoming features” section is honest but also a caution flag. Smart Blocks and Custom Workflows are listed as future work on the public homepage — which means if your use case depends on them, the tool isn’t ready for you yet.

---

Pricing: SaaS vs self-hosted math

Wraft Cloud: No public pricing. The site directs you to “Get Early Access” and “Book Demo” [2]. This is consistent with the private beta status — pricing hasn’t been finalized or published.

Wraft Self-hosted: AGPL-3.0 license, so the software itself is free. Infrastructure cost depends on your setup [1].

What you’re replacing — a realistic comparison:

DocuSign: Personal plan $15/mo (1 user, 5 sends/mo limit). Standard $25/user/mo. Business Pro $40/user/mo. A 5-person team on Business Pro: $200/mo, $2,400/year — and that’s only e-signatures, not templates or storage.

PandaDoc: Starter $19/user/mo (basic e-sign + limited templates). Business $49/user/mo for full automation features. A 5-person team on Business: $245/mo, $2,940/year.

Self-hosted Wraft: A VPS with 4GB RAM on Hetzner runs ~$6-10/mo. That covers the infrastructure for the entire team, with no per-user or per-document fees [2].

The savings math for a 5-person team moving from PandaDoc Business to self-hosted Wraft: roughly $2,800-$2,900/year. That’s real money for an early-stage company, which is exactly who would be considering this tool.

Caveat: pricing data for Wraft Cloud is not available. If you want managed hosting from the Wraft team, you’ll need to contact them directly [2].

---

Deployment reality check

The README points to deployment guides at docs.wraft.app/developers [1]. The site advertises self-hosting as a supported path and mentions Docker-based deployment [2].

What you likely need:

• A Linux VPS with 4GB+ RAM
• Docker and docker-compose
• A domain and reverse proxy (Caddy or nginx) for HTTPS
• PostgreSQL and object storage (S3-compatible)

What’s unclear:

• The README itself links to documentation but provides no inline installation steps — it’s a thin readme that defers to external docs [1].
• With 129 stars and private beta status, community support is limited. If you hit a deployment issue, the Discord channel is your primary recourse [1].
• The website lists SSO as an available integration [2], but whether that’s in the community self-hosted build or gated behind a paid tier is not documented publicly.

The honest signal: The README is three screens long and mostly points outward to documentation that may or may not be comprehensive. Compare this to a mature self-hosted project like Mattermost or Nextcloud, where the README alone walks you through installation. For Wraft, plan to spend time with the docs and potentially the Discord community before your instance is running cleanly.

Realistic time estimate for a developer: 1-3 hours if the deployment docs are solid. For a non-technical founder: don’t attempt this without help.

---

Pros and Cons

Pros

• Full lifecycle scope. Template → fill → approve → sign → store in one platform. Most open-source alternatives only cover one or two of these steps [2].
• Open formats. Markdown and JSON mean your content isn’t trapped. If Wraft disappears or you migrate away, your documents are readable without the app [1].
• Pandoc + LaTeX/Typst rendering. Proper typographic control for PDFs, not a WYSIWYG that exports messy HTML-to-PDF [2].
• SSO and REST API included. Enterprise-adjacent features available without requiring a paid license — at least based on current website copy [2].
• AGPL license. Free for internal use. Source is open and auditable, which matters when the platform handles contracts [1].
• Privacy-first positioning is genuine. Self-hosted means your contract data, vendor names, and financial terms never leave your infrastructure [3].

Cons

• 129 GitHub stars. This is not a dig — it’s a fact that tells you about production risk. Small community means fewer battle-tested deployments, fewer answered questions in issue trackers, and greater bus-factor risk [1].
• Private beta. The product isn’t GA. Features change, APIs may break, and the hosted version has no public SLA [2].
• No public pricing. You can’t evaluate the hosted tier without a sales conversation [2].
• No third-party reviews. There is no independent evidence of production deployments at scale. You’d be the one writing the first review.
• Thin README. A tool this early-stage needs excellent documentation to compensate for community size. The README defers to external docs rather than being self-contained [1].
• Upcoming features are load-bearing. Smart Blocks and Custom Workflows are listed as not-yet-shipped. If your use case needs them, wait [2].
• AGPL implications for commercial use. If you’re building a product on top of Wraft or embedding it in a client-facing service, read the license before deploying [1].

---

Who should use this / who shouldn’t

Use Wraft if:

• You’re a legal, HR, or ops team that generates high volumes of repetitive documents (contracts, NDAs, offer letters, proposals) and wants to move off a $40+/user/mo SaaS.
• You’re comfortable with early-stage software — meaning you can handle rough edges, contribute bug reports, and tolerate occasional instability.
• You have a developer who can manage a self-hosted deployment and Docker infrastructure.
• Your primary concern with current tools is data privacy: you want contract metadata and content staying on your servers.
• You value open formats and want your document content portable regardless of what happens to the vendor.

Skip it (for now) if:

• You need production-grade reliability today. At 129 stars and private beta, Wraft hasn’t earned that trust yet.
• You have a non-technical team with no DevOps support. The deployment story isn’t polished enough for a zero-ops install.
• Your use case depends on Smart Blocks or Custom Workflows — these are listed as upcoming, not shipped [2].
• You need proven integration with Salesforce, HubSpot, or other CRMs. Webhooks and REST APIs exist [2], but pre-built connectors are not documented.

Consider the alternatives if:

• You only need e-signatures: Docuseal or Documenso are focused, mature open-source options.
• You only need document storage and retrieval: Papermerge or Teedy handle that without the full lifecycle complexity.
• You want a proven self-hosted CLM: there isn’t one yet at the maturity level of n8n or Nextcloud — that gap is exactly the space Wraft is trying to fill.

---

Alternatives worth considering

• Docuseal — Open-source e-signature focused tool. Narrower scope than Wraft but more mature. If signing is your primary need, start here.
• Documenso — Open-source DocuSign alternative. Strong community, good UI, focused on signing workflows.
• Papermerge — Open-source document management and archiving. No e-signatures, no templating, but solid for the storage layer.
• DocuSign — The incumbent. Mature, widely integrated, expensive at scale, fully proprietary. The per-document cost model gets punitive fast.
• PandaDoc — Closest SaaS equivalent to Wraft’s scope. Better templates and CRM integrations, no self-hosted option, $19-49/user/mo.
• Docassemble — Open-source document assembly with logic-heavy forms. More developer-facing, not a CLM platform, but powerful for conditional document generation.
• Typst — Not a CLM, but worth knowing: Wraft uses Typst as a rendering option, and if your team is comfortable writing Typst directly, you may not need a workflow layer on top.

The realistic shortlist for a non-technical team wanting to self-host document automation is Wraft vs Docuseal. Docuseal is more mature and focused; Wraft is broader in scope but less proven. If you need full lifecycle management beyond just signing, Wraft is the only open-source option attempting that scope.

---

Bottom line

Wraft is tackling a real problem — enterprise CLM and document automation platforms are expensive, privacy-invasive, and lock you into their formats. The architectural choices are sound: open formats, Pandoc rendering, and a full-lifecycle approach put it in a category where no mature open-source alternative exists. But 129 GitHub stars, private beta status, and the absence of any third-party production reviews means you’re betting on potential, not proven reliability. For a developer-led team with the capacity to run a self-hosted service and tolerance for early-stage software, it’s worth evaluating seriously. For everyone else, wait six months and check back — or contact the team for a hosted trial. The gap it’s filling is real, and if the project matures, the self-hosting math alone makes it worth the switch from PandaDoc or DocuSign.

If the deployment complexity is the blocker, that’s a solvable problem — it’s exactly what upready.dev handles for clients.

---

Sources

1. Wraft GitHub Repository — README, license, contributor information. https://github.com/wraft/wraft
2. Wraft Official Website — Homepage, product features, FAQ, deployment information. https://www.wraft.app
3. Wraft CLM Feature Page — Self-Hosted Contract Lifecycle Management product page. https://www.wraft.app/features/clm
4. Wraft Documentation — Developer and user guides. https://docs.wraft.app