Post-quantum certificates issued through an API

Engagement models

Four shapes. Every quote is written against a scope.

No figure appears on this page. A published number is stale the day scope changes, and a stale number gets argued against rather than corrected. What is published instead is the shape of each commercial relationship and exactly what drives the quote, so you can estimate before you ask.

Retainer

A recurring commitment for a defined capability and a defined response posture, billed on a fixed period rather than against hours consumed.

3 service lines

What you are buying

Standing access to a named capability and a contractual response time. The value is that the engagement terms are already signed when you need them, so an incident starts with a phone call rather than with procurement.

Fits

Incident response, where negotiating scope during an incident is the expensive part
Fractional CISO, where the work is judgement and continuity rather than deliverables
Monitoring, where the obligation is continuous by definition

What drives the quote

Response posture: the severity levels covered and the response time committed against each
Estate size, counted in issuing hierarchies, monitored certificates and enrolment paths
Coverage window, and whether escalation authority sits with us or stays with you

Normally used for

Fractional CISO
Incident response
MSSP monitoring

Wrong shape when A retainer is the wrong shape for a one-off with a hard end date. Buying twelve months of standing capability to run a three-month migration is paying for availability you have already consumed.

Fixed-scope project

A statement of work with a defined boundary, a named artifact list and an agreed completion condition. Priced against the scope, not against elapsed time.

3 service lines

What you are buying

A set of artifacts that exist at the end and did not at the beginning: an inventory, a signed hierarchy, a policy document, an assessment. Completion is the artifact being accepted, not a date passing.

Fits

Post-quantum migration planning, where the deliverable is an inventory and a sequenced plan
PKI and certificate lifecycle build-outs, where the deliverable is a hierarchy and its policy
CMMC readiness, where the deliverable is a scoping document, an assessment and a POA&M

What drives the quote

Number of distinct signing and key-agreement surfaces in the boundary
Whether an existing hierarchy is being extended or a new one designed and keyed
Whether evidence has to satisfy an external assessor, which changes what counts as done

Normally used for

Post-quantum migration
PKI and certificate lifecycle
CMMC readiness

Wrong shape when Fixed scope is the wrong shape when the scope is genuinely unknown. Where nobody can yet say what has to be inventoried, the honest first step is a proof of concept that establishes the boundary.

Proof of concept

A short, bounded engagement against a single named question, with a written answer as the deliverable and no obligation on either side afterwards.

2 service lines

What you are buying

An answer to one question — whether a composite lineage survives your TLS terminators, whether your enrolment path can carry an ML-DSA signature, what your issuance volume actually is. The output is a written finding, including the finding that it does not work.

Fits

Establishing scope before a migration project is priced
Validating a composite profile against a specific terminator, client or hardware fleet
Testing the issuance interface against a real integration before committing to it

What drives the quote

The number of questions. One question is a proof of concept; five is a project with a softer name
Whether we operate in your environment or reproduce it in ours
Whether the output has to be defensible to a third party or only to your own engineers

Normally used for

Post-quantum migration
PKI and certificate lifecycle

Wrong shape when A proof of concept is the wrong shape for production work. It is deliberately not hardened, not documented for handover and not supported, and pretending otherwise is how a pilot becomes an unowned production dependency.

Pay per transaction

Metered against a countable unit — a certificate issued, an evidence record anchored, a verification performed. No seat, no minimum, no contract term.

2 service lines

What you are buying

Capacity without a commitment. The unit is countable and the count is recorded on the evidence ledger, so the invoice and the audit trail are the same record rather than two systems that have to be reconciled.

Fits

Certificate issuance where volume is variable or seasonal
Evidence anchoring, where the natural unit is the record rather than the month
Teams evaluating the platform who should not be asked to sign anything to do so

What drives the quote

The unit — issuance, anchoring and verification are counted separately because their costs differ by orders of magnitude
Volume band, since the marginal cost of an anchor falls sharply with batching
Whether evidence retention is required, and for how long

