Architecture overview

A self-hosted QSign deployment brings the signing experience and application integration into a customer-controlled environment. The exact deployment design depends on the signing methods, integrations, security requirements, and operating model agreed with each customer.

Conceptual flow

1. An application creates a signing request or a user starts one in QSign.
2. The signer reviews the document and completes the configured signing method.
3. QSign records the outcome and makes the completed document and audit information available to authorized users or applications.

The customer and QSign agree on data handling, access controls, availability, and support responsibilities before deployment. Detailed infrastructure diagrams and operating instructions are shared directly with authorized self-hosting customers.

For the hosted signing handoff, see the hosted USB DSC API guide.