Alelyon
Get access

One build. The boundary is your key.

There is a single Windows build, and downloading it asks nothing of you — no account, no LinkedIn, no key. The two tiers separate at sign-in, not at download: without a beta key everything runs locally and no hosted DQC-OS is issued; a key is what adds it, and a key is issued automatically when a signed-in account verifies with LinkedIn. The public alelyon-os toolkit is separate again and needs none of it.

What the key changes.

  • Open beta

    Local UI and open toolkit

    This is the same build as the closed beta, and it downloads right here — no LinkedIn, no account, no key. The tier is decided at sign-in: with no beta key, everything runs locally and no hosted DQC-OS is issued. Separately, the publicalelyon-os toolkit needs nothing either.

    What this tier includes, however you obtain the build:

    • Terminal UI, Lattice, the local calculator, and per-answer tool traces
    • A local model server, or a cloud provider key you configure
    • The separately published verifier, coordinate, compute-DAG, and API-client tools
    • No hosted DQC-OS backend or hosted receipt issuance
    Installer (.exe)Portable (.zip)

    Windows 10 / 11, 64-bit · 0.6.1

    Open toolkit source

    Packaged previews enter through local account sign-in. That local account lives on the user's machine; it is not remote identity or a hosted-service entitlement.

  • Closed beta

    Hosted DQC-OS access

    This is the hosted path for authorised requests against an Alelyon-operated deterministic backend, and that half is not part of the open beta. LinkedIn verification is live. A hosted DQC-OS key is issued automatically the moment a signed-in account completes verification — nobody reviews it, there is no queue, and it appears on your account page. An anonymous verification issues no key: the key needs an account to attach to, so sign in first and verify from the account page.

    • LinkedIn OpenID Connect establishes control of the LinkedIn account, not every profile claim
    • No LinkedIn scraping or public-profile lookup
    • A server-side issuance boundary: keys are minted only for signed-in, LinkedIn-verified accounts
    • A revocable bearer key for the account that redeems it, expiring on its own with self-serve renewal
    Continue to LinkedIn verification

Release integrity · 0.6.1

Built from commit 5cb8b0043df0. These builds carry no Authenticode signature, so the SHA-256 below is the only integrity check available to you.

  • Alelyon-Setup-0.6.1.exe · 233.2 MB

    410eccc793ae79f1dc2592fc9da4daf76358030b7ec481147ff6b978bb791840

  • Alelyon-0.6.1-win64.zip · 223.1 MB

    e1284845f86abeb5f359f4664fd68b7aed1af2662382941a4ca66bd58b8c3928

On Windows: certutil -hashfile <file> SHA256. A digest that does not match is the protection working — do not run the file, and report it.

Open toolkit

Replay the evidence you actually have.

alelyon-os is published separately from the Terminal and the planned hosted service. Its verifier can replay supported receipts against supplied inputs and policy. An authenticated result still needs a public key obtained out of band: the receipt can detect revision of committed inputs, but it does not prove that a producer did not invent bad inputs at capture.

pip install alelyon-os

Installs the alelyon-verify command. Runalelyon-verify selftest to exercise the bundled conformance fixtures without a network connection.

View on PyPISourceHow verification works
Choose your beta

One build. Two tiers.

The Windows build downloads with no sign-in, no LinkedIn and no key. Which tier you are in is decided when the app signs in: without a beta key you run everything locally, and a key — issued automatically to a signed-in, LinkedIn-verified account — is what adds Alelyon’s hosted DQC-OS.

Open beta

Run the app without a beta key.

There is one build, and this is the same one the closed beta uses — the tiers differ at sign-in, not at download. Sign in without a beta key and you get the local tier: Terminal UI, Lattice workspace, local calculator, and visible tool traces. A beta key is what adds hosted DQC-OS issuance.

  • Local-first Windows interface
  • Open Alelyon toolkit and source
  • No hosted backend entitlement
Download installerPortable buildOpen source toolkit

Windows 10 / 11, 64-bit · 0.6.1

Closed beta

Verify identity with LinkedIn to unlock hosted DQC-OS.

LinkedIn OpenID Connect verifies control of the LinkedIn account; Alelyon does not scrape your profile. It records a verified access request, and when you verify from your signed-in account page, your hosted DQC-OS key is issued automatically— no review, no queue, nobody to wait for. It does not create or sign you into an Alelyon account, and an anonymous verification issues no key: the key needs a signed-in account to attach to.

  • Everything in the open beta
  • Hosted deterministic DQC-OS calculations, unlocked by your key
  • Signed envelopes and certified answer paths
Sign upLog in

Signing up uses Alelyon’s own email-and-password account flow, which is separate from LinkedIn verification below. One Alelyon account signs you in to every Alelyon application, and it keeps working until you delete it. Verifying with LinkedIn comes next and links that identity to this account.

Verify with LinkedIn

Verify from your signed-in account page and your hosted DQC-OS key is issued automatically — it appears on that page the moment verification completes. Copy it into a password manager and enter it when Alelyon Terminal asks during sign-in; if it expires, opening your account page issues a fresh one.

Available now

Ask, and a person reads it.

Prefer to talk to someone first, or need access sooner than the self-serve paths allow? Ask directly.

Nothing about access waits on a person. The build downloads with no sign-in and no key; a hosted DQC-OS key is issued automatically when a signed-in account verifies with LinkedIn, and it appears on that account’s page. This address is for everything else — questions, problems, deletion requests, and anything a page cannot answer. It is read by a person, so no response time is promised.

Request access by email

Do not include credentials, account numbers, API keys, or position data in the message.