How to License QRCS Technology
QRCS technologies are designed to be embedded as secure back-end engines inside products, appliances, services, and device firmware. We support evaluation, pilot, and commercial licensing models that align with how infrastructure security is procured and deployed.
This page summarizes what can be licensed, common commercial structures, support options, and what a typical evaluation looks like. Detailed pricing and contract structures are provided under NDA on request.
Who This Is For
Our licensing and support model is designed for teams that need disciplined implementation quality and long lifecycle maintainability: OEMs and embedded manufacturers, infrastructure and security vendors, industrial integrators, regulated enterprises, and public sector deployments.
QRCS is suitable when you want to integrate secure transport, secure messaging, key lifecycle, or administrative access without building an internal cryptographic platform from scratch.
Licensable Components
QRCS offerings are modular. Customers typically license a foundation library plus one or more protocol engines, then expand as needed.
QSC Library
The cryptographic substrate used across the portfolio, designed for disciplined C integration, deterministic behavior, and long lifecycle environments.
Secure Transport and Tunneling
QSTP, DKTP, SATP, and SKDP engines that establish authenticated secure channels and tunnels suitable for gateways, appliances, services, and device communications.
Secure Messaging
QSMP messaging semantics for command and control, telemetry, event streams, and service-to-service messaging. Intended as an engine embedded behind your application.
Key Provisioning and Lifecycle
HKDS and SKDP systems for device and fleet key distribution, lifecycle management, and rotation models suitable for constrained and offline environments.
Infrastructure Access
PQS and SIAP components for administrative access, authentication, and controlled operational entry points, designed for integration into existing workflows.
Domain Security Systems
MPDC components for high assurance domain trust and distributed security architectures where compartmentalization and multi-party contribution are operational requirements.
Licensing Models
We structure licenses to match how customers deploy secure infrastructure. Common models include:
- Evaluation license: time-limited internal evaluation for integration and feasibility testing, non-redistributable.
- Commercial product license: redistribution rights for embedding QRCS components into a commercial product line.
- OEM and embedded license: per device, per device class, or per production run terms, suitable for long lifecycle products.
- Enterprise internal-use license: organization-wide deployment for internal systems and infrastructure.
- Strategic license: tailored scope for high assurance or multi-domain deployments, often paired with deeper support.
Commercial Support Options
Support is structured to reduce integration risk and provide long lifecycle stability. The appropriate tier depends on your deployment scope, release cadence, and assurance requirements.
| Support Tier | Designed For | Typical Inclusions |
|---|---|---|
| Standard | Teams with internal integration capability | Maintenance releases, bug fixes, security advisories, documentation updates |
| Professional | Active integration and pilot deployments | Integration guidance, architecture review, build and deployment assistance, priority response |
| Enterprise | Regulated, long lifecycle, or high assurance deployments | Long lifecycle support, coordinated disclosure, upgrade planning, custom profiles, direct engineering access |
Integration and Deployment Support
QRCS protocol engines are designed to be integrated as secure back-end components. Most customer work is packaging and operations, not re-implementing cryptography. We support common integration patterns, including:
- Embedded SDK integration: static library integration into firmware, gateways, and appliances.
- Infrastructure services: deployable tunnel, messaging, or access services that provide a hardened data plane.
- Sidecar and agent patterns: secure transport modules integrated into existing service meshes or control planes.
- Reference implementations: console demonstrations that validate protocol behavior and provide integration examples.
Evaluation and Pilot Process
Most engagements begin with a short technical alignment call, followed by an evaluation or pilot that validates fit in your environment. A typical path is:
- Initial technical discussion and scope definition
- NDA execution, if required
- Evaluation license issuance and delivery of integration materials
- Integration or proof-of-concept period (typical 30 to 90 days)
- Acceptance review and production planning
- Commercial license and support agreement
Public Source Code and Evaluation Licensing (2026)
QRCS publishes selected reference implementations, test code, and supporting materials to enable public review, cryptographic analysis, interoperability testing, and evaluation.
Publicly available source code and associated materials are provided under the Quantum Resistant Cryptographic Solutions Public Research and Evaluation License (QRCS-PREL), unless explicitly stated otherwise. This license does not permit commercial use, production deployment, commercial redistribution, or incorporation into any product or service without a separate written agreement executed with QRCS.
The public availability of reference material is intentional and supports cryptographic transparency, independent security assessment, and compliance with applicable cryptographic publication and export regulations.
For licensing inquiries, supported implementations, or commercial use, contact: licensing@qrcscorp.ca
Licensing, Transparency, and Cryptographic Assurance
Quantum Resistant Cryptographic Solutions Corporation (QRCS) publishes cryptographic reference implementations, formal analyses, and test materials as part of its commitment to transparency, independent verification, and long-term cryptographic assurance. In modern cryptography, public scrutiny and reproducibility are essential prerequisites for trust and adoption, particularly for new designs and post-quantum systems.
Accordingly, QRCS makes selected source code and documentation publicly available under a public research and evaluation license to support academic review, interoperability testing, and regulatory compliance related to cryptographic publication and export controls. Public availability does not imply unrestricted use.
All QRCS cryptographic software, protocols, and implementations remain the exclusive intellectual property of QRCS. Commercial use, production deployment, redistribution, or integration into products or services requires a separate written commercial license and, where applicable, a support and maintenance agreement.
QRCS does not rely on security through obscurity. Instead, security is achieved through conservative design, formal analysis, public evaluation, and disciplined operational governance. Supported, hardened, and production-grade implementations are provided only under commercial agreement.
Security and Assurance
QRCS maintains a specification-driven development approach. Protocol specifications define message formats, state machines, constants, and error handling. Implementations are written in disciplined C and supported with validation tooling to enable byte-level verification during integration and long-term maintenance.
For regulated deployments, we can provide due diligence materials under NDA, including architecture notes, protocol specifications, implementation analyses, and integration guidance.
Contact
Licensing and partnerships: licensing@qrcscorp.ca
Commercial support: support@qrcscorp.ca
General inquiries: info@qrcscorp.ca