Normally used for

Certificate issuance
Evidence anchoring and verification

Wrong shape when Metering is the wrong shape when what you need is somebody accountable. A per-transaction relationship carries no response obligation; the moment you need one, that is a retainer.

Side by side

Choosing between the four

The deciding question is rarely price. It is whether you are buying an artifact, an obligation, an answer or capacity.

Engagement model comparison
Model	Billing unit	What completion means	Response obligation
Retainer	Fixed period	It does not complete. It renews or it ends.	Yes — severity levels and response times written into the agreement.
Fixed-scope project	Scope document	The named artifacts exist and have been accepted.	For the duration of the project only.
Proof of concept	One question	The question has a written answer, including a negative one.	None. A proof of concept answers the question; production work is scoped separately.
Pay per transaction	Countable unit	Each transaction completes on its own.	None. The moment you need one, that is a retainer.

Two shapes frequently run together: a project to build the hierarchy, then a retainer to hold the response obligation once it is carrying production traffic.

What can be quoted

22 lines, and what a quote against each one may contain

22 offerings across the cryptographic core, chain and operations tracks, each with its current status so scope is clear before work starts.

Build status to commercial posture
Status	What it means	What a quote may contain
Available	In service today.	Delivery — a fixed-scope project or a retainer.
Rolling out	In service, with further capability in development.	Delivery for the parts in service; the statement of work lists any remaining scope.
In development	Built and in final engineering before release.	An engineering or early-access engagement ahead of general release.
Planned	Designed and specified, on the product roadmap.	A proof-of-concept engagement.

The same mapping applies to every quote.

