Kevin Rose has released SignuDoc, a free, open-source alternative to DocuSign that puts the signing software in its users’ own cloud accounts. Announcing it on Nov. 16, Rose used an $8,100 annual DocuSign price comparison for a 15-person team and offered a different proposition: deploy his project to your own Vercel account, with no per-seat software fees. His launch post highlights custom branding, audit trails and tamper-evident seals.
The response quickly reached beyond signing PDFs. Guillermo Rauch celebrated the prospect of personalized software people own. Greg Isenberg saw a business opportunity in giving useful software away. Matthew Berman took the argument to its boldest conclusion, predicting that “All software will be de facto open-source and free.”
Those reactions turn Rose’s launch into a concrete example of the future taking shape in the discussion: useful applications that people can run and adapt for themselves.
Software you can make your own
“A new era of software is upon us. Personalized, fully owned, open source. And higher quality than what it replaces,” Rauch wrote in response to Rose.
SignuDoc gives the ownership part of that vision a practical shape. Its MIT-licensed code is available to inspect and modify. The project describes a signing flow that lets users upload PDFs, place fields and send signing links, with reusable templates and their organization’s branding. Documents and application data live in cloud accounts controlled by the operator.
A team can therefore start with a working application and change its copy of the code. That is the appeal the account Build A Goat picked out in its response to the launch: adapting an internal tool to a team’s needs without waiting for a vendor to add the desired workflow.
Rauch’s claim that this software is higher quality remains his assessment. The tangible invitation from Rose is already there: take the code, deploy a copy and make it your own.
A free product can still create a business
Isenberg’s reaction offers a particularly interesting answer to what this could mean for SaaS companies and independent developers. Find popular software people resent paying for, he proposed, release a free open-source alternative and build goodwill. Then offer paid hosting, team features and support to power users.
In that model, giving away the application is the beginning of a business. People who want control can run it themselves; people who value convenience can pay someone to operate and support it. Isenberg presented this as a playbook, not an announced SignuDoc pricing plan.
The conversation also has a sharper edge. Jeff Walton argued that free alternatives threaten the technical advantages protecting established SaaS businesses. His investment thesis is a prediction, but it shows how quickly the discussion moved from one signing app to the durability of subscription revenue.
Berman imagines software becoming free by default. Isenberg imagines businesses charging for services around it. Both see room for a useful free product to change what customers choose to pay for.
Ownership comes with choices
SignuDoc’s own documentation keeps the practical distinction clear. The software has no seat fees, while companies using its Vercel deployment need paid hosting. The README lists Vercel Pro at $20 a month, with other usage costs possible, and makes operators responsible for updates and administration.
It also describes a narrower signing product than DocuSign, including one PDF per signing request and sequential signing. Teams still need to check that its features fit their requirements.
For the builders celebrating Rose’s release, the opportunity is to have that choice in the first place. SignuDoc offers a concrete project to examine, run and change. Isenberg’s proposed service business leaves room for people who would rather pay for help. And Rauch’s personalized-software vision puts the user’s needs at the center of what gets built.
Rose has made his contribution to that conversation usable: the code is available, and the deployment flow copies the project into the user’s own GitHub account. The next version can be theirs.
Comments