Skip to content

What is Aleph

A model is only part of the system. Aleph brings together the context, tools, memory, permissions, interfaces, execution, workflows, and specialized environments around a model.

The model is interchangeable. The working environment is where the rest of the system takes shape.

Aleph is local-first. Your workspaces, files, chats, artifacts and local execution run on your computer. Network access occurs when you intentionally invoke a connected API or service that requires it.

That can include a remote model or API, OAuth, a connector, or another external provider. The boundary is explicit rather than hidden in the product narrative.

The product direction includes a local Qwen 8B path, bring-your-own API keys, and supported external provider adapters. Specific models and CLI/agent runtimes depend on the installed build; availability depends on the installed release, local software, credentials, and permissions.

Aleph does not reduce the environment to a provider logo wall. Its role is to give interchangeable models a durable place to work.

Use La Sala to describe a task to an available agent and review its work. Open a specialized workspace for a domain-focused environment, or use The Workshop / El Cuarto to define an agent’s model, identity, goal, and tools. You do not need to compose a new agent before starting.

Read your first session for the path from installation to a first task.