By LibreSign

LibreSign

What it does

LibreSign is open-source electronic-signature software integrated with Nextcloud. A team can prepare a document, request signatures, follow the signing process and validate the result while choosing how to operate the underlying Nextcloud environment. LibreCode developed the application and offers optional services around it.

Last updated
Oct 20, 2026
LibreSign · Editorial illustration
Conceptual editorial illustration of blank documents moving through two signing stages and a final validation check.

Work at LibreSign?

Help customers find accurate information about your software.

Manage this listing →

Find your fit

Who it is for

The clearest fit is an organization that wants signing to sit within its Nextcloud document environment and needs a traceable process for internal and external signers. Teams without Nextcloud should include a compatible installation or managed setup in their evaluation; the app does not run without it.

LibreSign is relevant when signing order, certificate choice and later validation matter more than simply adding a visual mark to a PDF. Define the required assurance level and who will operate the environment before choosing a deployment.

Back to sections

The work it supports

Core capabilities

A sender can create or upload a document, choose signers and select a digital or electronic signing method. Pilot a representative contract from upload through the final signed file to see whether the actual routing and document format meet your needs.

For several recipients, LibreSign supports sequential signing so a sender can set the order. External recipients can sign through a link without creating a LibreSign or Nextcloud account. Check the invitation and identity process with a safe sample before using it for sensitive documents.

The application supports personal and system-generated digital certificates. Certificate choice affects the assurance of the resulting signature; decide which certificate and identity checks a particular document needs rather than treating every method as equivalent.

LibreSign records signature events and timestamps in an auditable history. Teams can use that record to follow who acted and when, while separately checking whether the configured timestamp and identity method meet a legal or regulatory need.

Signed-document validation is part of the product, including a QR-code validation option. Verify a finished sample from the recipient's side and keep the validation path with the organization's document-retention process.

A REST API supports integration with other systems, and signers can use a mobile browser. Confirm the specific API endpoints, authentication and browser experience in a test environment before promising a connected workflow to users.

Back to sections

Understand the offer

Pricing and getting started

The LibreSign application is free and open source with no license fee, and an organization can host it on its own Nextcloud instance. That path still needs a compatible Nextcloud environment and someone responsible for installation, updates, backups and access controls.

LibreCode separately offers managed hosting and professional support. Its pricing page currently publishes no amounts, instead directing organizations to discuss Business adoption support or API Integration. Ask for a written scope covering hosting, setup, support, data location and ongoing cost.

The FAQ defines a billable service user as an organizational Nextcloud account; external signers who receive links do not count. Confirm that definition and any minimums, usage terms or implementation fees in the actual quote, since the public pricing page does not specify amounts.

Back to sections

Look a little closer

Before you choose

Start with the deployment decision: use a compatible Nextcloud environment that permits the app, or ask LibreCode to scope managed hosting. Then test a small signing request with an internal sender and an external recipient, including the final validation step.

The vendor describes simple, advanced and qualified-signature workflows, but the legal weight of a result depends on certificate, identity verification, hosting and process design. Qualified signatures require the appropriate qualified certificate and trust-service arrangement. Have the intended jurisdiction and document type reviewed before relying on a signature level.

Timestamps are recorded, yet their legal weight can depend on configuration and applicable law. Check the certificate and timestamp chain on a completed sample, together with audit-history retention and who can later verify the document.

Back to sections

4 distinct sources behind this profile. Research observed Oct 20, 2026. Features and offers can change.
View sources and research →

Help keep this profile useful

Spotted an outdated detail? Send the correction with a supporting source. A verified account is needed to submit.

Suggest a correction ↗