Account

Create an account, or sign in.

An Alelyon account is the thing you sign in with. It is separate from LinkedIn verification — that is how you get the Windows build, and it does not create an account on its own.

Looking for the download? That is LinkedIn verification, and it does not require an account.

Choose your beta

One build. Two tiers.

Verify with LinkedIn once and the Windows build is yours. Which tier you are in is decided when the app signs in: without a beta key you run everything locally, and a key 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
Closed beta

Verify identity with LinkedIn and download the build.

LinkedIn OpenID Connect verifies control of the LinkedIn account; Alelyon does not scrape your profile. A completed verification hands this browser the Windows build straight away — there is no queue and nobody to wait for. It also records a verified access request, which is what an operator reviews when a hosted DQC-OS key is issued later. It does not create or sign you into an Alelyon account, issue a hosted-access key, or grant hosted DQC-OS access.

  • The Windows build, downloadable now
  • Everything in the open beta
  • Hosted deterministic DQC-OS calculations (once a key is issued)
  • Signed envelopes and certified answer paths

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.

The download starts from the page this returns you to, and the grant it carries is short-lived — take the build then rather than later. The hosted DQC-OS key is the separate, reviewed part: when the service opens it is shown once, so save it somewhere secure and enter it when Alelyon Terminal asks during sign-in.

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.

The build itself is self-serve: verifying with LinkedIn is what hands it to you, and no one reviews that. This address is for the hosted DQC-OS key and for anything that needs a person. Requests here are read, and a key is granted case by case while Alelyon is in closed beta. A public beta environment is planned and will use the same route; it is not open yet, and no response time is promised until it is.

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