Alelyon
FAQ

Questions, answered.

  • What is Alelyon?

    An AI lab, and the Windows app it builds for working with AI: Lattice (an AI code editor with an agent), local and cloud models, a research assistant, the assistant Sinai, and friends.

    The Alelyon app
  • Is Alelyon free?

    Nothing on this site asks for payment: the app and an Alelyon account cost nothing today, and no price has been set for later releases. This page will say so before one applies.

    Models you bring can cost money through their providers, or through your Claude or ChatGPT plan when you use Claude Code or Codex.

  • Does it work offline? Do I need an account?

    No account is needed. Choose “Use offline” at sign-in and everything on your computer works: your models, files, the IDE and saved research. An account adds friends and Alelyon’s hosted preview; sign in with GitHub, Google, Hugging Face or LinkedIn.

  • Is my code private? What leaves my computer?

    Only what you send to a service you chose: a prompt to a hosted model, a search to OpenAlex or arXiv, a message to a friend, a sign-in to Alelyon. On its own, the app only asks Alelyon’s sign-in service whether it is up, with no account details. There is no analytics or telemetry, and with a local model through llama.cpp your prompts never leave your computer.

    Security & privacy
  • Can the agent change files or run commands on its own?

    Not without you. Its edits wait for your review, commands and tools ask first unless you always allowed that exact one, and Ctrl+Alt+End stops every turn. Auto mode, which only you can switch on, lets the agent use your desktop; purchases, payments, sign-ins and account changes still ask, and it never types a password.

  • Can I run local LLMs? Which models work?

    Yes: GGUF models on your own GPU through llama.cpp. Also open models hosted by OpenRouter, Hugging Face, Together AI, Groq, Fireworks AI, DeepInfra or Cerebras with your key; Claude Code and Codex on your own plans; any OpenAI-compatible endpoint; and Alelyon’s hosted preview with an account.

  • Are friend messages encrypted?

    No. Only you and your friend see them, in the app and on this site, but they are stored on Alelyon’s server in plain text and are not end-to-end encrypted. Removing a friend deletes the conversation for both of you. Don’t send anything you would not want stored.

  • Is it open source?

    Parts are. The receipt verifier and toolkit (Alelyon-OS) and the sign-in and friends client (Alelyon-Client) are public under open licences, and more of the app is planned to follow. The official installer also carries closed plug-ins, such as the replay engine and voice.

    Open source
  • Is the download signed?

    The download page says so for each release, from the release’s own manifest, with SHA-256 digests to check your file. An unsigned build makes Windows warn that the publisher is unrecognised.

    Download
  • Does it run on macOS or Linux?

    Not yet: the app is built for Windows. Lattice on the web runs in any modern browser, and opening a folder there needs Chrome or Edge.

    Lattice on the web
  • How do I uninstall it?

    From Windows Settings, Apps. Your models and projects stay where you put them; the app’s own state is in your user folder under .alelyon, which you can delete. To delete your Alelyon account and its data, write to the address on the privacy page.

    Privacy
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.