Can DocuSign be vibe coded?
Request a low-stakes signature with a transparent audit log and no legal-assurance claim
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For DocuSign, request a low-stakes signature with a transparent audit log and no legal-assurance claim. The hard boundary is brand trust, identity options, global legal framework, integrations, and compliance, plus document fidelity, identity, and compliance.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
high editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Request a low-stakes signature with a transparent audit log, preserve originals, generate auditable outputs, and keep files in a user-owned store without any legal-assurance claim.
- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- brand trust, identity options, global legal framework, integrations, and compliance
- pixel-perfect proprietary PDF engine
- identity verification
- qualified trust services
- Trust, audits, and counterparties matter more than feature parity.
- Compliance, licensing, and legal accountability are core features.
Why people still pay
People still pay for DocuSign because the visible editor is reproducible, but reliable rendering and legally defensible signature workflows are not a casual side project. The recurring cost buys format edge cases, fonts, rendering, encryption, signatures, evidence, retention, storage, backups, and legal requirements, not just the visible interface.
Trust, audits, and counterparties matter more than feature parity.
Compliance, licensing, and legal accountability are core features.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to DocuSign
Context
**DocuSign** — Request a low-stakes signature with a transparent audit log and no legal-assurance claim. It currently costs $15/mo.
A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For DocuSign, request a low-stakes signature with a transparent audit log and no legal-assurance claim. The hard boundary is brand trust, identity options, global legal framework, integrations, and compliance, plus document fidelity, identity, and compliance.
This brief describes a focused, single-operator replacement for the part of DocuSign that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Request a low-stakes signature with a transparent audit log, preserve originals, generate auditable outputs, and keep files in a user-owned store without any legal-assurance claim.
Build a focused single-user workflow with real persistence, search, and export.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Docker.
PostgreSQL.
LibreOffice headless.
Local or S3-compatible storage.
Public HTTPS for signature links.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build a closest honest personal substitute for DocuSign in an empty repository.
Use Next.js 15, TypeScript, Python 3.12, FastAPI, pikepdf, LibreOffice headless, and PostgreSQL; do not offer alternative stacks.
The core loop is: request a low-stakes signature with a transparent audit log, preserve originals, generate auditable outputs, and keep files in a user-owned store without any legal-assurance claim.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Keep every original immutable and write each operation to a versioned output file.
Support merge, split, reorder, rotate, compress, watermark, redact, OCR, and Office-to-PDF conversion.
Render page previews and warn when fonts, forms, signatures, or encryption may be altered.
For signature mode, place fields, invite signers, record consent, and seal a final PDF hash.
Maintain an append-only event log with timestamps, document hashes, and delivery outcomes.
Add file expiry, download, deletion, backup, and a prominent low-stakes-use warning.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Do not claim to reproduce proprietary data, network liquidity, regulated access, or frontier infrastructure.
Deliberately leave out qualified or regulated electronic signatures.
Deliberately leave out government identity verification.
Deliberately leave out full Acrobat-level editing and enterprise document governance.
Finish by running the tests and listing the exact commands used.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Brand trust, identity options, global legal framework, integrations, and compliance.
Pixel-perfect proprietary PDF engine.
Identity verification.
Qualified trust services.
Trust, audits, and counterparties matter more than feature parity.
Compliance, licensing, and legal accountability are core features.
What you still own after launch
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Maintain every third-party integration as APIs and OAuth rules change.
Risk
**High consequence.** Use this as a prototype or personal aid. Keep a qualified human and an established provider in the loop for consequential decisions.
Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[Stirling PDF](https://github.com/Stirling-Tools/Stirling-PDF) — Active open-source web application for a broad set of PDF operations
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/docusign
You still own the product
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.
Open-source prior art
Before you start
Can DocuSign be vibe coded?
Not faithfully. A consolation build is possible, but the paid product's decisive value sits outside a solo rebuild. For DocuSign, request a low-stakes signature with a transparent audit log and no legal-assurance claim. The hard boundary is brand trust, identity options, global legal framework, integrations, and compliance, plus document fidelity, identity, and compliance.
What can an AI coding agent reproduce from DocuSign?
Request a low-stakes signature with a transparent audit log, preserve originals, generate auditable outputs, and keep files in a user-owned store without any legal-assurance claim. Build a focused single-user workflow with real persistence, search, and export. A responsive interface with real empty, loading, success, and error states.
What will a DIY DocuSign replacement still be missing?
brand trust, identity options, global legal framework, integrations, and compliance; pixel-perfect proprietary PDF engine; identity verification; qualified trust services; Trust, audits, and counterparties matter more than feature parity.; Compliance, licensing, and legal accountability are core features.
What do I still own after building a DocuSign alternative?
Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss. Maintain every third-party integration as APIs and OAuth rules change.