Alelyon
Community

Build together, in the open.

Friends in the app, open source to build on, and research anyone can read.

Friends Open source

Friends: who is online, requests, and one-to-one chat. This panel needs JavaScript.

Demo with sample people, running in your browser.

Get involved

Four ways in.

  • Code with AI on the web

    Lattice’s chat and editor in your browser. No install.

    Open Lattice

  • Add your friends

    Pick a username in the app and share it.

    Friends

  • Read the research

    Findings beside their limits, misses included.

    Research notes

  • Build on open source

    The verifier and the published sign-in and social contracts.

    Open source
Open source

Open where it helps you build.

Each public repository is generated from the source the app is built from, through an allowlist and a scan for anything private.

  • Alelyon-OS

    Apache-2.0 or MIT

    The receipt verifier and its toolkit. Also on PyPI as alelyon-os.

    View on GitHub

  • Alelyon-Client

    Apache-2.0

    The app’s open pieces, starting with the sign-in and friends client and both of its API contracts.

    View on GitHub
01

Open source Public mirrors

Today the verifier and the sign-in and friends client; the app shell, Lattice, Sinai’s face and the simulator are planned next.

02

In the official installer Closed plug-ins

The replay engine, voice and, once it is ready, Sinai’s own mind.

03

On Alelyon’s servers Live services

Accounts, friends and the hosted preview. “Use offline” skips them.

Talk to us

Questions, bugs, ideas.

A person reads every message. Bugs in the open repositories go to GitHub issues; security reports go to the contact in the Privacy Notice.

ContactFAQ
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
The build is not being served yetOpen source toolkit
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.