Partner programme

Vendor-neutral quantum recommendations, embedded.

Your customers ask "why this device?". You hand them a third-party verified answer — rendered server-side, signed, immovably co-branded.

qlro.io/embed/recommend

↑ live widget. Without a partner key it shows the auth gate — the integrator sets it via partner_key=….

Pick your tier

Three ways partners use Qlro

Embedded for SaaS that want the recommendation in their UI. Audit for procurement-bound customers. Marketplace for inbound leads with zero integration.

Embedded

Drop-in widget for multi-vendor SaaS partners

best for

Quantum platforms, dev tools, algorithm SDKs

  • <QlroRecommend /> React component or iframe
  • Origin allowlist + key rotation + webhook
  • Co-branded footer (immovable)
  • 5-minute integration

Audit

Ed25519-signed PDFs for procurement + audit

best for

Consultancies, advisors, regulated R&D

  • 8-section, 9–12 page audit-grade PDF
  • Independence Statement on cover
  • Candidate-devices considered + reason codes
  • qlro verify <pdf> — offline auditor verification

Marketplace

Lead-routing from qlro.io to your platform

best for

Partners that want inbound, no integration

  • Per-qualified-lead pricing
  • Listing in /partners + /workloads CTAs
  • UTM-tracked routing + webhook
  • No SDK / iframe work required

5 minutes

From signed attestation to first recommendation

No infra change on your side. The widget is hosted on qlro.io and renders inside your product as an iframe — your customer never leaves your UI.

1. Sign attestation

One-click signing on the partner portal. Until non-NULL the embed endpoint refuses to render — Independence is a structural gate, not a promise.

2. Issue widget key

Generate a public-distributable key locked to your origin allowlist. Drop the key into NEXT_PUBLIC_QLRO_KEY (or equivalent).

3. Drop the iframe

<QlroRecommend partnerKey workload /> — or one iframe tag. React, Remix, Vite, Vue, and plain HTML examples are shipped.

YourFeature.tsx
import { QlroRecommend } from "@qlro/embed/react";

export function YourFeature() {
  return (
    <QlroRecommend
      partnerKey={process.env.NEXT_PUBLIC_QLRO_KEY!}
      workload={{ template: "chemistry.lih_ground_state" }}
      theme="auto"
      lang="en"
      onRecommendation={(rec) => {
        // hand off to your own analytics / lead-routing
      }}
    />
  );
}

Audit anatomy

What lands on the auditor's desk

An 8-section, Ed25519-signed PDF — designed to be read in isolation by a regulator who has never met you. Verifiable offline with one CLI command.

p.1
Section 1
Cover

Workload, customer, partner, snapshot DOI, content hash.

p.2
Section 2
Independence

Signed clause + partner attestation timestamp.

p.3
Section 3
Workload spec

Circuit, qubits, depth, priorities, constraints.

p.4
Section 4
Candidates

Every device considered. Excluded rows carry reason codes.

p.5
Section 5
Recommendation

3-axis decomposition + Pareto plot embedded.

p.6
Section 6
Confidence

Sample size, Fisher-z band, calibration freshness.

p.7
Section 7
Reproducibility

pip install + 5-line Python + curl. Frozen snapshot DOI.

p.8
Section 8
Citation + audit trail

BibTeX (customer-anchored) + signed audit log.

Verification

The auditor never has to trust us

Every audit PDF is signed with an Ed25519 keypair Qlro holds. The verifier needs only the PDF and our public key — no account, no API call, works air-gapped.

Audit PDF
Auditor receives the signed file.
qlro verify
One CLI command, no Qlro account.
Public key
Fetched from /.well-known/.
Ed25519 check
Recompute SHA-256 + verify.
PASS / FAIL
One line. Reason code on fail.
auditor's terminal
$ pip install qlro
$ qlro verify report.pdf
PASS: report.pdf
  Signature: 59dbe21566351faa…7a584eab361bf60b
  Public key: https://qlro.io/.well-known/qlro-signing-pubkey.pem

Pilot is open. Three slots remaining.

Per-recommendation pricing is finalised after the first three pilot partners are live. Independence is binding from day one. We bring your auditor into the conversation early when that helps.