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
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.
yourplatform.com/quantum
Qlro Recommendation
DOI 10.5281/zenodo.19785800
WorkloadChemistry · LiH ground state
Recommended
🏆
IBM Quantum Brisbane
IBM · 127 qubits · Heron r2
Overall
0.873
Fidelity
0.873
Cost / run
$0.14
Queue
2m 14s
IQM Garnet
Alternative
0.810 · $0.21 · 4m
Independence-attested · server-rendered✓ signed
qlro.ioLive recommendation rendered server-side and Ed25519-signed. Partner controls the input; Qlro controls the output — co-branded, immovable.
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.
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. The embed widget will not render until you've signed — Independence is enforced by the system, not just stated.
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
A ten-page, Ed25519-signed PDF — designed to be read in isolation by a regulator who has never met you. Verifiable offline with one CLI command.
Verification uses the example public key shipped beside the PDF — production audits use Qlro's rotating signing key, retrievable from /.well-known/qlro-signing-pubkey.pem.
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/.
Signature check
Open-standard cryptography (Ed25519 + SHA-256). Works offline.
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 programme, by application.
Independence is the structural premise of the programme — binding from the first day. We work closely with each pilot partner, bring their auditor into the conversation when that helps, and decide commercial terms together — not pre-set.
Already onboarded
Sign in to your surface
Already approved as a partner, or already bound as a customer-org member? Skip the sales page.