Every offering with its status and how it is quoted
Offering	Status	What it does	Quotable as	Deposited work behind it
CygnetLib and Cygnet Provider	Rolling out	A cryptographic provider with native post-quantum primitives, so a composite certificate is what issuance produces by default rather than the output of a migration project.	Delivery for the parts in service; the statement of work lists any remaining scope.	CygnetLib Cryptographic Library (20 source files); Cygnus Cryptographic Engine (159 source files)
Cygnus Foundry — cloud PKI	In development	Certificate issuance as an API: one verb per operation, an offline root, intermediates under policy, and SCEP or ACME enrolment at the edge.	An engineering or early-access engagement ahead of general release.	Cygnus Foundry Cloud PKI (39 source files); Sanctum PKI Stack (102 source files)
Sanctum AEGIS	Rolling out	A canonicalisation and tier compiler: policy in, deterministic DER and a resolved algorithm tier out, so two parties compiling the same policy get byte-identical artefacts.	Delivery for the parts in service; the statement of work lists any remaining scope.	None
Scryptorium and CygnusScrypt	Rolling out	The policy language. One declarative document describes how an estate issues, enforces, rotates and audits, and compiles to the configuration each component actually enforces.	Delivery for the parts in service; the statement of work lists any remaining scope.	CygnScrypt Compiler and Runtime (34 source files); Scryptorium Compiler (5 source files)
QZT — quantum-safe zero-trust overlay	Rolling out	A transport overlay where every peer holds an attested identity and a session is quantum-safe end to end, with an operator surface that shows each node sealed, attesting, warded or quelled.	Delivery for the parts in service; the statement of work lists any remaining scope.	CygnduitZT Transport (53 source files)
Sanctum LINK — attested enrolment	Planned	Device enrolment where the credential is bound to hardware at the moment of issue, so an enrolment record proves which device holds the key rather than which account requested it.	A proof-of-concept engagement.	None
sanctum-chain — evidence ledger	Rolling out	An append-only ledger of PKI events: OID provenance, hardware attestations and Merkle tree heads, with the append-only property enforced by the database rather than by convention.	Delivery for the parts in service; the statement of work lists any remaining scope.	Cygnus Convergence (30 source files)
Anchoring and proof of existence	Available	Periodic publication of a signed tree head to a public chain, so a record held privately can still be shown to have existed at a point in time.	Delivery — a fixed-scope project or a retainer.	None
Open timestamp receipts	Planned	Free, open, verifiable timestamping whose receipts a third-party client can check without contacting Sanctum at all.	A proof-of-concept engagement.	None
SCN — settlement and tokenomics	Rolling out	The unit that meters chain work: a mint schedule with halving, vesting with a cliff, burn on consumption, governance weight, and a multi-signature treasury.	Delivery for the parts in service; the statement of work lists any remaining scope.	None
Deterministic contract execution	Rolling out	Contracts expressed as a typed intermediate representation and executed by a deterministic interpreter with gas metering, so the same input yields the same state transition everywhere.	Delivery for the parts in service; the statement of work lists any remaining scope.	None
Attested collectibles	Rolling out	Non-fungible records whose provenance is a hardware attestation in the ledger rather than a claim in metadata, with collections, transfers and listings.	Delivery for the parts in service; the statement of work lists any remaining scope.	None
Chain as a service	Rolling out	A tenant gets its own ledger with its own anchor schedule and fee policy, metered per transaction with a monthly floor, across three tiers.	Delivery for the parts in service; the statement of work lists any remaining scope.	None
Validator set and reputation	Rolling out	A recorded validator set with per-validator reputation, so the question of who attested to a block has a durable answer.	Delivery for the parts in service; the statement of work lists any remaining scope.	None
Machine-payable verification	Planned	A verification call an autonomous agent can pay for with no signup, no API key and no prior relationship, so the client stays open-source while the call is still billed.	A proof-of-concept engagement.	None
Post-quantum migration readiness	Available	Cryptographic asset inventory, a bill of materials for what your estate actually uses, harvest-now-decrypt-later exposure, and a sequenced migration plan against the federal deadlines.	Delivery — a fixed-scope project or a retainer.	Sanctum PQC Validator (2 source files)
NIST SP 800-171 assessment evidence	Available	Control-by-control traceability from requirement to artefact to owner, built so a self-assessment score is defensible rather than asserted.	Delivery — a fixed-scope project or a retainer.	None
Fractional CISO	Available	A risk register that is maintained rather than produced once, board-legible reporting on a fixed cadence, and the quick wins identified before the roadmap.	Delivery — a fixed-scope project or a retainer.	None
Sanctum Intel	Rolling out	Continuous vulnerability triage against your actual inventory: advisories in, prioritised and ticketed work out, with exploitation likelihood weighed rather than severity alone.	Delivery for the parts in service; the statement of work lists any remaining scope.	None
Service desk and MDR triage	Available	Ten queues with per-queue automation ceilings, where incident response and detection queues assist a human and never resolve on their own.	Delivery — a fixed-scope project or a retainer.	None
Enterprise Control Center	Available	One operator surface for the whole estate: node inventory and enrolment, tunnel state, certificate expiry, desk load and the fault register.	Delivery — a fixed-scope project or a retainer.	Cygnary Control Plane (186 source files)
Endpoint and device operations	Rolling out	Remote monitoring, patch state and mobile device management extended from the same policy that governs issuance, rather than a separate tool with a separate truth.	Delivery for the parts in service; the statement of work lists any remaining scope.	None

Status comes from the same catalogue the services and platform pages use, so every page shows the same status for each line.

Common terms

True of every engagement regardless of shape

These are not negotiated per deal, so they are stated once here rather than discovered later.

Standing terms

Every quote is written against a named scope. A quote without a scope document attached is not a quote we issued.
Artifacts produced under a project are yours, including the source form of any policy, profile or inventory.
Where an engagement depends on a capability that is not yet built, the statement of work names it and the quote excludes it. Nothing is sold on the assumption that it ships during the engagement.
Retainers state the severity definitions and the response commitment in the agreement itself, not in a linked page that can be edited afterwards.

Bring a scope, get a number

If the scope is not yet knowable, the honest first engagement is a proof of concept that establishes the boundary. Engagement detail is on the services page.

Request a quote Contact