UpcomersSign

Modified on 2026-09-23 from Documenso Community Edition 2.18.0, revision 389390c884949fe27c240488a3259da3cdba93e0. Based on the cumulative VerocSign r9 release. Product naming, visual assets, standalone preparation, optional recipient email verification, timestamp validation and evidence retention were changed. This service is not operated or endorsed by Documenso, Inc.

Upstream software: © 2026 Documenso, Inc. All rights reserved. Copyright and third-party notices remain in the source. Community source and these modifications are available under the GNU Affero General Public License v3, without warranty. Separately licensed enterprise code remains subject to its original license; no enterprise entitlement is granted.

Download modified Community source and reproducible build overlay. The archive preserves the original licenses and documents acquisition of unmodified upstream dependencies from the exact upstream revision. Enterprise source is not relicensed or redistributed in this archive.

Build: 2.18.0-upcomerssign.20260923-signup-centering-r2

The 2026-09-22 refresh updates brand assets, colors, interface and email presentation. Authentication, recipient access, retention and signup policies remain inherited from this brand release.

The 2026-09-22 feature repair restores the document folder loader and explains retained-evidence deletion restrictions in Czech and English. Existing brand assets, authentication, SMTP, recipient access and retention policies are preserved.

The 2026-09-22 follow-up repairs direct-template completion, retained-evidence operation feedback, team and authentication errors, document text validation, reminder and certificate localization, PDF upload recovery, mobile editing and brand colors during error-page navigation. Existing brand assets, dependency versions, database schema, startup, SMTP and signing-evidence retention policies are preserved.

The 2026-09-23 auth-page fix keeps the signup form and the other sign-in, password and verification pages within their centered parent container. Previously accepted application repairs, authentication, dependencies, database schema, SMTP and signing-evidence retention remain unchanged.