Professional Post-Quantum Integration Services
PQ Cloud subscriptions pay for hosted verification capacity. Production engineering that connects RANNTA to an exchange, blockchain, validator, treasury, wallet backend or administrative authorization path is a separate scoped engagement.
Review authorization boundaries, signer placement, key lifecycle, replay controls, failure behavior and deployment constraints. Deliver a written integration design and implementation scope.Exchange authorization integration · from $10,000
Integrate withdrawal, treasury, wallet-backend or administrative authorization paths with canonical payloads, ML-DSA-65 evidence, registered-key policy and fail-closed verification.Blockchain / validator integration · from $25,000
Integrate validator, node, protocol-operation or treasury authorization paths, including key registration/rotation, test vectors, failure-path tests and staged rollout support.Enterprise / custom engineering · scoped quote
Multiple authorization domains, complex deployment requirements, higher assurance documentation, custom operational controls and audit support are quoted after technical discovery.
What an implementation engagement can include
Scope can include authorization-path mapping, canonical payload design, signer/API integration, TypeScript SDK or direct HTTP integration, ML-DSA-65 public-key registration and rotation, HybridRequired policy configuration, replay protection, negative-path testing, staging or testnet validation, production runbooks and deployment support.
Commercial boundaries
Starting prices are indicative entry points, not fixed quotations. Final pricing depends on the number of protected authorization paths, current custody/signing architecture, HSM or KMS constraints, deployment topology, test environments, availability requirements, documentation requirements and requested delivery scope.
Hosted PQ Cloud API usage is billed separately when the production design uses the hosted service. The $599 Business plan is therefore not an integration fee.
Independent third-party security audit fees are not included by default. RANNTA can provide implementation documentation, test vectors and remediation support for an audit commissioned by the customer or separately agreed with an external auditor.
Customer private keys remain customer-held. RANNTA integration does not replace the customer's classical authentication, transaction-risk controls, native consensus rules, custody system or final business authorization decision.
Typical delivery sequence
Discovery and threat model → integration design → implementation → negative-path and replay tests → staging/testnet validation → production rollout plan → post-deployment verification.