A thirteen-seat council of frontier models · post-quantum signed answers

The apex of AI, cryptographically verifiable.

Throndar fuses what the seats of a thirteen-model council answer into one governed answer, and signs it with post-quantum cryptography you can check yourself.

Claim your free seat →   Sign in

Start free with 200 credits — no card required.

ML-DSA-87 signed receipts · Falcon-1024 co-signed at the model plane (FN-DSA, pre-standard — FIPS 206 not yet published) · transport is the platform's TLS · signing keys never sent to the browser

Frontier models from the leading labs · normally fused into one governed, post-quantum-signed answer

13

seats on the council roster

PQC

ML-DSA-87 (FIPS 204) signed answers

Verifiable

check a signed answer in your browser

$0

to start — 200 credits, no card

Why Throndar

One console. Every advantage.

A premium intelligence layer engineered for teams that refuse to choose between power, polish and security.

The governed council

Why a council beats one model

A single model gives you one guess. Throndar sends your prompt to the seats of a thirteen-model council and fuses their drafts — a council answer is normally synthesised from several seats, and the signed receipt records when it was not (council-grounded: false).

1. 01 Route. Your prompt goes to every configured seat of the council — the same prompt to each, or to the first three on a fast Live-Voice turn. Nothing splits it up or picks seats per part.
2. 02 Deliberate. The seats answer in parallel, and a seat that has not answered within the draft window (at most 30 seconds) is dropped; one seat cross-examines and fuses the drafts — disagreement is a signal, not noise. If only one seat answers, or the fusion fails, the receipt says so.
3. 03 Govern. The answer's governance flag records how it was made — council_synthesised, synthesis_fallback or single_model — and the receipt signs that flag with the answer. No separate check grades or approves an answer before it ships.
4. 04 One answer. You get a single answer — normally synthesized from several seats, with a signed record of how it was made — instead of one model's unverified guess.

See how the 13-model council works, end to end →

Post-quantum by design

Built for the quantum era.

Transport is whatever TLS the hosting platform and runtime negotiate with each client — the protocol version, cipher suite and key-agreement group are theirs, not Throndar's; Throndar runs no key exchange of its own. Its post-quantum contribution is the signatures: an ML-DSA-87 (FIPS 204, final) receipt on signed-in council answers; Falcon-1024 (FN-DSA, pre-standard — FIPS 206 not yet published) and SLH-DSA-SHA2-256f (FIPS 205, final) co-signatures that the model-plane bridge puts on every answer it signs; and an SLH-DSA co-signature on the web layer's own receipts, Autopilot receipts and transparency-log tree heads when that leg is enabled.

• NIST FIPS 204/205
• One algorithm in common with CNSA 2.0
• Governed & auditable

ML-DSA-87 is the general-purpose signature algorithm the NSA CNSA 2.0 suite names; the suite also names a key-encapsulation algorithm and the stateful hash-based signatures LMS and XMSS, which Throndar does not run itself. One algorithm choice in common — not suite alignment, not a certification. See the standards mapping →

Signature · ML-DSA-87

FIPS 204, final: the receipt on signed-in council answers.

Co-signatures · Falcon-1024 / SLH-DSA

Falcon-1024 (FN-DSA, pre-standard — FIPS 206 not yet published) and SLH-DSA-SHA2-256f (FIPS 205) from the model-plane bridge on every answer it signs; the web layer adds SLH-DSA to its own receipts when that leg is enabled.

Transport · platform TLS

Browser and bridge hops use the TLS the platform negotiates; Throndar adds no key exchange of its own.

Keys · server-side secrets

Web receipt keys derived with HKDF-SHA256; the bridge's keys loaded from its own environment. Never sent to the browser; no HSM or KMS; public keys published for independent verification.

Provenance you can check

Don't trust us. Verify it.

Verify a Throndar answer yourself at /verify/proof — it runs in your browser against the public keys embedded in the proof. A sample proof is published at /demo-proof.json.

Verify any answer · Sample proof (JSON) · Public transparency ledger

Premium media

A premium media engine suite.

Image, voice and video generation from named third-party engines in one metered console: FLUX image generation is live by default; ElevenLabs voice, Topaz upscale and Runway, Kling and HeyGen video are built and switched on per deployment.

• Flux Image (image) · live by default
• ElevenLabs Voice (voice) · switched on per deployment
• Runway Video (video) · switched on per deployment
• Topaz Upscale (image) · switched on per deployment
• HeyGen Avatar (video) · switched on per deployment
• Kling Video (video) · switched on per deployment

Open the Studio

Connectors

Bring your whole stack.

Connect the tools your team already lives in so the council can read real context. The connectors only read, and connector tokens are encrypted server-side and never exposed to the browser.

• Email
• Calendar
• Drive & storage
• Code & repos

Payments

Pay how you prefer.

Settle in crypto or fiat — Bitcoin, Ethereum, Solana and Algorand, plus card; Zelle where enabled, as it is switched on per deployment.

• Bitcoin
• Ethereum
• Solana
• Algorand
• Zelle (where enabled)
• Card

On-chain settlements are verified before access is granted.