When LibreSign fits a Nextcloud organization and when DocuSign still fits better
LibreSign fits when your files, users and sharing already live in Nextcloud and you want signatures to stay on your own servers. In that setup, a legal or HR team stores agreements in Nextcloud folders, shares them with colleagues through existing permissions, and sends them for signature from the same place. LibreSign is an AGPL-3.0 licensed Nextcloud app that works with Nextcloud files, users and sharing, includes internal and external signers in one request, validates signed documents and certificate status, and sends notifications and reminders. DocuSign fits better when the business runs on envelopes, reusable templates, bulk send and a broad catalogue of connectors into CRM, HR and finance systems, where the signing workflow matters more than the file store.
Four factors decide the choice. First, count the workflows that need templates. If most agreements are one-off documents uploaded to a folder, LibreSign covers them directly. If you reissue the same offer letter or contract hundreds of times with different fields, template reuse and bulk send in DocuSign may save more effort than they cost. Second, check who signs. Mostly internal staff point toward LibreSign. A high share of external counterparties, who expect a familiar signing experience and no account creation, requires a test of the external signer flow with your own customers. Third, define the signature assurance you need. Confirm with your legal counsel whether simple or advanced signatures are enough, and confirm with LibreSign's documentation which certificate options it supports for your case. Fourth, decide who runs the server. A Nextcloud instance needs patching, backups and upgrades one major version at a time, so a team without that capacity should price in a support contract or DeployOpen's retainer.
Which option fits which signing scenario
This table matches common signing scenarios to the better fit between LibreSign inside Nextcloud and DocuSign. Read each row for the reason, then confirm the specific feature and plan requirements against current vendor documentation before you decide.
| Scenario | Better fit | Reason |
|---|---|---|
| Internal approvals on files already in Nextcloud | LibreSign | Signing runs where the document, user accounts and sharing already exist, so no copy leaves the Nextcloud server for the signature step. |
| External counterparty receives a signing link | Either, after testing | LibreSign supports internal and external signers in one request. Confirm how external signers verify identity and how their data is handled in your setup. |
| Recurring templated contracts sent from a template library | DocuSign or Documenso | Templates with reusable recipient roles are a core DocuSign feature. Check whether LibreSign covers your template reuse pattern before relying on it. |
| High-volume bulk send from a spreadsheet | DocuSign or DocuSeal Pro | Bulk send is built around sending many envelopes from a list. Confirm LibreSign's batch behavior with the project before committing to high volumes. |
| EU qualified electronic signatures (QES) | Neither, without a qualified trust service provider | A qualified signature needs a qualified certificate from a listed qualified trust service provider. Ask any vendor which provider issues the certificate and whether it is on the national Trusted List. |
| Simple or advanced signatures inside your own control | LibreSign | Self-hosting keeps signing certificates, signer data and audit records on your servers. Confirm which signature level your legal team needs for each contract type. |
| Signed document validation and certificate status checks | LibreSign | LibreSign is documented to validate signed documents and certificate status. Ask your assessor which validation evidence they expect to see. |
| Operating a supported Nextcloud version | Plan for both | Nextcloud major versions are supported for about one year and upgrades must go one major version at a time. Budget ongoing upgrade work whichever option you choose. |
How LibreSign signs files where Nextcloud already stores them
The main difference for a Nextcloud team is where the signing request starts. LibreSign is an AGPL-3.0 Nextcloud app, so the document that needs signing is usually already a file in Nextcloud, stored under the same users and sharing rules the team uses every day. Instead of uploading a copy to a separate signing service and then tracking the result elsewhere, the request is created from the file itself. Before you rely on this, confirm in your own test instance how LibreSign handles file permissions, versions and the signed copy that is saved back, because those settings decide who can see a contract after it is signed.
LibreSign can include internal and external signers in the same request, which matters when an employee and a supplier must sign the same agreement. Internal signers are Nextcloud users, while external signers receive an invitation and sign without a Nextcloud account. Notifications and reminders keep the request moving, and the app also validates signed documents and checks certificate status. Its API lets other systems start requests and read results, so a ticketing or HR workflow can connect to it. Map each of these to a test case with your own signer roles and sequence before you commit.
Signature types and certificate options must be confirmed against the current LibreSign documentation and your legal requirements, not assumed from a feature list. Ask which signature levels the app produces, which certificates it can use, and whether the validation it performs meets the evidence your counsel expects for your jurisdiction and contract types. Where DocuSign publishes which signature levels each plan includes, LibreSign's own documentation and your legal review are the sources to rely on, and the answers should be written into your signing policy before go-live.
Capabilities compared: DocuSign envelopes against LibreSign requests
This table maps the DocuSign features most teams rely on against what LibreSign offers inside Nextcloud. Where the supplied facts do not settle a LibreSign capability, the cell tells you what to confirm in the current release before you plan a migration. Read the eIDAS and identity rows first if legal validity or sign-in policy drives your decision.
| Capability | DocuSign eSignature | LibreSign in Nextcloud |
|---|---|---|
| Sending and grouping documents | Envelopes bundle one or more documents, recipients and fields into one transaction | Signing requests attach to files already stored in Nextcloud, with the file staying in its folder |
| Templates and reusable setup | Templates hold documents, recipient roles and fields for repeated sending | Confirm in the current release how reusable request setups and field placement are stored and reused |
| Signer routing and mixed audiences | Routing orders and roles are configured per envelope, including sequential and parallel steps | Internal Nextcloud users and external signers can sit in the same request; confirm signing order options |
| Reminders and notifications | Reminders and expiry settings are configured per envelope | Notifications and reminders are supported; confirm frequency, expiry and escalation settings |
| Certificate and signature validation | Completion certificate records each signer's actions and the envelope's history | Validates signed documents and certificate status; confirm which certificate authorities and trust lists are used |
| Audit records | Certificate of completion is generated per envelope and can be downloaded with the signed file | Confirm what the signing record contains, how it is exported and whether it is kept with the file |
| API and integration breadth | Broad REST API and a large catalog of connectors to business applications | Integrates through APIs and the Nextcloud app ecosystem; confirm coverage for your existing systems |
| Identity sign-in | SSO and identity controls depend on DocuSign plan and configuration | Users come from Nextcloud accounts, which can be backed by LDAP, Active Directory, OpenID Connect or SAML; confirm the signing app honors these |
| eIDAS signature levels | Simple signatures are listed on Personal, Standard and Business Pro plans; advanced and qualified signatures are listed only for Enhanced plans sold through sales (DocuSign pricing page) | Confirm which signature levels LibreSign produces, whether it supports qualified certificates from a qualified trust service provider, and what a qualified signature requires |
| Legal framing | Electronic signatures are legally effective under the US ESIGN Act, subject to its exclusions | The ESIGN Act framework applies equally; validity depends on the document type and the signing process you run |
Where signed files, signer data and certificates live
Moving signing into Nextcloud changes where contracts, signer identities and audit records sit, and who controls them. Each of the four decisions below affects data residency, access control and the legal weight of a signed file, so settle them before choosing between LibreSign and DocuSign envelopes.
Data location of files and signed copies
LibreSign stores signed documents in Nextcloud file storage, so the files live wherever your Nextcloud instance and its data directory run: your own cloud account, a data center or an air-gapped network. DocuSign holds envelopes in its own cloud. Check where the Nextcloud data directory, database and backups sit, and whether any copies leave that location through notifications, previews or integrations.
Signer identity through the directory
Internal signers can sign in through LDAP or Active Directory, which Nextcloud's LDAP app maps to user accounts, or through OpenID Connect or SAML authentication backends. External signers are invited by email and do not need an account. Confirm which group of users may start a signing request, how a departing employee's access is removed, and how external signer identity is verified.
Who issues the signing certificate
Under the ESIGN Act, an electronic signature is not denied effect solely because it is electronic, but the evidence behind it still matters. Under eIDAS, advanced and qualified signatures depend on the certificate: a qualified signature needs a certificate from a qualified trust service provider listed in a national Trusted List. Decide whether your instance issues its own certificate, which gives a different evidentiary position, and whether your jurisdiction needs a qualified provider.
Retention of audit records
DocuSign produces a certificate of completion for each envelope, and the audit trail is kept with the envelope in its platform. With LibreSign, the signed PDF, the signing record and any validation results are stored as Nextcloud files and database entries, so retention depends on your backup schedule and your own retention rules. Define how long records are kept, where they are archived, and how you prove they have not been altered.
Keeping the platform supported
Nextcloud publishes a new major version every four months, and administrators must upgrade one major version at a time with a backup before each step. A signing workflow that depends on an app needs that app to be compatible at each step. Plan who applies maintenance releases and tests the LibreSign app after upgrades, because the signed records you keep are only as usable as the system that reads them.
Licensing and Nextcloud editions: what is free and what is paid
Nextcloud Server and the LibreSign app are both licensed under AGPL-3.0, so you can run, inspect and modify them without a license fee. The Nextcloud Server repository states that contributions from 16 June 2016 onward are licensed under AGPLv3 or any later version. LibreSign is also AGPL-3.0 and adds document signing to Nextcloud files, users and sharing.
- No license fee: Using the community server and LibreSign carries no per-user license charge under AGPL-3.0.
- Costs that remain: You still pay for servers or cloud capacity, storage, backups, database administration, patching and the staff time to run them.
- Upgrade discipline: Nextcloud requires one major version at a time, so you must plan and test each step yourself.
- Community support: Support comes from forums, documentation and any partner you contract, unless you buy an Enterprise subscription.
- Third-party apps: Confirm each app's license and compatibility before you enable it alongside LibreSign.
Confirm with the LibreSign project and your own environment whether any LibreSign feature depends on a specific Nextcloud edition or subscription before you assume the community build covers your needs.
Nextcloud GmbH sells Nextcloud Enterprise alongside the community version, aimed at enterprise, public sector and education users. It is sold in Standard, Premium and Ultimate tiers with a 100-user minimum. According to Nextcloud's pricing page, list prices start at 71.29 euros, 104.99 euros and 204.75 euros per user per year for 100 or more users, with lower rates from 200 users.
- Standard: Includes one year of maintenance, which fits teams that want vendor-backed patches without a longer commitment.
- Premium: Adds a maintenance lifecycle of five or more years, extended support hours and clustered instance support.
- Ultimate: Adds support up to 24/7 with response times down to one hour.
- Per-user recurring fee: The subscription recurs each year and scales with user count, so it is the largest ongoing line if you adopt it.
- Minimum commitment: Organizations under 100 users cannot buy the 100-user minimum tier as listed, so ask Nextcloud how smaller deployments are handled.
Before you choose a tier, compare the maintenance lifecycle and support hours with your own patching and on-call capacity, and request a written quote that states the user count and term.
The right edition depends on who will operate the platform and how quickly you need vendor response when something fails. A community deployment can be sound for a team with strong Linux, PHP and database skills, while a subscription shifts some support and lifecycle risk to the vendor. The choice is a cost and risk decision, not a license restriction you must accept.
- Internal capacity: Estimate who will patch, back up and upgrade the instance and whether that work is already staffed.
- Lifecycle needs: Compare the maintenance window of your chosen Nextcloud release with how often your compliance and security reviews require upgrades.
- Support expectations: Decide whether you need business-hours help, extended hours or 24/7 response.
- Hosting model: Enterprise support does not replace your own infrastructure, backups or security monitoring.
- Partner options: Implementation and hardening services are a separate cost from Nextcloud's subscription, so budget for them independently.
Ask the vendor and your implementation partner to put the edition, user count, support level and recurring fees in one written scope so the comparison with DocuSign is like for like.
What a self-hosted Nextcloud signing stack costs to run
What does DocuSign charge that a self-hosted LibreSign stack does not?
The DocuSign cost is a recurring subscription paid to DocuSign, usually per user, with envelope limits, and advanced features such as SSO, eIDAS advanced or qualified signatures and HIPAA or FedRAMP support sit on higher tiers. Its pricing page lists eIDAS simple signatures on lower plans and advanced and qualified signatures only on Enhanced plans sold through sales, so confirm the exact tier and add-ons you need with DocuSign. LibreSign itself is AGPL-3.0 licensed and carries no license fee, so your recurring costs move to infrastructure, staff time and any support contract you choose.
Who pays for the servers, database and web tier behind Nextcloud?
Your organization pays for them, either as cloud accounts, data center capacity or hardware, and these costs recur every month. The Nextcloud 35 system requirements recommend MariaDB 11.8 or PostgreSQL 18, PHP 8.5 or a supported earlier version, and Apache 2.4 or nginx with php-fpm, so size compute, storage and database licensing (if any) against those. Costs rise with user count, file volume, signing volume and high availability design, and fall when you consolidate onto existing virtualization or managed database services.
What backup and storage costs should I plan for a Nextcloud signing system?
Backups are a recurring cost tied to storage growth and retention periods, because signed PDFs, audit records and the Nextcloud database all need restore points. Nextcloud All-in-One includes BorgBackup-based backups, which reduces tooling cost, but the backup target storage and off-site copies are still your bill. Nextcloud's upgrade guidance requires a backup before every upgrade, so count the storage needed for those extra restore points as part of the run cost.
How much staff time does running a self-hosted Nextcloud signing stack take?
Staff time is usually the largest cost component and it recurs, covering patching, monitoring, certificate management, backups, restore tests and user administration. Nextcloud publishes a major release every four months and supports each for one year with monthly maintenance releases, and upgrades must go one major version at a time, so plan recurring upgrade windows. The effort depends on whether you have in-house platform skills, how many integrations and third-party apps you run, and whether your directory is connected through LDAP or SAML, so estimate it from your own team's capacity.
What does Nextcloud Enterprise support cost, and is it required?
Nextcloud Enterprise is optional. It is a paid subscription sold in Standard, Premium and Ultimate tiers with a 100-user minimum, and the list prices on the Nextcloud pricing page start at 71.29 euros, 104.99 euros and 204.75 euros per user per year for 100 or more users, with lower rates from 200 users. Standard includes one year of maintenance, Premium adds a lifecycle of five or more years and clustered instance support, and Ultimate adds support up to 24/7 with response times down to one hour. Check the current figures on the Nextcloud pricing page, because list prices can change and vary by volume.
Does DeployOpen's implementation work change the total cost of ownership?
Implementation is a one-time, fixed-scope engagement that DeployOpen agrees in writing before work starts, covering planning, installation, integration of LibreSign with your Nextcloud users and certificate handling, hardening, backup setup and documentation. Ongoing support, upgrades and continuous testing are available as separate retainers. A quote follows from the written scope, so ask for the scope items, deliverables and what is excluded, and compare them with your current DocuSign renewal and internal staff estimates.
What should I ask for in a quote for a LibreSign deployment?
Ask for a written breakdown of one-time items and recurring items, so you can compare them directly with the DocuSign subscription. Request the infrastructure sizing assumptions, the database and PHP versions covered, backup and restore responsibilities, the upgrade cadence and who performs each major upgrade, the directory integration scope, and whether certificate validation and signer notifications are included. Also ask which parts stay with your staff, which parts are retainers and what happens to the setup if you end the engagement.
How a move from DocuSign to LibreSign usually runs
The sequence moves signing into Nextcloud in an order that keeps open envelopes valid, preserves completed records and leaves the team with a tested, upgradable Nextcloud instance.
Inventory envelopes, templates and integrations
List every active DocuSign template, the envelopes still awaiting signatures, the recipient roles each template uses, and every system that calls the DocuSign API or receives its webhooks. Record which teams own each item. The step is done when the team has a written inventory that a second reviewer has checked against the DocuSign admin console and the integration code.
Export completed agreements and audit records
Download completed envelopes, their certificates of completion and audit trails through the DocuSign eSignature REST API or the web console, and store them in a retention location that does not depend on either system. Confirm with legal which records must be kept in which form. The step is done when a sample of exported files opens correctly and can be matched to the inventory by envelope ID.
Stand up Nextcloud on supported versions
Install Nextcloud Server on a supported PHP and database combination, using the versions listed in the Nextcloud 35 system requirements, behind Apache 2.4 or nginx with php-fpm. Choose the current supported major release at the time of installation and check the release schedule. Use Nextcloud All-in-One if the team wants the official packaged installation. The step is done when the instance loads over HTTPS and the admin checks report no critical warnings.
Connect identity and install LibreSign
Connect user sign-in to the existing directory using the LDAP app, or to an OpenID Connect or SAML provider, so signers and senders use their corporate accounts. Then install the LibreSign app from the Nextcloud app store and confirm that internal users and the external signer flow both work in a test request. The step is done when a test user can sign in with directory credentials and complete a signing request from start to finish.
Rebuild templates as Nextcloud-stored documents
Recreate each high-use DocuSign template as a document stored in Nextcloud, with folder structure, sharing rules and the signing positions that LibreSign requires. Map each old recipient role to an internal user, group or external signer in the new request. The step is done when every retained template produces a test request that a reviewer has checked against the original DocuSign template.
Switch integrations to the LibreSign API
Point each integration from the DocuSign API and webhooks to the LibreSign API, and confirm that status changes and completed files reach the systems that need them. Test the notification and reminder behavior with the owners of each integration. Keep the DocuSign credentials available for read access until the cutover is confirmed. The step is done when each integration has processed a test signing event end to end.
Run both systems until open envelopes close
Keep DocuSign running for envelopes already in flight and send all new requests through Nextcloud. Track open DocuSign envelopes until none remain, then restrict the DocuSign account to read-only access if the contract allows it. Schedule Nextcloud upgrades so that each major version is applied one at a time, with a full backup taken before every upgrade and third-party apps disabled until confirmed compatible. The step is done when no open DocuSign envelopes remain and the first upgrade plan has been documented.
Questions buyers ask before moving signing into Nextcloud
What drives the cost of moving DocuSign signing into Nextcloud with LibreSign?
The cost depends mainly on how much of the signing work is already in your hands. LibreSign itself is an AGPL-3.0 app, so there is no license fee for the app, but the total cost includes the Nextcloud server and its database, hosting, backups, your staff time, and any outside help. Recurring costs are hosting, maintenance and staff time for upgrades. One-time costs are setup, template rebuilding and testing. If you buy Nextcloud Enterprise for support, the list prices in the Nextcloud pricing page start at 71.29 euros per user per year on the Standard tier for 100 or more users, with a 100-user minimum. Ask any provider for a quote that separates setup, template migration, integration work, support and recurring hosting, so you can compare it with your current DocuSign spend.
How long does a move from DocuSign to LibreSign take?
The duration depends on the number of templates, the number of active integrations, the state of your Nextcloud environment and how many people must be retrained. A small team with a few templates and no API integrations can move faster than an organization with many approval paths, custom fields and systems that send envelopes automatically. Running DocuSign and LibreSign side by side until open envelopes close is usually part of the plan, so the calendar is also shaped by your longest open agreement. No duration is fixed by the product, so ask for a timeline built from a written inventory of your templates and integrations, and check it against your upgrade and change-control windows.
What must our team supply before a LibreSign project starts?
Three inputs decide whether the project runs smoothly. First, Nextcloud administration: someone must own the server, the database, PHP and web server versions, backups and the upgrade path. Nextcloud does not allow skipping major releases, so administrators must upgrade one major version at a time, back up before each upgrade and disable third-party apps until they are confirmed compatible. Second, identity: decide whether users come from LDAP or Active Directory through the LDAP app, or from OpenID Connect or SAML. Third, a template inventory listing every DocuSign template, its signer roles, routing order, reminders and where the signed files must be filed. Without that inventory, scope and quotes will be guesses.
Can our team migrate from DocuSign to LibreSign without outside help?
Yes, a team with Nextcloud administration experience and someone who understands your signing workflows can do much of the work internally. LibreSign is an app inside Nextcloud, so the skills overlap with running Nextcloud itself. The harder parts are usually the ones outside the app: setting up identity correctly, validating certificate handling for your documents, rebuilding templates, changing any API integrations that currently call DocuSign, and writing the operating procedures that your auditors will ask about. If your team lacks one of these skills, a fixed-scope engagement can cover that part while your staff keep control of the system. DeployOpen plans, implements, integrates, hardens, backs up and documents self-hosted platforms in your own infrastructure, and the scope is agreed in writing before work starts.
Does LibreSign meet eIDAS or ESIGN requirements for our documents?
The answer depends on the signature level you need and the kind of record. Under the US ESIGN Act, an electronic signature may not be denied legal effect solely because it is electronic, but the Act excludes some records, such as wills, most family law matters, most of the Uniform Commercial Code, and court documents. Under eIDAS, the European Commission describes simple, advanced and qualified signatures, and a qualified signature requires a qualified certificate from a qualified trust service provider listed on the national Trusted List. Whether LibreSign's signatures satisfy a particular requirement is a question for your legal and compliance team and, where needed, an independent auditor. Confirm with the LibreSign project and with your counsel which signature level and certificate source each document type requires before you commit.
What happens to our existing DocuSign envelopes and completed agreements?
Existing envelopes do not move automatically. Open envelopes should be allowed to finish in DocuSign, and completed agreements should be exported and archived before your DocuSign plan ends. Keep the audit trail with each agreement, since it is part of the evidence of how the document was signed. Ask your provider how completed records will be stored in Nextcloud, how they will be indexed, who can view them and how retention rules will apply. Also confirm the export steps with DocuSign's own documentation and check your contract terms for any export or retention obligations.
What operational work does a self-hosted LibreSign instance add?
Self-hosting moves signing operations to your team. You will manage Nextcloud upgrades, which arrive as new major versions on a four-month cycle, with each version supported for one year through monthly maintenance releases. Plan for backups before every upgrade, monitoring of the web server and database, certificate renewals for TLS, and checks that notifications and reminders are delivered. Ask for a runbook covering upgrade windows, restore testing and who is on call for a failed signing request. Nextcloud All-in-One is an official installation method that bundles backups and other services, which can simplify operations but still needs ownership by your team.
Does a Nextcloud signature hold up legally?
Under the US ESIGN Act, a signature, contract or record tied to interstate or foreign commerce cannot be denied legal effect, validity or enforceability solely because it is electronic. That protection applies to a LibreSign signature as much as to a DocuSign envelope, but it is a rule about form, not a guarantee that a particular signature will win a dispute. The Act also excludes records governed by laws on wills, codicils and testamentary trusts, state family law such as adoption and divorce, most of the Uniform Commercial Code, and court orders or official court documents. Before you move any of those document types into Nextcloud, confirm with counsel whether they fall inside or outside the Act in your jurisdiction, and whether a paper or wet-ink step is still required.
The European framework under eIDAS separates three levels: simple, advanced (AdES), which must let the signatory keep control and make later changes detectable, and qualified (QES). A qualified signature must be created by a qualified signature creation device, rest on a qualified certificate, and carries the legal effect of a handwritten signature across EU Member States. Qualified certificates come from qualified trust service providers that are audited, granted status by a national authority and listed in the national Trusted List. A LibreSign signature does not become qualified because it runs on your own Nextcloud server. Confirm in writing which level your LibreSign setup produces, how the signer's identity is established, and whether any certificate is issued by a listed provider.
Check what your current DocuSign plan provides before you assume parity. DocuSign's pricing page lists simple electronic signatures on its Personal, Standard and Business Pro plans, and advanced and qualified signatures only on Enhanced plans sold through sales, so a DocuSign customer may already rely on a level that a self-hosted setup does not produce by default. Ask counsel which signature level each agreement type requires, document that decision alongside the audit trail your LibreSign instance keeps, and treat the answer as the acceptance criterion for the migration.
How DeployOpen helps evaluate, implement and migrate Nextcloud signing
DeployOpen is a Chainscore Labs company that plans, implements, integrates, hardens, backs up, upgrades, documents and supports self-hosted open-source platforms in the client's own infrastructure. For Nextcloud signing, we start by confirming which files, users and signing flows must stay in Nextcloud, then build and hand over a LibreSign setup that fits them.
How we scope
- Engagements are fixed-scope, with scope, deliverables and timelines agreed in writing before work starts.
- The written scope lists which Nextcloud groups, shares and folders will be used for signing requests and who may send them.
- We confirm internal and external signer flows, reminder rules, and which certificate validation and notification settings the organization needs.
How we build
- We install and configure the LibreSign app on a Nextcloud instance in your cloud account, data center or air-gapped network.
- We connect LDAP, Active Directory, OpenID Connect or SAML sign-in where your identity setup requires it, and test login for each group.
- We test signing end to end, including external signers, reminders, validation of signed documents and the APIs used by your other systems.
How we hand over
- You receive documentation of the configuration, signing workflows, user roles and the backup and upgrade procedure for your instance.
- We document how signed files, validation results and notification logs are stored, so your compliance and records teams know where evidence sits.
- We walk your administrators through the one-major-version-at-a-time upgrade path and the checks to run before enabling third-party apps.
How we support
- Ongoing support, upgrades and continuous testing are available as retainers after handover.
- A retainer can cover monthly Nextcloud maintenance releases, LibreSign updates and re-testing of signing flows after each change.
- Ask any quote to state which items are included, who performs the upgrade testing, and how your own staff are involved.

