No credentials in the browser
Provider keys and secrets remain server-side. The client never sees them.
Documentation
Docs & developer experience
14 of 15 documents published — specifications, policies and guides written from the code that actually runs. Drafts are marked.
01 · START
Start here
What QAISS is, what it is not, and the fastest path to something real.
PublishedRead02 · STARTQuantum computing in plain English
Qubits, gates, measurement, noise and hybrid workflows — without the hype.
PublishedRead03 · STARTArchitecture overview
The five QAISS layers — experience, coordination, execution, data, settlement — and what is live in each today.
PublishedRead04 · SPECIFICATIONWorkload schema (Passport v0.1)
The portable manifest that makes a quantum run reproducible and verifiable.
PublishedRead05 · SPECIFICATIONBackend adapter specification
The contract a backend must follow so its passports verify everywhere.
PublishedRead06 · SPECIFICATIONHybrid execution & backend adapters
How one passport moves between CPU simulation, GPU simulation and quantum hardware, and which adapters exist today.
PublishedRead07 · SPECIFICATIONBenchmark methodology
Protocol v0 (draft): workload, timing, required metadata and comparability rules.
PublishedRead08 · BUILDAPI reference
Proposed endpoints. No production API exists; examples use mock data.
DraftRead09 · BUILDPython & TypeScript SDK
What you can use today from Python and TypeScript.
PublishedRead10 · BUILDExamples
Runnable examples — in the browser today, as notebooks later.
PublishedRead11 · POLICYSecurity model
How the site and connectors are designed to fail safely.
PublishedRead12 · POLICYPrivacy model
Which requests leave your browser, to which third parties, and why — no analytics, no cookies set by QAISS, no uploads.
PublishedRead13 · POLICYData retention
Exactly what QAISS stores: three preferences and, only if you use those features, saved Lab experiments and challenge progress, all in your own browser storage, and nothing on any server.
PublishedRead14 · POLICYChangelog
Where to find every material change to the QAISS site, documentation, statuses and public claims, with versions.
PublishedRead15 · POLICYKnown limitations
An honest list of what does not work yet, what is untested, and what QAISS does not claim.
PublishedReadAPI preview · mock
Shape of the future API
Illustrative only. Mock data until a production API exists.
POST /v0/workloads # MOCK — no production API exists
{
"workload": { "format": "qaiss-ir/0", "ref": "sha256:…" },
"targets": ["sim.cpu.reference"],
"passport": { "seed": 42, "precision": "fp64", "noise_model": null },
"consent": { "paid_backends": false }
}
→ 202 { "job_id": "job_mock_01", "status": "queued" }Connector rules
Non-negotiable for every future connector
Rate limits & abuse protection
Every endpoint is rate-limited and monitored.
Audit logs
Submissions, policy decisions, and data access are logged.
Explicit consent for fees
Jobs that incur third-party usage fees require explicit, per-job user consent.
No seed phrases, ever
QAISS will never ask for a seed phrase or private key.
Full transaction disclosure
Any future on-chain action shows contract, network, fees, permissions, and risks before signing. No automatic signing.