Enterprise
Organization-wide document signing with integration, security, private deployment and professional services.
Deployment
WQ3 Dedicated
A private environment for WQ3 that we plan with you around your requirements.
Why teams use it
Isolated environment for your organization.
Deployment planned around your policies.
Integration and support included in planning.
Related
Security
How WQ3 protects documents through the signing workflow.
Plan a dedicated environment.
Contact sales to discuss your requirements.
Who it's for
Government bodies, financial institutions and large organisations that need an isolated environment and their own security policies.
How setup works
Planning
We agree requirements, integrations and security policies with you.
Build
We set up the dedicated environment and connect it to your systems.
Run and support
Team training and ongoing support after launch.
Common questions
Are the features the same in every option?
Yes. Cloud, API and Dedicated are different ways to use the same WQ3 platform.
Can we start with one and move later?
Yes. Many teams start on the cloud, then add the API or move to a dedicated environment.
Turn policies into reviewable requirements
Before discussing the dedicated environment, prepare a list of decisions your organization needs to resolve. Identify document types, participating teams, systems to connect, and policies governing access to signed documents and their handling. This keeps the deployment discussion grounded in actual workflows rather than general assumptions about what a private environment should provide.
Separate mandatory requirements from preferences, and identify who approves each decision. If hosting location, retention, recovery, or administrative access is governed by internal rules, raise those points explicitly for confirmation during planning. Do not assume that the word “dedicated” settles these details; make them part of your review before approval.
Define signing requirements separately from deployment
Deployment and signature level answer different questions: one concerns the platform environment, while the other concerns how each participant signs. WQ3 has exactly three levels: electronic signature, remote signing, and token signing. For your dedicated deployment brief, map document categories to their appropriate levels rather than treating a private environment as a reason to use one level everywhere.
Different signers can use different levels within the same document, allowing your requirements to reflect each participant’s role. The eKYC add-on verifies the account holder’s identity and can be required with any level; it is not a fourth signing level. Involve legal and compliance reviewers when deciding where identity verification, remote signing, or token signing is needed.
Review the evidence your teams will need
Make record review part of the dedicated deployment assessment rather than leaving it until after launch. WQ3 records document actions from sending through the final signature, and the audit trail accompanies the completion certificate. Identify who will review this evidence and how your organization will use it for record keeping, internal checks, or questions about a completed document.
The public check page supports verification without an account, using a QR code and reference and comparing the file’s SHA-256 fingerprint with the stored fingerprint. Verification records include signer names, signature level, and timestamps. Review this information with privacy and security stakeholders so your deployment requirements consider both the signing experience and subsequent document verification.
Set clear workflow acceptance criteria
Use a representative signing workflow as the basis for acceptance review: document preparation, sending, signer access, completion, and evidence review. WQ3 protections include locking documents once sent, individual invitations, roles and permissions, and encrypted connections using TLS 1.2 or newer. Translate these controls into practical checkpoints your reviewers can assess.
Keep technical acceptance distinct from legal review. Egypt’s E-Signature Law No. 15 of 2004 gives electronic signatures and documents legal validity when its conditions are met, not simply because they use a private environment. Ask reviewers to assess the proposed workflow and signing evidence together, then document unresolved requirements before approving the intended use.
Start your first signing journey today.
Create your WQ3 account, or talk to us about your organization’s requirements.
Frequently asked questions
Does dedicated necessarily mean on-premises?+
The dedicated description does not specify hosting location or guarantee on-premises deployment. Raise your hosting and location requirements during planning for confirmation.
Must every signer use the same level?+
No. WQ3 allows different levels for different signers in one document. Choose according to the document and each participant’s requirements.
Is eKYC a dedicated signing level?+
No. It is an account-verification add-on that can be used with any of the three signing levels.
Does a document verifier need an account?+
No. The public check page supports authenticity checks without an account, using the QR code and reference.
Does dedicated deployment alone guarantee legal validity?+
No. Legal validity depends on applicable conditions. Review signature level, identity verification, and document evidence with your legal adviser.